Culture
Generative AI Is Not Going to Build Your Engineering Team for You 11 minutes read.
"Let’s start here: hiring engineers is not a process of "picking the best person for the job". Hiring engineers is about composing teams. The smallest unit of software ownership is not the individual, it’s the team. Only teams can own, build, and maintain a corpus of software. It is inherently a collaborative, cooperative activity. [...] The best teams are ones where no one is bored, because every single person is working on something that challenges them and pushes their boundaries. The only way you can get this is by having a range of skill levels on the team." -- Charity Majors is spot on. The problem I see often with hiring for Junior Engineers is that we don't know how to check for potential and drive. We hire someone with no experience (obviously) but also with no hunch on their learning curve, no expectation setting, and then create a full picture based on that, "we shouldn't even bothered hiring them, we need Senior engineers."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Andrej Karpathy, Who Worked Directly Under Elon, Explains 4 Ways Elon Runs His Companies Differently 4 minutes read.
The entire thread is fascinating and unique in our industry. Many of us will agree and even think, "Yes, we're doing the same," but it's often hard to act on that. "We have so much work to do, how can we let go of someone now?" or "It will take me months to replace them, so maybe it's good enough." But this is my favorite: "A company usually goes through tons of exercises and documented procedures to solve an issue. But when Elon learns of them, he tries to solve immediately."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Async Code Reviews Are Choking Your Company’s Throughput (Video) 72 minutes read.
Fascinating talk by Dragan Stepanovic. Co-creation process (e.g. Pair programming) can improve the team's effectiveness around challenging projects. If you plan and work on a project with someone else, set tasks you should do together due to the complexity or context required. The most important thing is to ensure that the number of projects the team is working on simultaneously is smaller than team size / 2.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.