The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
In the last 2 jobs I have been to, I saw a pattern... A pattern should warn against and I am wondering what could be done...
In both case there are application with lots of man hours and developer and moving part dependant on each other and developed (and, more importantly, updated) independently....
And it happens every now and then that some code that was once working fine stop doing so because one of it dependency started to behave differently... And lots of time is spending not adding and fixing new code but updating old one to fight what could be called new bug affecting old code.
This can be a real time waster...
How long do you expect to heap one sinister hack upon another without getting into trouble? Or has anyone ever sucessfully built a skyscraper on top of something that started out as a wooden shack, nailed together by some kids decades before?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
The most fascinating thing is that when new code developed - and destroyed old code - it passes QA (at least here), but because no one knows about the relation between this and that in the complicated landscape, the bug happily installed in customer's site... So not only they discover it (which look bad), but we have to fix it under pressure (SLA), so we obviously will introduce more bugs - one of them will be to run the new code
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
Last week my fearless leader (director/boss) sent an email of praise in that he ran some applications he built dependent upon my frameworks. He hasn't touched them in over four years (no one has). It still all works. Backwards comparability maintained.
Lesson to be learned? There are some side benefits from being the Lone Coder.