Framing impossible
When something seems obviously impossible, check whether that’s because of the thing itself or because of how you’ve framed the question.
When something seems obviously impossible, check whether that’s because of the thing itself or because of how you’ve framed the question.
The dip isn’t dramatic. It’s not a crisis. It’s just another Monday where the page is blank and there’s no particular reason to fill it.
When I started this, it was for a month. I’ve never felt so close to the end while struggling to reach it.
But New Year’s Day is not the end. I’ll continue.
AI won’t say no to your idea. The market will say no but only after you’ve built it.
The rarest person is the one who says yes but why.
They accept the idea exists. Then they ask why anyone should care.
Find that person before you write the first line of code.
There are people who want to make things. And there are people who can build things. Sometimes they’re the same person.
But for everyone else, the first iteration has always been expensive. Websites, apps, services. Getting something built meant finding someone who could build it and convincing them your idea was worth their time and cost.
Many ideas died right there. Not because they were bad ideas but because the gap between imagining and building was too wide to cross alone.
Now you can get these ideas out of your system. Try them for cheap. See if they hold up when they’re real and not just in your head.
Some ideas deserve to be built. Others you need to put to rest. Either way, you can find out without being pot-committed.
Walking home from lunch with a friend, I noticed a bug on an experiment website.
I opened Claude Code. Explained it. Set it off.
Within a few minutes I got the code. It pushed to the repository which told my hosting provider to create a preview site.
I confirmed the fix. Released it.
Five minutes end to end.
Think how this impacts small product sites, campaign sites.
Does it scale to teams of ten people? Or a hundred? Probably not right now.
But this is how far we’ve got. Claude Code was released in February.… this year… 2025.
If everyone can code now.
Then details matter more than ever.
Action comes first, motivation comes second.
It’s not the other way around.
The future always wins. It’s undefeated. So don’t fight the future, everyone. It’s happening whether you like it or not. - Chris Do - The Futur Podcast
Every generation is blamed for cheating by using tools the previous generation did not have access to.
I remember working in Photoshop and there were no layers. When there was no magnetic lasso. I remember when autocomplete was not a thing in the IDE. I remember when the IDE did not exist, you wrote in notepad. I remember when sampling in music was considered cheating. When using open source was considered unprofessional. When using Wikipedia was cheating. When using stock photos was cheating. When using Stack Overflow was cheating.
I will remember when using GenAI was considered cheating.
Today I watched the Getting Lost documentary about the awesome tv-series Lost. One interesting fact is that the writers never expected to get past the pilot. They focused on making one episode that worked. But they are experienced writers and by trade they embedded potential in the characters and left small plots that could be picked up.
Like friendly TODOs in code. Not promises to implement. Just honest markers that say “this could be something.” or ”remember to fix this later.”