I would recommend reading Code Complete, 2nd Edition.

That is normal, and it is why code should be written as simply as possible without sacrificing functionality, and why comments that describe why you wrote something the way you did are critically important.

You should plan enough to understand how the application is supposed to work. The details can be ironed out during development, but the overall vision should not change much. Planning is even important for conversions because the target language might have better ways of designing the code. The result will probably be completely different from the original even though they both do the same thing. A straight line by line conversion of VB6 to C# is not a good idea, if you get my drift.

I always make sure that clients are involved in the development process from start to finish, both to keep myself informed about their needs and to keep them informed about what I am doing. That way things do not get too far off track and everybody understands the vision of the final product.

Nobody can predict when they will finish a project. Estimates are always off unless you get lucky. You should do some research on agile software development. It might help you nail down some of the process stuff that you seem confused about.

This is like the most useless book I've ever purchased.

I think it offers a lot of good material and things to think about to someone young in the industry.