Probably more accurately titled "Bay Area Tech is a Small World After All"<p>TLDR: Chekr Director of Solutions, formerly Director of Strategic Sales (and first business hire), starts client on-boarding company (nice idea, streamline a lot to minimize hand-holding).
> Hiring people that have a track record of taking projects from inception to delivery and who actively seek out projects to own is critical<p>Doesn't that regard the first few early hires (who'd take some form of senior/management positions later on)? For me a person who delivers projects means somebody who's very involved in the process; somebody that calls significant decisions about the product.<p>Should all hires be like that? Isn't being able to execute the tasks you're assigned enough?
What exactly is meant by "commits" that you talk about in 1:1 and meetings? Is that more like "commitments" or "git commits". The former I agree, the latter I think is in many cases a terrible measure of productivity, because it discourages activities that don't directly lead to code, such as pairing with your junior, or helping a customer, or providing mentorship for others, etc. Remember you'll get what you measure.
I thought that since this author's startup is sorta a 'reddit for politics', I'll plug my own startup (currently self-funded) which is a 'chatroulette/duolingo for politics': <a href="https://dinnertable.chat/" rel="nofollow">https://dinnertable.chat/</a>