santeron wrote:That you will learn "on the job", not from a book or in a classroom.
Maybe there is a part of the programming process I haven't think of that I lack knowledge and experience.
As I said my major problem is not writing the code, but mostly how to structure it beforehand on paperDon't you see how this very sentence contradicts itself? If you had no trouble writing the code, you wouldn't need designs on paper.
santeron wrote:We are talking about exactly the same thing. And yes what you talk about is very difficult and can hardly be taught from a book or in a classroom. Really, it takes years of experience before you get to that point where you can comfortably lay down a proper OO design based on functional and technical specs.
lol I didn't mean it like that. Of course I can write code and structure it in my head with no problem. I have never used an actual paper to do so (at least not for fairly easy programs). If you give me a layout or an algorithm I will probably have a decent solution pretty quickly. What I was trying to imply, maybe falsely, is that most of the times I have problem moving from clear specifications of a system to classes, interfaces etc. in a clear, modular, encapsulated OO design.