|
Correct - I am often amazed the exiting software worked.
Some years ago I spent 2 days fixing a recurring error through out the code base I inherited. My mistake was not doing them one at a time w/testing, because at least one out of the ~150+ warnings (actually a major coding error) broke code when the fix was applied. The code base still exists without the fix.
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
|
|
|
|
|
All of our project priorities are decided by a steering group
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
Oh - I'm so sorry for you.
Like pretty much anything else (car, ship, airplane), when you steer by committee you will be lucky if you just go 'round in circles instead of crashing into something.
I usually refer to "Steering Committee's" as a "Group Grope[^]".
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Do you mean a group of steers?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Leslie Lamport, well known in the field for more than a generation, at one conference gave the introductory speech for a panel discussion on "What can we learn from theory?". He opened by referring to one dictionary defining a "theory" as "a body of theors", and a "theor" as "a person who communicates directly with the gods". So, Lamport claimed, The question to be answered in this panel discussion is "What can we learn from a group of people who communicates directly with the gods?"
|
|
|
|
|
I actually left my first job due to the steering group. They repeatedly directed me/us to implement functionality that had been available for several releases, or functionality that made no sense whatsoever in the given context, and those who thought they knew programming prescribed how we should extend this and that data structure for a given functinality, but no such data structure had ever existed in the code. (I guess that fellow had been working on a similar system in another company, taking for granted that ours were made exactly the same way.)
Today, I guess I would have just nodded an OK, ignoring the detail directions, later presenting that old functionality as if it were new, and if they asked for the nonsense functionality, explained it to them then. But at that time when I was young and excited about my own expertise, I found it tremendously frustrating to receive orders from a steering group without a clue.
|
|
|
|
|
I think the survey focuses more on devs picking the project they work on (from a list of projects selected for implementation by the steering group).
/ravi
|
|
|
|
|
Right now I'm focusing more on choosing which projects not to work on.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
