Never end
-
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
It reminds this proverb. Become addicted to constant and never-ending self-improvement.
Regards, Koushik. Most people never run far enough on their first wind to find out if they've got a second. Give your dreams all you've got and you'll be amazed at the energy that comes out of you.
-
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
At my last place:
- The original gimps that designed the system left. No loss.
- A senior dev was sucked in, he said the system was unworkable, no-one listened.
- I was sucked in as I was a "safe pair of hands to get the job done". I agreed with above's opinion.
- I left.
- The other senior dev left.
- Another senior dev was sucked in. He left.
- The .net Manager left.
The .net team was peaked at about 15 members, it is now about 7, it wasn't the better devs they kept by-and-large..
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
neogeos wrote:
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
Hi Neogeos, Then programmer redundancies are superfluous as application and user converge on quantum states which are entangled as they approach unemployment. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
-
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
Welcome to real life as a developer.
Software Zen:
delete this; -
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
Never Ending Employment and no rest to Developers, always coding and fixing their Bugs.
Regards, Koushik. Most people never run far enough on their first wind to find out if they've got a second. Give your dreams all you've got and you'll be amazed at the energy that comes out of you.
-
Never Ending Employment and no rest to Developers, always coding and fixing their Bugs.
Regards, Koushik. Most people never run far enough on their first wind to find out if they've got a second. Give your dreams all you've got and you'll be amazed at the energy that comes out of you.
I don't have bugs. I also write the manual: if it is in the manual, it's a feature, not a bug. :-D
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
-
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
It's called "job security". Be happy that you have it, or quit and find other work - like running the machine that puts ridges on the sides of checkers...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
Wally : is there any way to tell a difference in working on ever changing product and not working at all. Dilbert : My life is a deadly spiral of failure. :rolleyes:
-
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
Given that what you describe is the norm, I'd rather know what happens when the opposite occurs. It'd be nice to see it happen -- just once, like.
I wanna be a eunuchs developer! Pass me a bread knife!
-
What happens when the application becomes an endless cycle of changes as the user of the application is not decided on what you really need, because people who made the initial request or use cases to gather information, not did quite well?
Scope creep
Craigslist Troll: litaly@comcast.net "I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson
