The advent of general coding AI assistants almost immediately changed how I think about hiring and interviews.
In the software engineering world, this mindset shift was psychologically easy for me, because I’ve always had a bias against the types of coding questions that AI can now answer near-perfectly. And they also happen to be the kind of questions I personally do badly at - the ones requiring troves of knowledge or rote memory of specific language capabilities, libraries, and syntax. It is not so psychologically easy for everyone, especially those who have developed a core skill set of running or passing “leetcode-style” interviews. Even before AI, the only types of coding questions I would personally ask were things that simply evaluate whether a candidate is lying or not about whether they can code at all, which was and still is surprisingly common. I have interviewed people that list bullet points like 7 years of Java experience but can’t pass a fizz-buzz like question, and this was a question I gave out on paper with a closed door and no significant time pressure.
June 29, 2025 · 6 minutes · Read more →
The “Human Joystick” is an experimental VR movement system in which the player moves through the virtual environment by changing their physical location within their VR “playspace”.
January 1, 2020 · 3 minutes · Read more →