|
|
|
|
|
by logfromblammo
4338 days ago
|
|
One man's grind is another man's passion. I'm usually the only one on any team that is willing to sit down with "that tool", written by some guy who left the company years ago (maybe using VBA Excel or Access macros because he wasn't actually a trained programmer), and understand it to the point that I can fix just one piece of it without rewriting the whole thing from scratch. And then I can recommend ways to wean the company's process away from that sort of fragile dependence on unmaintainable code. But that kind of work is not for everyone. A lot of the time, people don't even like the smell of the code they wrote themselves only a few months ago, so slogging down in the sewers of the ex-COO's magic Excel spreadsheet would be absolute torture. I see it less like an undercity diver busting up grease clots in the drains, and more like a surgeon carefully and methodically removing colon polyps before they go malignant. And I am burning out here because I have been explicitly ordered to not fix anything without prior permission. Ordinarily, I would be spending some time every day safely refactoring old code and eliminating dead code. But SLoC is a management metric here. Reducing the total lines of code would upset the applecart. |
|
God... what a horrifying situation. That seems like exactly the opposite of what management should be doing. I get satisfaction when I can refactor copy/paste, unparameterized code with something more concise and easily testable. I hope you find a better place to be soon.