You're so right about the work not going away and the containers changing. That's what happens every time there is a big technological change. There will be a lot of disruption. But there will also be a ton of new opportunity. And we can't yet understand exactly what that's going to look like.
Really appreciate the article and insights. I really wonder what this means for large enterprise environments as it seems like the future is smaller and more agile.
My hunch is that enterprise will be slow to notice, and then it becomes a thing. Possibly justification for more layoffs, but that would be short-sighted. Those people know the work, and they’ll buy themselves more bandwidth to orchestrate and pursue new experiments. If enterprise sees that as an opportunity, they win. If they go for the short-term cost savings, they probably get beat by smaller, more savvy competitors.
When I have some basic proof of concept which is tricky what with the day job and all that! We probably need to win our first £client who will likely be our dev partners too.
You're so right about the work not going away and the containers changing. That's what happens every time there is a big technological change. There will be a lot of disruption. But there will also be a ton of new opportunity. And we can't yet understand exactly what that's going to look like.
Really appreciate the article and insights. I really wonder what this means for large enterprise environments as it seems like the future is smaller and more agile.
My hunch is that enterprise will be slow to notice, and then it becomes a thing. Possibly justification for more layoffs, but that would be short-sighted. Those people know the work, and they’ll buy themselves more bandwidth to orchestrate and pursue new experiments. If enterprise sees that as an opportunity, they win. If they go for the short-term cost savings, they probably get beat by smaller, more savvy competitors.
What a time to be alive!
Haha yes it is!
Incredibly interesting! Thanks Joseph.
If workflows evaporate and roles dissolve, what becomes the queryable unit of coordination?
How does demand find supply without reverting to inference and noise?
These are some of the questions I've been trying to answer.
The answers are likely in who’s doing the coordination, which I know you’re working on. When are we going to see a demo?
When I have some basic proof of concept which is tricky what with the day job and all that! We probably need to win our first £client who will likely be our dev partners too.
Having said that, I have a vibe coded thing that kinda does the basics for 'workers' here: https://capacity-signal.lovable.app/
plus something from the 'work' side here:
https://intent-flow-registry.lovable.app/
neither are production ready yet tho - they work but very limited.
cheers for asking!
Love it. You should know @Nicholas Whitaker, whom I admire and whose work on capacity is brilliant.
sent him an email and CCd you. thanks for the nudge!
I been have summoned 🤣. Love this thread. I need to read this on the plane tomorrow but you already know I’m a huge fan of this line of thinking.