171 karma · joined May 12, 2010
Here's to hoping a few more follow in his footsteps...
Can someone who knows what they're talking about tell me how accurate that summation is?
If, however, you feel that anything more than a front controller, a registry and some common sense is just ego-stroking, roll your own and enjoy ;)
Can someone shed some light on any advantages they feel are of a reasonably significant importance, and why? I mean, I can see plenty of advantages, but they're all so negligible they're not worth even the time it takes to change font, IMHO.
...and do please note the IMHO - I'm asking, not telling :)
Source? That's almost entirely untrue in my own experience (my audiences are quite large, quite varied, and not particularly ludite).
I would have thought he meant it the other way around.
Fear not though - as someone with an entire menagerie of unpopular opinions about programming, business and life in general, karma as a measure of agreement with the opinion is more useful to me than as a measure of people's opinion on the constructiveness of the comment. It's also feeding a spectacular persecution complex, which comes in handy when I discover I've been talking rubbish on a subject :)
As good a definition of code beauty as I've ever seen... even if not as popular.
'Clean lines' is my mantra. Whether it be done through a remote API, a database queue or a multitude of classes, loose coupling and sensible, strict and adaptable communication between clearly separated units is my number one priority. Everything else has, at the very least, the danger of encouraging the traces of the architecture astronaut within me... and he's enemies number one, two and three :)
The units themselves can be as good or as thrown-together as circumstances demand, but the separation/communication being of a professional standard is set in stone.
Wishful thinking? How does his lifespan affect the probability of the 2-hour mark being broken?