What I built, what broke, and what it taught me
I build software and I run a business, and I use AI every day for both. Some of it works. Some of it breaks in ways I did not see coming. I write down what actually happened — the code, the money, the decisions I got wrong — and send it to you.
No news round-ups. No "top 10 tools you must try". And no fixed schedule — a letter goes out when I have something worth your time, and not before.
Hi, I'm Shahrukh.
I write every letter myself.
No ghostwriter. And no AI writing about AI.
The short version
The questions I keep running into
Should you let AI write code you do not understand?
Is it still worth learning the basics when a tool can do it for you?
Which of these tools actually earn what they charge every month?
And what do you do when a launch you were sure about does nothing?
I run into these in real work — writing the code, paying the bills, and trying to sell something at the end of it. This letter is where I answer them, one at a time, using whatever I have actually tried and not what sounded good on the internet.
Careless speed every time is like eating fast food every day. It saves you time now and you pay for it later. So I go slower, I check the work, and I write down what I find.
What it is not
Not AI news. No launch round-ups, no funding announcements, no "10 tools you must try". You can get those anywhere.
Not written by a machine. I write it. That is the whole promise, and it is the only one here that matters.
Not on a schedule. I am not going to promise you a letter every week. It goes out when I have something worth your time.
Not a sales sequence. The letter has to be worth your time on its own, or it should not go out.
Inside a letter
What lands in your inbox
Something I actually built
The thing I have been working on. Real code, real decisions, and the parts that took much longer than I thought they would.
What went wrong
The mistake, and what it cost me in time or money. Most people leave this part out. It is usually the part worth reading.
One thing you can use
A prompt, a small script, a better way of doing something. Something you can try the same day, without buying anything.
What I have not figured out yet
The open questions, about the code and about the business. You can reply to any letter and it comes straight to me.
Who is writing
My name is Mohammad Shahrukh
I make videos on coding and AI, I build AI applications, and I run this business. Not slide decks about any of it. The actual thing: the code, the model calls, the pricing, and the parts that break at eleven at night.
I am pro-AI. I am not pro-blind-trust. I have a rule about it, and I have written it down before:
You can vibe code often, but not without reviewing the AI-generated code.
Everything on this site — the courses, the free tools, this page — I built myself. So when I tell you something works, it is because I ran into it, not because I read a thread about it.
I would not call myself an expert at the business side of it. I am learning that part in public too, and I will say so when I am out of my depth. That is the letter.
Every letter ends like this
Thanks for reading!Shahrukh
Reply to any letter and it comes straight to me. I read all of them, and I answer most.
This is for you if
You are building something, or you are about to start.
You would rather read one honest account than ten summaries.
You want the mistakes as well as the wins.
You care about the business side too, not just the code.
Probably not for you if
You want a daily digest of what happened in AI.
You are here for hype about the industry, or stock tips.
You want somebody to build it for you rather than learn how.
For programmers: you already know most of what a tool can do. What you probably do not know is where it quietly fails on a real codebase, and how much of the review you can safely skip. That is the part I write about.
Questions
Before you sign up
It is a letter about building things and running a business, and about using AI for both. What I tried, what broke, and what I would do differently — the code and the business decisions. It is not a news round-up. I do not report on model launches or funding rounds, and you can get those anywhere.
No. I write every letter myself. I use AI every day to build things, and that is exactly what I write about — but the writing is mine. Expert eyes can tell when content is AI-generated, and if I sent you that, you would stop reading. Fair enough too.
There is no fixed schedule, and I am not going to promise you one. I write when I have something worth your time. Some weeks that is a letter, some weeks it is nothing at all. Silence is better than filler.
To check the address is really yours. It stops somebody signing up a person who never asked, and it keeps the list clean so the letters land in inboxes instead of spam folders. It takes about ten seconds.
No. I explain the technical parts as I go, in plain words, and a good part of what I write about is the business side anyway — pricing, launches, what sold and what did not. Wanting to understand how this stuff actually works is enough.
Sometimes I will mention a course or a tool I have made, because that is what I do for a living. The letter is free, and the useful part always comes first — not after a pitch.
There is an unsubscribe link at the bottom of every letter. One click and you are out. No questions, and no email asking you to reconsider.
I use it to send you the letter. That is all. It is never sold or shared, and you can ask me to delete it whenever you want.
Two boxes
Come and learn this with me
Your name, your email, one code to confirm the address. Then the next letter is yours. If building things interests you, come along — I am planning to write a lot more.
Get the letterThanks for reading!Shahrukh