Programming Throwdown Episode 187,

Agentic Coding.

Take it away, Jason.

Hey, everybody. Okay, so quick intro topic here. I was talking to a lady. I won't use her name. Let's call her a Jane. I was talking to Jane, a friend of

mine. And she has been at her company, which is kind of like a hardware company. So it's not really

Jane's specialty. It's a hardware company that needs some software. Right. And, you know,

Jane's unhappy there. And there's all sorts of reasons why Jane's unhappy. It's understandable.

And she's at nine months. And so they have a one year cliff. And so she has to kind of tough it out for three more months. And it just made me think about vesting schedules because I think that companies, you know, haven't really thought this through.

There's like a cargo cult mentality where, you know, oh, this company did, you know,

this type of vesting schedule, so we're just going to copy them. And I think that some bad behavior has been copied. and when you start breaking it down,

it never really makes sense.

And so I'll start by criticizing the one year cliff.

You want to explain what it is though?

Not everybody.

Oh, yeah.

Okay.

So, okay.

If you're in, let's let's like wind it back.

If you're in, let's say sales, you get a commission, right? So you build a portfolio of companies that want, you know, some product and you get a commission. And if you're doing some service-based sales, then you could potentially get a commission every single year. You can have a customer that is going to use your service for the next 20 years,

but because you were the salesperson that got the deal, you will just keep getting commission

for 20 years, potentially. That's how sales works, right? And so for engineering and other

fields, you know, they want to have an incentive

...