Content doesn't always have to target buyers. A CTO writing about AI infrastructure might not attract customers, but it builds a powerful employer brand that attracts top engineering talent, a valid business goal.

Company lore and the 'why' behind technical decisions often disappear when employees leave. An AI agent can analyze the entire codebase and its commit history to answer questions and reconstruct narratives, effectively turning your repo into a searchable archive.

When hiring senior engineers, the crucial test is whether they can build. This means assessing their ability to take a real-world business problem—like designing a warehouse system—and translate it into a tangible technical solution. This skill separates true builders from theoretical programmers.

Simply passing unit tests (like in SWE-bench) is a weak signal of a coding AI's usefulness. A far better evaluation is whether a senior engineer would actually merge its solution into the main codebase. This holistic judgment accounts for code patterns, test quality, and architectural consistency, which current benchmarks miss.

When hiring senior technical talent, the most valuable skill isn't just coding proficiency but the ability to take an abstract business problem—like designing a logistics system—and translate it into a functional technical solution. This skill demonstrates a deeper understanding that connects work to real-world value.

Theoretical knowledge is now just a prerequisite, not the key to getting hired in AI. Companies demand candidates who can demonstrate practical, day-one skills in building, deploying, and maintaining real, scalable AI systems. The ability to build is the new currency.

When contractors complain they can't find good people, it's often a culture problem, not a talent shortage. A great workplace turns existing employees into recruiters who attract other high-quality talent from their networks, creating a self-sustaining recruitment pipeline.

When hiring, focus on what a person has created, not their stated attributes or background. A great "invention" (a project, a piece of writing, code) is the strongest signal of a great "inventor." This shifts the focus from potential to proven output, as Charlie Munger advised.

Countering the "quality over quantity" mantra in software engineering, Robinhood's internal data reveals a positive correlation between the number of code lines contributed and the quality of that code. This suggests that top-performing engineers excel in both volume and craftsmanship.