Palermo4

# re: OOP?

My standard retort to that kind of immaturity is: "That's the primary difference between being 'just a coder' and a programmer.....and between being a programmer and a developer or architect!"

If they scoff at that, explain that the distinction between a coder and programmer is the ability to perform good up-front top-down LOW-level analysis and design before CODING.....and the distinction between a programmer and a developer/architect is the ability to perform good up-front HIGH-level analysis and design before PROGRAMMING.

My second retort would be even more pointed: "This is EXACT reason why executives think that software development is a LOW-LEVEL activity! They see LOTS of 'coders' and don't understand the BIG difference between 'coding' and 'developing'...and choose to off-shore our jobs because we fail to educate them on this difference!"

Then, of course, if they STILL don't get it: "Coders are the first to lose their jobs! It's your choice! Bootstrap yourself to a higher skill-level or CHANGE CAREERS!"

# re: OOP?

All that is true if you're working in a department that primarily designs software or even working on a big project. For most of my career, I've developed small projects that needed to be done quickly. I would love to have the time to hash out all the details up front. Hopefully OO will allow developers to convince management of the benefits of having to do the design up front. But I'm skeptical. If you're working for a department that doesn't really understand what you do, how do you convince them that adding design time (with no visible product) is good?

# re: OOP?

That's really fun because I think so many of us start out that way. No matter how many years ago it was, I remember concentrating on what I COULD do with code and doing it. Coding for the sake of code, not for the sake of the solution. Very interesting indeed.

# On syntax and semantics

<p>
This entry was sparked by the post "<a href="http://weblogs.asp.net/palermo4/archive/2004/04/13/112664.aspx">OOP</a>" and the coding, programming, developing, architecting that followed it:
</p><p>
In the beginning, there was syntax. "Hello World!" was printed, and all was well.
</p><p>
Then, one by one, semantics started creeping in and the beauty of syntax was lost.
</p><p>
As the semantics multiplied, soon, no syntax was ever discussed.
</p><p>
The semantics started rigidifying into structures and patterns and soon the tower of babel was built.
</p><p>
Alas, the syntax on which the semantics were built could no longer hold the weight of the tower, and it came crashing down.
</p><p>
The importance of syntax, made apparent by the crashing of the tower, re-emerged.
</p><p>
Syntax was re-built considering all semantics, "Hello World!" was printed, and all was well again.
</p><p>
------------------------------------
</p><p>
Coders, there's more to code than the code.
</p><p>
Developers, if you are so lucky as to be able to think in a programming language, then architecture and design will flow from your fingers and all will be well. Just remember, if you think in C#, the limits of your thinking will be the limits of the language.
</p><p>
Don't develop in only one language !
</p>