That is nothing new.gilesgoatAugust 11 2011, 10:26:49 UTC
That is nothing new Triggur .. whoever works in the IT long enough ( not even for that long really ) know about the more-than-what-should-be amount of SW that works that way.
I would also add "the demo curse", the thing that becomes like "a demo" to satisfy some customer will to buy and sometime make a proof of concept that with a hack there and a patch there becomes what "the final product" should have kinda been.
In theory "we'll refine it later" in practice this not always happens.
Let's redesign/do it proper may end up with :
- there's no time for that - they are already happy with that they installed it into ( too many places ) (**) - nobody is actually paying for that redesign (*) - we'll do it another time ( biggest lie ) - we need that money now
Actually (*) is the mayor cause of some hacked SW.
Coupled with (**) of course and they fact you are already doomed to support "the demo".
Re: That is nothing new.kakoukorakosAugust 11 2011, 12:44:36 UTC
Trig knows this.
Popularizing such a term would just make it more fun to ridicule bad behavior, and maybe make folks just a little more aware of their own bad behavior, lest they get ridiculed.
You know, much like the "It's not a bug, it's a feature!" mantra that mocks developers who are so difficult when it comes to fixing their broken crap that they try to convince their customers that the software is "working as intended", even if that makes no sense because it is horribly broken.
I like this idea, thedailywtf.com would probably catch-on to it if they were presented with a story to publish that used the analogy. There could even be little fly stickers to put on your monitor to signify how many flies you've killed before swallowing them!
Re: That is nothing new.triggurAugust 11 2011, 13:20:38 UTC
This isn't meant for a broad re-architecture or fixing a long-term problem.
It's meant for a single developer who is designing himself in circles or coding himself into a corner because his initial solution to some small problem was wrong, and as he runs into new issues, he adds new shitty hacks to just make it work, etc.
It's more a short term-- say days or weeks, not months-- kind of scope.
I run into this *constantly* with interns; they make one bad decision but then they don't have the experience to notice that everything suddenly got complicated and hard because of that one decision. Maybe EVERYTHING is already complicated and hard to an intern, so they don't realize their mistake.
Comments 5
Reply
Reply
I would also add "the demo curse", the thing that becomes like "a demo" to satisfy some customer will to buy and sometime make a proof of concept that with a hack there and a patch there becomes what "the final product" should have kinda been.
In theory "we'll refine it later" in practice this not always happens.
Let's redesign/do it proper may end up with :
- there's no time for that
- they are already happy with that they installed it into ( too many places ) (**)
- nobody is actually paying for that redesign (*)
- we'll do it another time ( biggest lie )
- we need that money now
Actually (*) is the mayor cause of some hacked SW.
Coupled with (**) of course and they fact you are already doomed to support "the demo".
Reply
Popularizing such a term would just make it more fun to ridicule bad behavior, and maybe make folks just a little more aware of their own bad behavior, lest they get ridiculed.
You know, much like the "It's not a bug, it's a feature!" mantra that mocks developers who are so difficult when it comes to fixing their broken crap that they try to convince their customers that the software is "working as intended", even if that makes no sense because it is horribly broken.
I like this idea, thedailywtf.com would probably catch-on to it if they were presented with a story to publish that used the analogy. There could even be little fly stickers to put on your monitor to signify how many flies you've killed before swallowing them!
Reply
It's meant for a single developer who is designing himself in circles or coding himself into a corner because his initial solution to some small problem was wrong, and as he runs into new issues, he adds new shitty hacks to just make it work, etc.
It's more a short term-- say days or weeks, not months-- kind of scope.
I run into this *constantly* with interns; they make one bad decision but then they don't have the experience to notice that everything suddenly got complicated and hard because of that one decision. Maybe EVERYTHING is already complicated and hard to an intern, so they don't realize their mistake.
I'm not sure :)
Reply
Leave a comment