Blog
What Really Needs to Happen Before Responding to the User?
A few years ago my brother-in-law asked me to build a small e-commerce site. The idea was simple: sell online the artisanal digestive liqueur he made. A handful of products, a bare-bones checkout, the receipt printed and slipped straight into the package.
That’s it.
A deliberately simple architecture
At that point there was no reason to complicate the architecture. Every request started and ended in the same place: the user confirmed the order, the application completed every operation, the response came back immediately.
Why my blog doesn't save articles in a database
Once I decided to start the blog, I had to begin building it.
Paper, pen, E/R diagram. The rush you get when you think: I’ll build it myself. The temptation we developers all feel, at least a little.
It’s the classic project that looks like a weekend job. Then you get into the heart of the design and in come editor, slugs, versioning, preview, SEO, sitemap, RSS, image management, search.
I didn't want a portfolio
There are those late-June evenings that seem made on purpose to be improvised.
The ones where the heat isn’t stifling yet, the beach is almost empty, and mass tourism hasn’t arrived yet.
The suggestion came just like that, without overthinking it.
“Pizza on the beach?”
It’s hard to say no to an invitation like that.
A little further along, a couple was packing up their things. They were about to leave. We invited them to stay with us. They looked at each other, smiled, and accepted.