March 2, 2017 at 8:55 am
Sergiy - Thursday, March 2, 2017 6:23 AMGary Varga - Thursday, March 2, 2017 5:30 AMName the rate?
The rate I am paid? No. That is not going to happen. It is client confidential for a start.
The rate of decrease in defects? Sorry, I can't measure both what has and hasn't happened.
The rate per defect or per defect not created? I don't get paid that way.The rate you've paid for not fixing your software because you did not leave any issues in it.
Gary Varga - Thursday, March 2, 2017 5:30 AMI disagree as I in my experience those that create loads of defects are often got rid ofReally?
Actually, they form a support team, communicate with customers, run daily scrum meetings, measure average issue resolution time, report team members kpi upstairs, etc.
Because if business will get rid of them then during several months while a new developer will dig through unmanageable code looking for errors the business will simply lose all clients and go down.and those that produce less are kept
Kept for what exactly?
If everything working fine and does not require daily attention from the IT guy, and it was thought through, so increased scale, new data would not cause any faults/issues - what to keep that employee for? Would any kind of stakeholders approve such an expense?
I don't think so. They'll get rid of such a developer as soon as they sure the software does not have any serious issues.
My experience cannot be invalidated just because it differs from yours.
It sounds like you are suggesting that failed developers become project managers, support staff and project coordinators. Whilst I have seen that happen on occasion, these are professions in their own right and it is doing them a disservice to suggest otherwise. Though it may be the way it works in your experience.
Kept for what? Well let me be the first to congratulate you on finding the one place with a single piece of software where the feature set has been permanently fixed that meets all the business requirements past, present and future. Everywhere else I have been everyone is busy (often more work than capacity).
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 2, 2017 at 5:53 pm
Gary Varga - Thursday, March 2, 2017 8:55 AMMy experience cannot be invalidated just because it differs from yours.It sounds like you are suggesting that failed developers become project managers, support staff and project coordinators. Whilst I have seen that happen on occasion, these are professions in their own right and it is doing them a disservice to suggest otherwise. Though it may be the way it works in your experience.
Kept for what? Well let me be the first to congratulate you on finding the one place with a single piece of software where the feature set has been permanently fixed that meets all the business requirements past, present and future. Everywhere else I have been everyone is busy (often more work than capacity).
Of course they are busy!
Work expands so as to fill the time available for its completion
Read the book.
You might start recognizing the patterns around you.
🙂
_____________
Code for TallyGenerator
March 3, 2017 at 5:27 am
Fully aware of Parkinson's Law. Thanks.
Nice that you live in a static world. I am very jealous.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 3, 2017 at 3:11 pm
There is no such thing as "static world". Who told you such a nonsense?
_____________
Code for TallyGenerator
March 9, 2017 at 5:37 am
Sergiy - Friday, March 3, 2017 3:11 PMThere is no such thing as "static world". Who told you such a nonsense?
You did.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 9, 2017 at 6:01 am
March 14, 2017 at 5:29 am
Sergiy - Thursday, March 9, 2017 6:01 AMI surely did not.It must be your too vivid imagination.:-)
...
If everything working fine and does not require daily attention from the IT guy, and it was thought through, so increased scale, new data would not cause any faults/issues - what to keep that employee for? Would any kind of stakeholders approve such an expense?
I don't think so. They'll get rid of such a developer as soon as they sure the software does not have any serious issues...
You can only get rid of all the developers if there is nothing to change i.e. static. 🙂
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 2, 2026 at 8:47 am
Back in 2017, I would have agreed with this 100%, but there are edge cases. There's the joke about 2 senior managers talking about their DBAs. One says, "My DBAs don't seem to do much, I'm thinking of letting one go". "Do you have problems with your databases?" the other asks.
No.
"Then double their salary", the 2nd one says.
I've heard the term arsonist fire-fighter in the context of software engineering. The perception up the management chain is that someone is a superhero for putting out all the fires, but never asking why there were fires in the 1st place.
The big problem for those who do a good job quietly is that they are invisible. If you are invisible, are you valued?
How do you increase your visibility without being an arsonist firefighter?
March 4, 2026 at 3:16 am
For me, I point out things I've did and give an analysis of what could be better, or would have prevented issues.
The more I document and point things out, the more visible I can be. I might not get them changed, but people start to know I see the system and its flaws.
Viewing 9 posts - 31 through 39 (of 39 total)
You must be logged in to reply to this topic. Login to reply