3 ms·

>the root problem is not in his tech skills. It doesn't seem to me like there was a root problem. There were several. The primary problems being that he was a

>the root problem is not in his tech skills. It doesn't seem to me like there was a root problem. There were several. The primary problems being that he was a bad developer, an asshole and non-cooperative. He wrote idiosyncratic bad code, copy pasta and documented nothing - that wasn't about him being an asshole - that's a lack of basic tech skills. Those are actually the things that led to the company not being able to deliver. I know plenty of perfectly nice junior developers who have done the same thing and if unchecked it causes the same problems they experienced. It doesn't say it, but it's strongly implied that it wasn't just others that had a problem understanding and maintaining his code because of his poor skills - he likely inadvertently made it difficult for himself too.

watwut 9y ago
I hear you, but those failing happen to pretty much everyone who overworks himself too much and don't have feedback. You loose sigh of it, because your brain get it. And you are tired and sleep deprived. Everyone makes mess occasionally and we should not judge people by their worst performance. (Meaning here that he produced both bad and good code). When he did get initial good reputation, he was able to solve problems, he was able to help etc. I think that we should not expect perfection of him nor we need to convince ourselves that he was completely incapable. He was unable to estimate how much time will maintenance of everything take and from there on, he could not win.