3 ms·

It's also worth thinking about the timeline inclusive of hiring delay. More detailed requirements makes hiring slower. I know 2 startups both hiring their firs

It's also worth thinking about the timeline inclusive of hiring delay. More detailed requirements makes hiring slower. I know 2 startups both hiring their first set of non-founder engineers. One startup took 4 months to hire 2 senior engineers who weren't in their stack and then gave both of them about a month to come up to speed on the tech. Literally running tutorials. So 5 months in, they have two onboarded senior engineers. The other startup is 6 months in and hasn't made either hire. They see deep experience in their tech stack as required and don't want to wait longer for onboarding. But in retrospect, they would have gotten to an onboarded team faster if they had hired like the first company.

sicksid 5y ago
yes very interesting take indeed, sometimes it is worth knowing also if your stack is too complicated that you truly need someone already trained, I have had that situation where I entered a job where I already knew the stack but the code was organized in a way with so many opinions that took me longer to understand and follow them in order to make meaningful contributions the staff developer had very narrow experience doing software and made almost everything he wanted in a "library" way or in a "micro service" way until he got bored and started doing mono repos because of this the CEO or founder, had a very bad impression on hiring and of course it was unrealistically to hire someone who had experience in the stack and in dealing with the ego of a lone wolf programmer which I believe can be as high as a Hollywood artist some times