There will be code (and maybe a drop of blood)
Now this is part of a greater series of posts that will follow, about how you go on writing code in an OO world. All the way from analysis to testing covering all sorts of topics and coding practices following a tutorial style.
It strikes me as odd (though I see the reason) that a lot of developers find it hard to correctly identify classes, objects, class relationships, responsibilities etc.
Seems to me like they quickly try to put their thoughts into code in fear of losing them and as a result have working code -yes- but quite as messy as their thoughts.
Now all the posts (including this one) that will follow on the series will not try to be clever. But hopefully act more like a reminder on what OO programming is all about.
It may sound controversial and some might gasp when I say this but; what precedes OO programming is grammar not math. That's OO 101. (though it doesn't seem to be part of any University's module guide)
So what to expect. The series will take a paragraph of text from any source on the internet (could be a wikipedia article, a news story or even a qnoid post) and transform it to object oriented code.
The series will be called "Don't lose your train of thoughts", so don't miss a post!
Disclaimer: As always, the code that will be part of the series is "example code". Do take it seriously, but only as much. Take the advice, not the code.
Kudoz: Derren Brown (inspired for the title "Train of Thoughts" from one of his "Trick of the Mind" episodes)