So I think an aspect of the software factory that intellectually feels right to me is some of the stuff around self-improving systems.
And I would say that's probably the closest to the bleeding edge that we're currently doing at work is...
And that takes the shape of usually things like, hey, PlanetScale can give us insights about our database and those can get fed in to open a pull request and certain conditions are met like that can just like auto merge, right? And so the idea is like, hey, we can build these loops of like self-healing or like self-improving systems.
But at the end of the day, like, you know, OK, we've we've resolved 50 different planet scale recommendations and like we like that didn't lead to any new customers.
Like maybe it has led to better database performance that, you know, you're like second or third order proxy of like, yeah, like we can scale up the system more or like we can run for longer without upgrading our cluster.
But I do feel like that is probably my biggest worry is that everyone is just like burning their like dopamine receptors on a bunch of low value stuff.
And then your brain just gets like turned to mush and you can't do the high value stuff because like I haven't I haven't I haven't sat deeply for like six weeks and like looked at a problem because I've just been, you know, babysitting low value snack agents.
Which, and I mean, going back first to the plant scale a bit, which I totally agree with and we do the same thing.
I would actually argue like that is where the factory metaphor breaks down because factories do not like inherently or by design self-improve.
They are operated, but it's the process of like operation and throughput and design are distinct things.
And that's just like, I think less true of software, but the, I mean, the brain turned to mush bit is like, I feel that deep within my bones.
And I think I'm someone who sadly will, will often equate like exhaustion productivity of like, Oh my God, that was a really long eight hours in the office.
And then you, then you look at, you look at what you shipped and it's like, But it was so tiring.
It was tiring because I was like tabbing between eight different workspaces constantly trying to like context switch over and over again.
Instead of like doing the one thing that would have been like slightly less easy, but had a much larger aggregate impact.
So I think an aspect of the software factory that intellectually feels right to me is some of the stuff around self-improving systems.
And I would say that's probably the closest to the bleeding edge that we're currently doing at work is...
And that takes the shape of usually things like, hey, PlanetScale can give us insights about our database and those can get fed in to open a pull request and certain conditions are met like that can just like auto merge, right? And so the idea is like, hey, we can build these loops of like self-healing or like self-improving systems.
But at the end of the day, like, you know, OK, we've we've resolved 50 different planet scale recommendations and like we like that didn't lead to any new customers.
Like maybe it has led to better database performance that, you know, you're like second or third order proxy of like, yeah, like we can scale up the system more or like we can run for longer without upgrading our cluster.
But I do feel like that is probably my biggest worry is that everyone is just like burning their like dopamine receptors on a bunch of low value stuff.
And then your brain just gets like turned to mush and you can't do the high value stuff because like I haven't I haven't I haven't sat deeply for like six weeks and like looked at a problem because I've just been, you know, babysitting low value snack agents.
Which, and I mean, going back first to the plant scale a bit, which I totally agree with and we do the same thing.
I would actually argue like that is where the factory metaphor breaks down because factories do not like inherently or by design self-improve.
They are operated, but it's the process of like operation and throughput and design are distinct things.
And that's just like, I think less true of software, but the, I mean, the brain turned to mush bit is like, I feel that deep within my bones.
And I think I'm someone who sadly will, will often equate like exhaustion productivity of like, Oh my God, that was a really long eight hours in the office.
And then you, then you look at, you look at what you shipped and it's like, But it was so tiring.
It was tiring because I was like tabbing between eight different workspaces constantly trying to like context switch over and over again.
Instead of like doing the one thing that would have been like slightly less easy, but had a much larger aggregate impact.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.