This is a reference I made for myself. Five required sections from the book, quality checks for each one, and one extension I added (Open Questions as a shapedness metric).
Would love to hear how others have adapted Shape Up for their context.
36 karma · joined December 23, 2022
This is a reference I made for myself. Five required sections from the book, quality checks for each one, and one extension I added (Open Questions as a shapedness metric).
Would love to hear how others have adapted Shape Up for their context.
I'm not sure I know the answer, but it's a very good point! Thanks
The parallels to software are exact. Front of house/back of house coordination. Pre-service meetings. The "pass" as a coordination point. Station ownership. The quiet kitchen principle.
Then I discovered Basecamp's Shape Up is essentially their version of the brigade de cuisine system. 6-week cycles, betting table, appetite setting, cool-down periods. It maps perfectly.
I wrote this to work through what small bootstrapped software companies can learn from how these organizations actually operate. Would love feedback from others dealing with this coordination problem.
If it doesn't sound right, maybe check you've not leaked any keys in public github repos etc? There's crawlers hunting for exposed API keys. Stay safe out there!
Security patches though, yeah, that's tougher. My position is that if security is a concern, you need to hire someone. As much as many of these tools can integrate with databases and set up auth, I'm not sure how much I trust it personally. Especially if the actual code is hidden.
But the internet stuck around. It was still useful.
Just because something is overhyped, or doesn't meet the standards of the world's most demanding engineering organisations, doesn't mean that it's not here to stay and improve.
Perspective.
Deployment is literally a button. Granted, to a replit subdomain. But following some documentation to add your own domain is not out of reach.
The benefit and excitement is most felt by people with little to no experience writing code themselves. The fear seems to come from building.. what, code for critical infrastructure? That's just not what we're talking about here.
The hype is real, the bubble is real, but that doesn't mean it's meritless.
We're talking about building useful tools. Small things, that work in a way that makes sense to the individual.
Something that could be churned out in a day or two by a competent dev, but is completely out of reach for Joe public.
That's where we're at.
I prefer to think about the ways it could go right. To empower people to create is the very purpose of computers, no?