Building AI Cheatsheet Generator Live: Lessons from a Four-Hour Stream
I built an entire AI-powered app live, in front of an audience, in just four hours. Did I finish it? Not quite. Did I learn a huge amount? Absolutely. Here is what happened, what I learned, and why I will do it again.
The challenge was simple: could I build and launch a working AI cheatsheet generator, live on stream, using AI first coding and Kaijo1 as my main tool?
Answer: almost! By the end of the session, the app could create editable AI cheatsheets, but it was not yet deployed. A few minutes of post-stream fixes later, it was live for everyone to try. (Next time, I will check deployment on every commit!)
Try the app here: aicheatsheetgenerator.com
What We Achieved in Four Hours
In just four hours, I went from a blank slate to a working product. The app generates AI-powered cheatsheets that you can edit and customise. The core features were working by the end of the stream, but deployment tripped me up. It only took a few more minutes to fix, but it was a reminder: always check your deployment pipeline as you go.
The real story is not just about the code. It is about how much faster and more reliably I could build with AI-first tools. Coding AI made it possible to move at a pace that would have been unthinkable a year ago. Kaijo, my reliability assistant, will make future improvements even smoother.
What I Will Improve Next
Shipping live is only the beginning. Here are the improvements I am planning:
Pay to download: I want to add a way for users to pay to download their cheatsheets, supporting the project and unlocking more features.
Better editing: I will improve the editing experience, including box ordering, styles, and colours, so users can make cheatsheets truly their own.
Automatic Kaijo evaluation: I plan to tell Kaijo about the edits and automatically evaluate them, making the app smarter over time and more tailored to the user.
Lessons Learned from Live Coding
Building live is exhilarating and exhausting. The pressure to deliver in real time forces you to make decisions quickly and trust your tools. Here is what stood out:
AI-first coding is a force multiplier. I achieved more in four hours than I could have managed in a full day solo. The AI handled boilerplate, suggested fixes, and kept me moving forward.
Deployment is always the bottleneck. No matter how fast you build, if you do not check deployment regularly, you will get caught out. I will automate more checks next time.
Audience feedback is invaluable. Viewers spotted issues, suggested features, and kept the energy high. Live interaction made the process so much more fun and productive.
Watch the Full Recording
If you missed the stream, you can watch the full recording below:
Or watch it directly on YouTube.
What Should I Build Next?
Should I do another live build with a different service? What would you like to see me tackle next? Let me know in the comments or reach out on social media.
More articles
The Huge List of AI Tools: What's Actually Worth Using in May 2025?
There are way too many AI tools out there now. Every week brings another dozen “revolutionary” AI products promising to transform how you work. It’s overwhelming trying to figure out what’s actually useful versus what’s just hype.
So I’ve put together this major comparison of all the major AI tools as of May 2025. No fluff, no marketing speak - just a straightforward look at what each tool actually does and who it’s best for. Whether you’re looking for coding help, content creation, or just want to chat with an AI, this should help you cut through the noise and find what you need.
Read moreAI: The New Dawn of Software Craft
AI is not the death knell for the software crafting movement. With the right architectural constraints, it might just be the catalyst for its rebirth.
The idea that AI could enable a new era of software quality and pride in craft is not as far-fetched as it sounds. I have seen the debate shift from fear of replacement to excitement about new possibilities. The industry is at a crossroads, and the choices we make now will define the next generation of software.
But there is a real danger: most AI coding assistants today do not embody the best practices of our craft. They generate code at speed, but almost never write tests unless explicitly told to. This is not a minor oversight. It is a fundamental flaw that risks undermining the very quality and maintainability we seek. If we do not demand better, we risk letting AI amplify our worst habits rather than our best.
This is the moment to ask whether AI will force us to rediscover what software crafting1 truly means in the AI age.
-
I use the term “software craft” to refer to the software craftsmanship movement that emerged from the Agile Manifesto and was formalised in the Software Craftsmanship Manifesto of 2009. The movement emphasises well-crafted software, steady value delivery, professional community, and productive partnerships. I prefer the terms “crafting” and “craft” to avoid gender assumptions. ↩
Why Graph RAG is the Future
Standard RAG is like reading a book one sentence at a time, out of order. We need something new.
When you read a book, you do not jump randomly between paragraphs, hoping to piece together the story. Yet that is exactly what traditional Retrieval-Augmented Generation (RAG) systems do with your data. This approach is fundamentally broken if you care about real understanding.
Most RAG systems take your documents and chop them into tiny, isolated chunks. Each chunk lives in its own bubble. When you ask a question, the system retrieves a handful of these fragments and expects the AI to make sense of them. The result is a disconnected, context-poor answer that often misses the bigger picture.
This is like trying to understand a novel by reading a few random sentences from different chapters. You might get a sense of the topic, but you will never grasp the full story or the relationships between ideas.
Real understanding requires more than just finding relevant information. It demands context and the ability to see how pieces of knowledge relate to each other. This is where standard RAG falls short. It treats knowledge as a stack of random pages, not as a coherent whole.
Time for a totally new approach.
Read moreIntroducing Kaijo: AI functions that just work
For months, I have wrestled with a problem that has consumed my thoughts and challenged everything I know about software development.
This week I wrote about building the future with AI agents. One of the key areas for me is moving beyond prompt engineering to something more reliable.
I have spent decades learning how to craft reliable software. Now I want to bring that reliability to AI development.
Today I am ready to share what I have been building in the background.
It started with a game. It ended with something that could change how we build AI applications forever.
Read moreBuilding the Future
Something has been on my mind for months. The rapid evolution of AI agents has opened up possibilities I cannot ignore.
We are witnessing the emergence of semi autonomous agents that will fundamentally reshape how we work and communicate. The opportunities in this space are extraordinary. I am diving deeper into this world of AI agent development and product creation.
My newsletter is evolving. Instead of dispensing tips from a position of authority, I invite you on a journey of discovery. I will document my experiences building with AI, how to apply my tech experience in a new world, and navigating the inevitable struggles and setbacks.
Read on for several key areas I am exploring.
Read more