Another strategy to reduce ergodicity is diversification. It's implicitly treated in Luca's book but not explicitly mentioned. How would that translate in software development? I think modularity in code structure and cross functionality in teams would be important aspects.
"When you get a new idea, try over-apply it. That’s the only way you’ll find the boundaries of its application."
This throwaway comment deserves much more attention. There are many fads that come and go in software development. And an excellent way to test their value to your org or your project is to over-apply them and from that derive what benefits they bring and their limitations. IMHO this is the surest way of assessing the techhnology's value and drawbacks for *you*, rather than having experts/consultants tell you.
The overconfident, young developer in me would like to -think- I fit into the more ergodic side of things, but I honestly have to say that much of my work is probably non-ergodic. I think so because I asked myself, with respect to having skin in the game: Am I actually sitting in with other developers, sitting in with users? No. Much of the work at present is silo'd and detached from the result. I write tests, sure. I am even responsible for the system if it breaks (on-call). But I would argue that if I am detached from the users and the other players making the system, then I am probably working in a way that is more liable to hit that "Game Over" state.
So I suppose I ought to ask myself if I am able to do anything about that, and if I am, take notes of the least obstructive (to the wider community of the organization) way to put more of my own skin in the game.
However, you triggered me with "Programmers are on call for production support".
I completely get the positive intent of this idea, but have so often seen it abused by organizations that want to skimp on tech support, infrastructure planning, user training, etc. that seeing it without a LOT of qualification makes me see red.
Programmers definitely need to take professional responsibility for the resiliency of their apps, but for the world to be safe for programmers, they aren't the only ones who need more skin in the game!
Ergodic Development
Another strategy to reduce ergodicity is diversification. It's implicitly treated in Luca's book but not explicitly mentioned. How would that translate in software development? I think modularity in code structure and cross functionality in teams would be important aspects.
Very nice. Total common sense. When is the book being released.
"When you get a new idea, try over-apply it. That’s the only way you’ll find the boundaries of its application."
This throwaway comment deserves much more attention. There are many fads that come and go in software development. And an excellent way to test their value to your org or your project is to over-apply them and from that derive what benefits they bring and their limitations. IMHO this is the surest way of assessing the techhnology's value and drawbacks for *you*, rather than having experts/consultants tell you.
The overconfident, young developer in me would like to -think- I fit into the more ergodic side of things, but I honestly have to say that much of my work is probably non-ergodic. I think so because I asked myself, with respect to having skin in the game: Am I actually sitting in with other developers, sitting in with users? No. Much of the work at present is silo'd and detached from the result. I write tests, sure. I am even responsible for the system if it breaks (on-call). But I would argue that if I am detached from the users and the other players making the system, then I am probably working in a way that is more liable to hit that "Game Over" state.
So I suppose I ought to ask myself if I am able to do anything about that, and if I am, take notes of the least obstructive (to the wider community of the organization) way to put more of my own skin in the game.
> Everyone sits together (or is on frequent video calls) so user problems are immediately experienced by those who caused the problems.
I don’t understand how sitting together leads to experiencing problems faster. Could you elaborate?
Meta cognitive note is instructive. I agree. It's a good way to form life principles.
Hi Kent, great post, great concept!
However, you triggered me with "Programmers are on call for production support".
I completely get the positive intent of this idea, but have so often seen it abused by organizations that want to skimp on tech support, infrastructure planning, user training, etc. that seeing it without a LOT of qualification makes me see red.
Programmers definitely need to take professional responsibility for the resiliency of their apps, but for the world to be safe for programmers, they aren't the only ones who need more skin in the game!
Nice song. The style is too "high" to gain popularity.
Surface scratched. "Not dying...I always get a lot of mileage out of that..."
Coincidence? Not. Great breakdown of the song I quoted. https://www.tiktok.com/t/ZT8FvAXRG/