2 ms·
Of course if he just wrote bad spaghetti code with no boundaries, no tests, and that breaks everything from time to time, he'd have locked in the company, make
by henvic 7y ago
Of course if he just wrote bad spaghetti code with no boundaries, no tests, and that breaks everything from time to time, he'd have locked in the company, make other developer's experience a nightmare, and so on and get away with it.
I think this might explain a few things I have seen or heard about in my life.
- bryanrasmussen 7y agowell only if it was password protected bad spaghetti code, otherwise they would have had a better developer look at the spaghetti and unravel it. But he wouldn't have gotten any jail time.
- henvic 7y agoI'm thinking more about a 'soft lock-in' situation: the developer writes bad code, but not as bad that you need to start over or stop using it. Just bad enough that only they will understand it and other people who try to contribute will get mad and waste a lot of time and effort to deal with it, so in the end, the bad developer continues writing their shitty code because no one else wants to get involved (and there are plenty of opportunities elsewhere).