Hot take 🌶️
I think schools should stop electronic msging to parents — WhatsApp, emails, school portals, all of it!
I think things were fine when kids came home and told parents about school, they brought us notes for urgent matters and were responsible for their own schedules
DuckTales premiered 39 years ago today.
I loved that show. Not for the gold. For the idea that adventure meant going somewhere wild with people you love.
It was Indiana Jones for kids.
Nobody's making the movie, so I made the trailer. Sound on. 🦆
Hey @Pixar, I have the story for Toy Story 6:
Bonnie is a little older now and has stopped playing with her toys. They are still there, but they spend more time sitting on the shelf than going on adventures.
One day she decides it is time to let them go. She puts Woody, Buzz, Jessie, and the rest of the gang up for sale on eBay. The toys do not totally understand what is happening at first, but it slowly hits them. They might be moving on again.
The person who ends up buying them is Andy’s mom. She sees the listing and thinks it would be perfect for Andy’s son, who is coming over for a sleepover next week. She does not realize these are the exact same toys Andy had as a kid.
So the toys get shipped out, but there is a mix up. They get delivered to the wrong house. SID’S HOUSE.
Sid is older now, but still weird in his own way. The house is kind of chaotic, full of strange rebuilt toys and half finished projects. It is not as outright scary as when he was a kid, but it is definitely not somewhere the toys want to stay.
This turns into their big adventure, figuring out how to get out of Sid’s house and back on track. Woody is trying to hold everyone together, Buzz is focused on solving the problem, and Jessie is struggling the most with the idea of being lost again.
Eventually they manage to escape and make their way to Andy’s parents’ house.
When Andy’s son opens the box, he immediately starts playing with them. Andy walks in, sees Woody and Buzz, and you can tell it hits him right away. Those were his exact toys.
You can’t outwork the whole world. There’s always going to be someone somewhere willing to work as hard as you. Someone just as hungry. Or hungrier.
Assuming you can work harder and longer than someone else is giving yourself too much credit for your effort and not enough for theirs. Putting in 1,001 hours to someone else’s 1,000 isn’t going to tip the scale in your favor.
What’s worse is when management holds up certain people as having a great “work ethic” because they’re always around, always available, always working. That’s a terrible example of a work ethic and a great example of someone who’s overworked.
A great work ethic isn’t about working whenever you’re called upon. It’s about doing what you say you’re going to do, putting in a fair day’s work, respecting the work, respecting the customer, respecting coworkers, not wasting time, not creating unnecessary work for other people, and not being a bottleneck. Work ethic is about being a fundamentally good person that others can count on and enjoy working with.
So how do people get ahead if it’s not about outworking everyone else?
People make it because they’re talented, they’re lucky, they’re in the right place at the right time, they know how to work with other people, they know how to sell an idea, they know what moves people, they can tell a story, they know which details matter and which don’t, they can see the big and small pictures in every situation, and they know how to do something with an opportunity. And for so many other reasons.
So get the outwork myth out of your head. Stop equating work ethic with excessive work hours. Neither is going to get you ahead or help you find calm.
[The Outwork Myth — It Doesn't Have To Be Crazy At Work, 2018]
Rick Rubin’s House on the Mountain test:
Create according to your own taste, not for applause, critics, algorithms, or market demand.
“Imagine going to live on a mountaintop by yourself, forever. You build a home that no one will ever visit. Still, you invest the time and effort to shape the space in which you’ll spend your days. The wood, the plates, the pillows—all magnificent. Curated to your taste.”
“This is the essence of great art. We create our art so we may inhabit it ourselves.”
“I'm willing to go to extremes to make the thing that I want to inhabit and it's not for anyone else. it's just for me.”
Feel like I'm missing out because I don't use skills, or a lot of MCP, or multi-agent orchestrations when using AI dev tools.
I'm just like "implement this feature" or "how do this work" or "no not like that, do this instead".
Idk, I feel fast and accurate so why change?
Claiming that "all my code is now written by an agent" is ambiguous. It includes:
1. Folks who know what they are doing and care about software design, who can now produce code much faster.
2. Vibe coders who treat the agent as a black box that generates a working system.
I validate daily that, with the current models, vibe coding is not suitable for building minimally maintainable systems. Agents introduce major internal quality issues quickly and spread them even faster because they echo existing patterns so well.
I see two challenges for programmers today:
First, learning how to do (1) properly: how to create the right context for agents, how to orchestrate them and manage their memory, how to remove toil, parallelize work, etc. In other words: maximize the value we can extract from this new sorcery.
Second, vibe coding is fantastic for non-programmers to create value by doing things they could not do before: quickly iterating on ideas, automating workflows, building ad-hoc tools, and so on. The key question is: where internal software quality starts to matter, and how to enforce it without diminishing this new source of value.
I am also increasingly convinced that many companies that blindly embrace vibe coding and chase futuristic PR headlines are about to discover the terrors of technical debt at scale.
I released kamal-backup today.
There are Kamal accessories for database backups. None do Active Storage. None use restic. None ship restores, drills, or evidence for security reviews.
So I built one.
https://t.co/U9QuGBLvMW
Programming with AI feels like going back in time. You write a prompt and wait to see what happens. It’s similar to when people used punch cards and had to trust the system to get it right.
Why you should write about everything you read:
1. 2–3× better memory (science)
2. Crystal-clear thinking
3. Endless writing ideas
Check out our system to help you become a better reader/writer fast.
I made Solid Queue fiber-based.
Threads need one DB connection each: they can all query concurrently. Fibers share one connection because only one runs at a time.
100 concurrent jobs:
threads: 102 db connections
fibers: 3 db connections
Plus 20% faster on real LLM streaming workloads.
PR is up on rails/solid_queue.
https://t.co/Wqdm7NsR9x