Kurt Mackey
๐ค SpeakerAppearances Over Time
Podcast Appearances
we tend to see, you know, higher satisfaction with more junior developers, right? People who just don't have a frame of reference yet on what is good, right? They're still, they're new to the profession. So there's certain things that if we just looked at this data, it might be that the 20% happy are coming from, you know, certain countries or,
we tend to see, you know, higher satisfaction with more junior developers, right? People who just don't have a frame of reference yet on what is good, right? They're still, they're new to the profession. So there's certain things that if we just looked at this data, it might be that the 20% happy are coming from, you know, certain countries or,
certain levels of tenure and seniority, that could explain quite a bit of that 20. I mean, and some of them are probably legitimately in good situations with good developer experience and greenfield projects with no technical debt where they're really happy.
certain levels of tenure and seniority, that could explain quite a bit of that 20. I mean, and some of them are probably legitimately in good situations with good developer experience and greenfield projects with no technical debt where they're really happy.
That's how I've heard this described. How can you kind of get the same feeling of joy and flow that you do when you're working on a side project? How do you get that same experience while working in your job? How can you recreate that? And if we could do that, we would unlock a lot more productivity. We would get a lot more out of engineers working at our companies. Yes.
That's how I've heard this described. How can you kind of get the same feeling of joy and flow that you do when you're working on a side project? How do you get that same experience while working in your job? How can you recreate that? And if we could do that, we would unlock a lot more productivity. We would get a lot more out of engineers working at our companies. Yes.
I think that's a good way to think about it.
I think that's a good way to think about it.
We do that.
We do that.
That's already, yeah. For every organization we work with, that's one of the... So first, we capture the data on it, and then based on... how they you know kind of stack up on each of the 14 we give them hey like based on here's how you answered these 14 now out of these 14 what are the top one to three that you know would most benefit your productivity
That's already, yeah. For every organization we work with, that's one of the... So first, we capture the data on it, and then based on... how they you know kind of stack up on each of the 14 we give them hey like based on here's how you answered these 14 now out of these 14 what are the top one to three that you know would most benefit your productivity
There are definitely certain ones that tend to float more toward the top.
There are definitely certain ones that tend to float more toward the top.
Documentation.
Documentation.
For sure. Yeah. What's interesting is, you know, the Stack Overflow kind of technical debt is not one thing, right? Technical debt is actually like all 14 of these things. Well, minus maybe two or three of them are actually types of technical debt, right? So documentation is actually a form of technical debt. Complex code is a form of technical debt. Slow CI CD is a form of technical debt.
For sure. Yeah. What's interesting is, you know, the Stack Overflow kind of technical debt is not one thing, right? Technical debt is actually like all 14 of these things. Well, minus maybe two or three of them are actually types of technical debt, right? So documentation is actually a form of technical debt. Complex code is a form of technical debt. Slow CI CD is a form of technical debt.
So all the technical factors do tend to float toward the top. Actually, but some of the cultural fact, you know, cross-team collaboration, like delays due to different teams having to coordinate with one another is also, I'd say, a pretty common theme. Makes sense.
So all the technical factors do tend to float toward the top. Actually, but some of the cultural fact, you know, cross-team collaboration, like delays due to different teams having to coordinate with one another is also, I'd say, a pretty common theme. Makes sense.