Jerod

Well, I mean, 20 years later, it's still hard for you. So you expect that to change at this point?

Well, I mean, 20 years later, it's still hard for you. So you expect that to change at this point?

Well, I think if you did it more often, I think some of it is because of your proximity to the technology not being on all the time. There are certainly people who are writing front end and specifically doing the CSS that 40 hours a week, 60 hours a week. Could you imagine? You do anything that much? No. No. You do anything that much and it's going to become easy to you.

Well, I think if you did it more often, I think some of it is because of your proximity to the technology not being on all the time. There are certainly people who are writing front end and specifically doing the CSS that 40 hours a week, 60 hours a week. Could you imagine? You do anything that much? No. No. You do anything that much and it's going to become easy to you.

Well, then it's always going to be hard until you commit.

Well, then it's always going to be hard until you commit.

What has not changed?

What has not changed?

Right now we're doing things we haven't changed our mind about.

Right now we're doing things we haven't changed our mind about.

Thank you. So there's a few things I've been preaching for years and years and years and years, and I don't think I'll ever change my mind on them. And one of those is slow down to go faster. I have not changed my mind. I still think if you want to go fast, you have to slow down. And it sounds like a contradiction, but it's not because as you go slow over the course of time,

Thank you. So there's a few things I've been preaching for years and years and years and years, and I don't think I'll ever change my mind on them. And one of those is slow down to go faster. I have not changed my mind. I still think if you want to go fast, you have to slow down. And it sounds like a contradiction, but it's not because as you go slow over the course of time,

you end up going faster because you don't have to redo, rewrite, start over, or backtrack as often as if you were moving too fast in the first place. As Kelsey Hightower said it, let's see if I can remember his saying it was really cool as everything Kelsey says is cool. I think he said, do it right, do it light, do it wrong, do it long. And I tell that to my kids sometimes.

you end up going faster because you don't have to redo, rewrite, start over, or backtrack as often as if you were moving too fast in the first place. As Kelsey Hightower said it, let's see if I can remember his saying it was really cool as everything Kelsey says is cool. I think he said, do it right, do it light, do it wrong, do it long. And I tell that to my kids sometimes.

And they're like, what's that mean? I'm like, I don't know, but it sounds cool, doesn't it? Listen to this podcast, you'll get it. Yeah, you do it right, you do it light. You just slow down. You go faster. You know, it's the old tortoise in the air. And so much of the tech industry is focused on raw and utter speed.

And they're like, what's that mean? I'm like, I don't know, but it sounds cool, doesn't it? Listen to this podcast, you'll get it. Yeah, you do it right, you do it light. You just slow down. You go faster. You know, it's the old tortoise in the air. And so much of the tech industry is focused on raw and utter speed.

And we end up foot gunning, as they say, shooting ourselves in the foot repeatedly or shooting our teammates in the foot or the future developer who's replacing us because I've spent my 12 months and I'm moving on. And we end up churning and burning a lot of our colleagues because we're so focused on speed. And if you would just slow down.

And we end up foot gunning, as they say, shooting ourselves in the foot repeatedly or shooting our teammates in the foot or the future developer who's replacing us because I've spent my 12 months and I'm moving on. And we end up churning and burning a lot of our colleagues because we're so focused on speed. And if you would just slow down.

and take the break or write that additional test or look at the source code or don't abstract that method yet or you know insert your way of slowing down here that those small decisions over time lead to faster and i still believe that today and i think i wrote that blog post like 15 years ago so Yeah, that's one.

and take the break or write that additional test or look at the source code or don't abstract that method yet or you know insert your way of slowing down here that those small decisions over time lead to faster and i still believe that today and i think i wrote that blog post like 15 years ago so Yeah, that's one.