Articles
25 posts tagged "For Founders"
How Using Claude to Interview You Can Help You Build Skills (and Apps)
I asked Claude to interview me and got twelve questions back. I answered two. What worked better was having it guess first and let me correct it. Here are the project instructions I use now, and the four files that come out of an interview.
Your Graph Should Not Be Inert
In 1986, an information scientist found a hidden medical connection nobody had made — not by running an experiment, but by linking two piles of research that never cited each other. I set out to build that same instinct into our knowledge graph. Then I got told I was 60 years late. Then 12. Here's what that taught me about why your second brain shouldn't just sit there.
AI Made Your Expertise Cheap. Now What?
Every service business is staring at AI knowing everything is changing and nothing is staying the same. That forces a bet: go premium, go volume, or shift to equipping. But all three bets share one dependency, and the same AI that made your expertise cheap is exactly how you feed it.
The AI Interviewed a Woman Who Doesn't Exist. That Was the Point.
I spent a weekend building a sales executive who doesn't exist, handed her fifteen secrets, and let an AI try to pull them out. The fake expert was the point: it's the first time an interview had an answer key, so it could earn a score instead of a compliment. Here's what testing an AI honestly actually costs.
The Video You've Been Putting Off Takes Five Minutes Now
You shipped something real and nobody knows it exists. Video used to mean gear, a crew, and an edit. Now it's a short script and about five minutes, which moves the hard part to whether you've got something worth watching.
Five Paradigm Shifts You Need to Embrace About AI
Five paradigm shifts from three years building with AI: design time over runtime, judgment over prompts, real feedback loops, conversation, and knowledge that's built, not stored.
Ten Conversations to have with Claude before Vibe Coding
One prompt gets you something. Ten conversations get you something better. Here are the ten you should have with Claude before any code gets written.
Use Claude to get you questions, not answers
Most Claude sessions produce transcripts because users ask for answers. The posture that produces real specifications looks different. Here's what it requires.
Stop Selling a Privacy Policy
When both sides have IP, current AI privacy answers force one of them to bleed. The fix isn't a better policy or a clever cryptographic trick. It's a design discipline: stop protecting what crosses the wire and start designing what's allowed to cross in the first place.
You don't have to be technical to own the architecture
AI is changing everything and nothing at the same time. So where should you spend your scarce time? Three things will always matter: your domain, systems thinking, and architecture. And architecture isn't what most people think it is. It's the load-bearing decisions you care about, written down before the AI builds the wrong thing.
Want to talk about what you just read?
Every great conversation starts with a single question.