I'm the head of engineering at Tegus. I write about politics, psychology, and software.
Over the last 4 years I’ve interviewed hundreds of engineers, first as a manager at a large company and then as the head of engineering at a startup. I believe in and heavily use pair programming interviews, in which the candidate and interviewer work through a small programming problem together.
Most history, from the high drama of Thucydides to the folk history of, say, the computing industry, focuses on the highlights and the standouts: the Gates, Jobs, and Zuckerbergs. In The Computer Boys Take Over , Nathan Ensmenger does the opposite - he tells the story of the emergence of the computer industry through the anonymous legions of men and women working as programmers, coders, system…
Most writing on management includes a paean to the importance of hiring the right people, the best people, who will differentiate the organization from the rest and make dreams come true. Despite widespread agreement on the importance of hiring, I haven’t seen anything on how to actually do it - how to go out and build a top team.
I recently saw both Lady Bird and Love, Simon , two movies that focus on the difficulties of being a teenager and navigating high school. They’re both good movies - not to skip too far ahead, but in my opinion Lady Bird is actually a great movie - and their overlapping topics and time in theaters makes a comparison feel natural.
When I was learning to be an engineer, people told me two different stories about application performance. The first was that while it’s fun to work on, don’t spend too much time on it unless you have to - premature optimization and all that . The second was that really, though, it’s good to have a fast system because users like fast systems - that is, performance is a feature . But when it’s all…
Interviewing developers is difficult and, what’s worse controversial. Rather than spill ink on how to interview a candidate, I want to cover a few mistakes I see people make when making hire/no-hire recommendations after an interview.
Progress in the field of software development occurs when developers invent technical solutions to problems caused by their own laziness, lack of discipline and mediocrity. Or, to put it more kindly, when we repeatedly prove that we can’t be trusted to do something, we invent a way to avoid doing it. This is a good thing.
Since November of last year I’ve been trying to lose weight. I didn’t start trying at a moment of personal crisis or anything like that; I was just frustrated with my health and appearance and decided to make a serious effort. The previous attempts I’d made at weight loss boiled down to going to the gym a bit more and had no real impact. I had never tried dieting. But, sitting around in my…
Hearthstone , the online card game by Blizzard, is well known for its exciting gameplay and huge community. I’d hold it up as a real triumph of game design; it’s well balanced, fast and fun. Beyond individual card design, though, Hearthstone stands out thanks to some subtle but powerful decisions the developers made about how the core of the game works. In this blog post, I’ll examine one such…
A few hours ago, !!con wrapped up. It was fantastic. Often I leave conferences having learned something, but tired and ready for the weekend. Writing this from the plane, I feel filled with excitement and energy.