Podcast Appearances
So I associate it to a much bigger, beefier computer.
That has many Tmux sessions going, one for each project, NeoVim as my editor, and then OpenCode.
It's usually split in half, so NeoVim on the left, OpenCode on the right, and I'm going between the two.
So yeah, Tmux, Arch, NeoVim, OpenCode.
Yeah, I think I'll tell you something that I've heard.
And I think on one hand, this makes sense.
On the other hand, I'm not too sure about it.
I think these teams are now looking at themselves as, okay, what's the role of an engineer now?
If you're not going to write the code, what do you do?
Your role maybe is to figure out how to make it easy to ship code that is
to safely ship code, right?
Set up guardrails so that someone prompts an agent to do something, it's not introducing a bug.
Make sure your testing story is good.
Make sure there's proper conventions and patterns in your code base that agents can follow so they're not adding something that's really crazy.
So your role ends up being more like, how do I set up the right guardrails to make it so someone that
is using an agent can kind of blindly ship something that works well.
Whether it's another engineer, it could be your marketing team that is trying to ship a change to your website.
How do you make it safer to make changes?
And this is like the novel way that everyone is kind of looking at engineering teams.
The thing that I find interesting is that that's not novel.