3 ms·
> git blame tells you nothing about the skillset it takes to be successful at any large tech company at a senior level 100%. I don't care who has "scope" or "i
by tppiotrowski 4y ago
> git blame tells you nothing about the skillset it takes to be successful at any large tech company at a senior level
100%. I don't care who has "scope" or "impact" or is "senior". I want to sit next to the developer I can ask about the pro/cons of any web development framework, that can help me analyze a heap dump, or explain why some transitive dependency is getting pulled in at compile time.
These are the ones I'm successful finding with git blame. They're the ones that can help me get stuff done.
- scarface74 4y agoWhen the big wigs are calling people into the room to lead technical discussions with their largest customers or potential customers, they aren’t going to go through your repos and see who had the best code.
- spoils19 4y agoPrecisely. I once had a really good architect who could design resilient, scalable systems that had a large positive impact to the company. Want to know what the problem was? He had no git commits for the last 6 months, so when I ran git blame over our repositories, I couldn't judge how he could analyze a heap dump.