Don't always remember to post. I thought this one was pretty easy, but has a clever twist.
Minute Cryptic - 9 April 2025
"Harvest turnip beside banks of creek?" (4)
🟣🟣🟣🟣🟣
I scored: 2 under par
www.minutecryptic.com?utm_source=s...
I once estimated that a bug fix would take a day. My manager padded it. His manager padded it. *His* manager padded it, and so on. By the time it reached the customer it had hit 6 months. They approved it.
It actually only took half an hour to fix. Because I padded it.
I don't post much so I may as well post internet word game results 🤷♂️
Minute Cryptic - 20 March 2025
"Cool block house of Lego is now reassembled without directions" (5)
🟣🟣🟣🟣🟣🟣
I scored: 2 under par
www.minutecryptic.com?utm_source=s...
Too many different words; the electorate need a simpler slogan. I propose "America, America, America, America", or AAAA!
I've been playing Citizen Sleeper 2. It's very good, but it is _so much harder_ than the first one. Seems like there's a new opportunity to do permanent damage to yourself every 10 minutes.
#citizensleeper #videogames
Serverless servers are so back
Servers are a pain to manage. Serverless is cost inefficient. Why not use the best of both?
Efficient compute on @vercel.com by packing more invocations into each function instance, like tiny, tiny servers. Fewer cold starts, lower bills, no performance impact.
Sometimes being flippant is a good gateway to not caring
The R&D update starts in one hour. Join us live at 9:00 AM PT.
TFW that big Kickstarter game arrives with its hundreds of components, but it turns out to actually be a pretty, tight, efficient deck-building race to the finish rather than a multi-hour point-salad slog 👌
#BearMountain #sweaterbear #boardgames
A million tiny, tiny repos! What could go wrong!?
The video game was first. The board game is an excellent adaptation of it!
The Beeb was great because 10 year old me could turn it on and land directly in a programming environment that let me interact with whatever random thing I'd made and plugged in directly by peeking and poking. No drivers, no libraries, no complex languages to learn.
2/2
The main thing that's missing is that it's a complex, protected mode computing device with layers upon layers of abstractions between the hardware and the user.
1/2
Sounds like this "task" is actually a project
The implication is that the latter means "unlimited interruptions"
It was amazing 😍
Mount Doom scrolling
Beige has been the colour of the year every year since 2019
You'll be great! I'll get the heated blanket ready ...
Chances of failure are inversely proportional to lines of code changed. Beware the one-liner!
I can tell by the pixels that it's Terraform Cloud
Damp microfibre cloth, but I'm not 100% happy with the result. If there's a better way I'm all ears!
Punch into a big ol' pile in the upturned box lid, then read the instructions and sort as I learn
I still can't even see my grass so I'm going with 0/10
 for decisions. 1-way doors are rare. Never act like something is a 2-way-door if it is a 1-way-door
- Don’t ask for permission, ask for forgiveness but be smart about it
- [Understand what experiments are for](https://www.notion.so/When-to-experiment-8fd91090ef7a418a9532b9681524fe0b?pvs=21)
- Actually QA your shit. Abusing users for QA is inefficient and disrespectful. Users are a source of feedback about the product
- Send your stuff to trusted testers and ask for feedback
- Don’t let indecision go into your head
- If in doubt ship the version that is closer to ship and iterate
- The outcome-differential between two options in a decision is usually lower than the opportunity cost of not shipping either of them
- **You don’t need approval from anyone at Vercel to ship.** People can tell you not to ship, but you don’t have to ask them for permission, they have to reach out to you proactively if they feel strongly enough
- You reach out to legal, finance, security, privacy for their expertise not their permission
- Be transparent about what you are shipping in channels such as product-area-updates, but it is not your responsibility to ensure everybody is consuming your updates](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:efr3ow2v22u45efltglpm3rs/bafkreih4cmsvnsrp6ey2wbrvpg5o7jp7mdbxjjt5mj2waez7duh3lfl4sy)
# You can just ship things - Never be blocked - Understand the [1-way-door/2-way-door metaphor](https://shit.management/one-way-and-two-way-door-decisions/) for decisions. 1-way doors are rare. Never act like something is a 2-way-door if it is a 1-way-door - Don’t ask for permission, ask for forgiveness but be smart about it - [Understand what experiments are for](https://www.notion.so/When-to-experiment-8fd91090ef7a418a9532b9681524fe0b?pvs=21) - Actually QA your shit. Abusing users for QA is inefficient and disrespectful. Users are a source of feedback about the product - Send your stuff to trusted testers and ask for feedback - Don’t let indecision go into your head - If in doubt ship the version that is closer to ship and iterate - The outcome-differential between two options in a decision is usually lower than the opportunity cost of not shipping either of them - **You don’t need approval from anyone at Vercel to ship.** People can tell you not to ship, but you don’t have to ask them for permission, they have to reach out to you proactively if they feel strongly enough - You reach out to legal, finance, security, privacy for their expertise not their permission - Be transparent about what you are shipping in channels such as product-area-updates, but it is not your responsibility to ensure everybody is consuming your updates
You can just ship things
I'm literally only here so that when people ask if I am, they don't have to then try and convince me!
They missed a trick not referring to Google Glass as Googley Eyes
