|
|
|
|
|
|
by al_borland
782 days ago
|
|
|
You got a job, did the job, got recognized and promoted for doing a good job… and did it all without adding needless complications to the project just to stroke your own ego and say you implemented it with feature X. How is this bad? I had a guy on my team who we all thought was amazing. He always knew the newest tech and tools, he’d spend his nights and weekends learning all the stuff. Once he left it was complete hell to maintain. He used all these unnecessary integrations, which meant more points of failure, more language hopping, and multiple learning curves for seemingly simple things. He also re-implemented custom version of systems supplied and maintained by other teams in the company… which meant more learning curves and less support… again, with no real benefit other than it helped him learn. His code was also hard to read, with horrible variable names (var1 - var14) or needless abbreviations that required an Enigma to make sense of. We have completely rewritten some of the things that need to stick around, and others are being subset. What we have left is much less complex and easier to maintain. Nothing is hidden away in systems no one really knows about. It’s never good with your technical ambitions come at the expense of your team and what you’re building. It sounds like you were able to do it the right way, even if you didn’t mean to. |
|
|
BTW: For all this "damage" to the code to have happened and only being spotted after the dev left... How was this able to occur?
(I assume no code reviews? Lots of solo programming?)