tomquirk

The answer to this is to shift left into product/design.

Sure, I'm doing less technical thinking these days. But all the hard thinking is happening on feature design.

Good feature design is hard for AI. There's a lot of hidden context: customer conversations, unwritten roadmaps, understanding your users and their behaviour, and even an understanding of your existing feature set and how this new one fits in.

It's a different style of thinking, but it is hard, and a new challenge we gotta embrace imo.

Opencode

Not sure if they're still doing it, but GitLab does the code review interview, and I too really liked it.

Before the interview, you clone the repo and get the app running on your machine.

For the first half of the interview, you review a pull request in real time. There's a mix of obvious and non-obvious callouts. And the second half, you actually implement your suggestions.

Honestly the code review portion alone is a great indicator of a dev's experience and soft skills.

Taking it for a spin today

hey kev quirk i'm tom quirk. great article!

I appreciate your opinion. And maybe there is some truth to your statement.

But in the professional context, none of that really matters IMO. If someone in your team is offended (and yes, it might seem stupid to you), then the dynamic of the team is thrown off. And ultimately, productivity suffers. That's how I'm thinking about it these days.