The author pits "Code Monkeys" against the Enterprise Architects in the web development world, and as one example, uses stored procedures vs. 'ad-hoc' queries created from code. The debate here is simply this - does it really matter if you're coding by enterprise standards, if you're getting the job done?
A straight line is the shortest distance between two points, but in programming, and more specifically, ASP.NET; you can throw that idea out the window. With ASP.NET we're presented with a plethora of best practices and patterns such as: N-tier development, code behind, and OOP methodologies, to name a few. But what does it all boil down to at the end of the day? The answer: creating a great experience for the end user. The author of the article sums it up best?
"Is the small developer that runs a fan site on stamp collecting wrong because she doesn't use stored procedures to fetch her news headlines? Absolutely not! (We do hope that she's parameterizing her queries, but she's certainly not wrong.) If she gets a couple thousand page views a day, and all she does is show headlines, she doesn't need some giant n-tier application that can drive a rover on Mars."
If I had to describe my coding style, I would say I'm somewhere in between a code monkey, and an enterprise architect?maybe a 'Coding Architect'? I often want do get the job done as quickly, and efficiently as possible. But at the same time I can be very meticulous, and I often look for the best approach, rather than the fastest.
Previous Topic
