"And, behold, I will deliver you up to the programmer tendency to build overelaborate castles of abstractions."<p>--- King James Programming (<a href="http://kingjamesprogramming.tumblr.com/post/136036727910/55-and-behold-i-will-deliver-you-up-to-the" rel="nofollow">http://kingjamesprogramming.tumblr.com/post/136036727910/55-...</a>)
The first one is basically the messaging system and a smart broker. I’m not aware of any brokers that would take into account how busy a particular node (they usually just use round robin approach) but surely the concept you outlined is far from being a definition of over-engineering, cron is almost always worse because it is hardly scalable (it is with some crutches and until some point when it becomes unscalabel again, and it introduces a consistent delay).
This is superb. YAGNI may have it's own Wikipedia entry, but that doesn't mean that we remember it when a brilliant idea comes to mind.<p><a href="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it" rel="nofollow">https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it</a>
Most of these sound awful to begin with, except the first maybe. Not to insult this guy, but people who force ego projects like these in a company quickly end up looking like a charlatan.
> "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."<p>This is brilliant.