Notes from the build, and from the growth after it.
I write down what I ship, what I run, and what the numbers do afterwards. Every issue has one thing you can apply the same week.
What actually lands in your inbox
Front-end notes
Next.js and React: rendering, caching, metadata, and the parts of the App Router that behave differently from the documentation. Written for people who ship.
Ads and tracking
What I run, what I change, and what the numbers do afterwards. The campaigns that lost money too, because reading about one is cheaper than repeating it.
Right to left, done properly
Layouts that are designed for the direction rather than mirrored into it, Arabic typography that holds up at display sizes, and what changes when one site has to carry Arabic and English at once.
Occasionally, the business side
How I scope and price work, what clients ask for, and what happens when a project goes sideways. No motivational posts.
Who it is for
Business owners who want to be found, and developers who want the technical detail. Both get the same email. I explain the terms as they come up, so no background is assumed.
How often
There is no fixed schedule. I send when I have something worth reading, which usually means a couple of times a month. Every email is one click from unsubscribing, and the link is at the bottom of each one.
Notes from the build, and from the growth after it.
Need the work done, not the notes?
The newsletter is the written version. When you want the front end built, the ads running, or an hour of my time, the form is one page away.