Anyone ever heard of 'Banana Software'?
-
... it s phrase for software that ripens at the customer site! Great, isnt it! Man, we make so much of that crap. No requirements, middle management never talking to the customer, making up what they think the market wants, and then, after the nth rework, it finally workis intime for the next product to come out and repeat the whole sorry story again. And all the time deadlines for the next fix in a weeks time with no chance to test it because the other 20 gazillion products need there slice of fire fighting too! Fucking middle management assholes!
Truth is the subjection of reality to an individuals perception
-
... it s phrase for software that ripens at the customer site! Great, isnt it! Man, we make so much of that crap. No requirements, middle management never talking to the customer, making up what they think the market wants, and then, after the nth rework, it finally workis intime for the next product to come out and repeat the whole sorry story again. And all the time deadlines for the next fix in a weeks time with no chance to test it because the other 20 gazillion products need there slice of fire fighting too! Fucking middle management assholes!
Truth is the subjection of reality to an individuals perception
Isn't that the precursor to Boomerang Software. No matter how many times you adjust it and throw it out there it just comes straight back and smacks you in the head.
Nothing is exactly what it seems but everything with seems can be unpicked.
-
Isn't that the precursor to Boomerang Software. No matter how many times you adjust it and throw it out there it just comes straight back and smacks you in the head.
Nothing is exactly what it seems but everything with seems can be unpicked.
It's what I call the "Albatross Effect". You release it, and from that day forward you spend most of your time wishing it would leave you alone. Once the problems begin, you end up working so hard to support your customers that you have no time left to do the ground-up rewrite that would fix the underlying problems. I've seen this happen again and again--at the same company, even--and software producers just never seem to learn. The old saying about how anything that is worth doing is worth doing well applies doubly to software development.