Solving more than one problem at a time is where things go off the rails. For example, try solving a new problem in an unfamiliar programming language. Chaos will ensue. There is hope and I have some ideas to share below: 1. Create a design doc. The doc should contain the need, your approach, benefits, and costs (and perhaps alternatives). Use the document to ensure you are solving only one problem at a time. Keep in mind that docs aren’t the only way.

Whiteboard interviews are awkward and with more people being remote, it’s even worse now. For the past 22 months, I’ve been thinking about how to better assess candidates, and also be fair and accommodating at the same time. Here’s what I’m working on now 🧵 1. Depending on the seniority of the position, I’m looking for multiple things: Their level of capability, their ability and willingess to lead, adherence to company values, and the ability and want to collaborate with others.

These rap and tech tweets won’t stop. Because they can’t stop.

Imagine a well operating team. It’ll mirror what Wu-Tang Clan did. It’ll form like Voltron and you’ll have a Genius at the head. You’ll even have an ODB because every great team needs an ODB. The ODB great because there is “no father to his style”. This individual does great things outside of the status quo.