Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I was a noob at the time and had assumed he was a minimum of 1 year experience better than me and really knew what he was talking about. He used great business terms and convinced the non-techies, too. In retrospect, it's a very obvious mistake. He convinced us the open source project that we based our business on for the 6 months before hiring him had limitations, but it turns out that the open source project was packed full of features, well polished, well designed, easily extensible, etc. and we spent 2 years catching up to where that product was, just in a different framework.


In 2011 we had to rewrite a backend which was architected by a guy who left after his plan didn't work which was effectively a rewrite of the rewrite. I left the company in 2013 and in 2014 they hired him at my new workplace (we had no contact before and this decision was oblivious for me). I left that company when they put him as team lead on my team and several years later I heard from an ex-colleague that they dumped a backend which was architected by this guy.


Very similar story to mine! :) I was hired together with a guy like this, knew all the fancy keywords and didnt want to touch the old code. We were lucky to refuse him, but it was just by chance. He left the company few months later.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: