Issues...Problems...
-
Hi All, The project I am working on is a trifle how is the best way of saying this 'problematic'. It has been running for a long period of time, management and accounts concerned, chewed through staff members none of the original design team are here now. That is the problem, we are now playing 'wack a mole' with bugs, there is an issue underlying I am sure of it. As it has changed designers so many times I think the phrase "It almost works, it nearly done" to be "It doesn't work right, I am leaving It's someone else's problem". Stuff has been built on a Shakey foundation and is now teetering on collapse, but I am not allowed to go looking into stuff that works to try to find the issues as it has been signed off. :omg:
-
Hi All, The project I am working on is a trifle how is the best way of saying this 'problematic'. It has been running for a long period of time, management and accounts concerned, chewed through staff members none of the original design team are here now. That is the problem, we are now playing 'wack a mole' with bugs, there is an issue underlying I am sure of it. As it has changed designers so many times I think the phrase "It almost works, it nearly done" to be "It doesn't work right, I am leaving It's someone else's problem". Stuff has been built on a Shakey foundation and is now teetering on collapse, but I am not allowed to go looking into stuff that works to try to find the issues as it has been signed off. :omg:
My "issues" can usually be traced to lack of visibility; putting off that dashboard or "log" I know the app needs. Like driving with an oil light only. (And the bulb may be burned out.)
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Hi All, The project I am working on is a trifle how is the best way of saying this 'problematic'. It has been running for a long period of time, management and accounts concerned, chewed through staff members none of the original design team are here now. That is the problem, we are now playing 'wack a mole' with bugs, there is an issue underlying I am sure of it. As it has changed designers so many times I think the phrase "It almost works, it nearly done" to be "It doesn't work right, I am leaving It's someone else's problem". Stuff has been built on a Shakey foundation and is now teetering on collapse, but I am not allowed to go looking into stuff that works to try to find the issues as it has been signed off. :omg:
That sounds so much like the situation where I am working... And no one wants to dig into this archeological dig of a mess to find the underlying causes...
-
My "issues" can usually be traced to lack of visibility; putting off that dashboard or "log" I know the app needs. Like driving with an oil light only. (And the bulb may be burned out.)
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
Like when you get that "engine" light on the dashboard, but just ignore it....
-
Hi All, The project I am working on is a trifle how is the best way of saying this 'problematic'. It has been running for a long period of time, management and accounts concerned, chewed through staff members none of the original design team are here now. That is the problem, we are now playing 'wack a mole' with bugs, there is an issue underlying I am sure of it. As it has changed designers so many times I think the phrase "It almost works, it nearly done" to be "It doesn't work right, I am leaving It's someone else's problem". Stuff has been built on a Shakey foundation and is now teetering on collapse, but I am not allowed to go looking into stuff that works to try to find the issues as it has been signed off. :omg:
Long ago I rather enjoyed fixing bugs in other people's code. Send the code to me. Maybe I'm still good at it.
-
Hi All, The project I am working on is a trifle how is the best way of saying this 'problematic'. It has been running for a long period of time, management and accounts concerned, chewed through staff members none of the original design team are here now. That is the problem, we are now playing 'wack a mole' with bugs, there is an issue underlying I am sure of it. As it has changed designers so many times I think the phrase "It almost works, it nearly done" to be "It doesn't work right, I am leaving It's someone else's problem". Stuff has been built on a Shakey foundation and is now teetering on collapse, but I am not allowed to go looking into stuff that works to try to find the issues as it has been signed off. :omg:
This is also called the project death march. You need an enemy to make hard decisions. No one wants to own up to the mess. My very first contract job was with a DMV processing company. I got settled in, did my work, poked around and came across a couple of boxes of Project Zeus. Going through it, it was high level OO design out the wazoo to replace a functioning system. After reading a bit, I asked the VP who ran my group about Project Zeus. He got a very concerned look on his face.... The story goes on from there. This project went through a full year of design. Mind you design. Not at one time did the whiz kids ask the grunts who knew the working system how things worked. Slip after slip, finally the head VP said, when am I going to have a working system? The week before that date, the entire team quit. Five years later, I come along. This place did have one nice feature - it had a cafeteria and cooks that could cook. Excellent blueberry pancakes. So, I'm sitting there eating my breakfast and the VP comes up, sits down just to chat. He says, "you know, we're thinking about shutting this product down...." me: "Why?" Him: "Well it's not new tech." me me: "I'll buy it." Him: "what?" me: "you heard me. What's your price?" Him: "haha, you're joking.." me: "nope, point me in the right direction." last I heard it's still running in the corner making millions.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Hi All, The project I am working on is a trifle how is the best way of saying this 'problematic'. It has been running for a long period of time, management and accounts concerned, chewed through staff members none of the original design team are here now. That is the problem, we are now playing 'wack a mole' with bugs, there is an issue underlying I am sure of it. As it has changed designers so many times I think the phrase "It almost works, it nearly done" to be "It doesn't work right, I am leaving It's someone else's problem". Stuff has been built on a Shakey foundation and is now teetering on collapse, but I am not allowed to go looking into stuff that works to try to find the issues as it has been signed off. :omg:
I totally agree with @OriginalGriff, time to quietly move on. But, just for laughs, this situation always reminds me of this: Abbott & Costello - YouTube[^]
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
-
Hi All, The project I am working on is a trifle how is the best way of saying this 'problematic'. It has been running for a long period of time, management and accounts concerned, chewed through staff members none of the original design team are here now. That is the problem, we are now playing 'wack a mole' with bugs, there is an issue underlying I am sure of it. As it has changed designers so many times I think the phrase "It almost works, it nearly done" to be "It doesn't work right, I am leaving It's someone else's problem". Stuff has been built on a Shakey foundation and is now teetering on collapse, but I am not allowed to go looking into stuff that works to try to find the issues as it has been signed off. :omg:
"It's nearly done" has been the mantra of most programming teams since I have been in the business (1994). What happens is that teams always do the easy stuff first. Naturally and with management's glowing approval and encouragement. So of course the "almost done" parts are the parts that noone has yet figured out how to do. This scenario will not change until programming managers wise up, and insist that teams COMPLETE THE HARD PARTS FIRST. And LOL, good luck with that...
-
"It's nearly done" has been the mantra of most programming teams since I have been in the business (1994). What happens is that teams always do the easy stuff first. Naturally and with management's glowing approval and encouragement. So of course the "almost done" parts are the parts that noone has yet figured out how to do. This scenario will not change until programming managers wise up, and insist that teams COMPLETE THE HARD PARTS FIRST. And LOL, good luck with that...
Member 9625785 wrote:
COMPLETE THE HARD PARTS FIRST
All such broadly sweeping statements are problematic.
-
Member 9625785 wrote:
COMPLETE THE HARD PARTS FIRST
All such broadly sweeping statements are problematic.
Including broad statements about broad statements I presume?
-
Including broad statements about broad statements I presume?
Yes, those are the broadest statements of all. It's like broad squared.
