Nobody deletes an app because of its framework
A friend asked whether to build native or use Flutter. Why AI may bring big companies back to native apps, and why a new product should still ship first.
THE JOURNAL
Ideas, reflections, and lessons. A record of the things worth paying attention to.
A friend asked whether to build native or use Flutter. Why AI may bring big companies back to native apps, and why a new product should still ship first.
A fake bank text that almost got me, a deepfake video call that cost a company millions, and why the answer to AI-powered scams is to get sharper, not to stop AI.
An index that froze the orders table, a shrine for praying while we waited, and why the best server prayer is the one nobody has to say.
In school, I built a tiny exam schedule app that almost every student on campus used for a couple of days. Then life got busy. Now AI is giving builders their weekends back.
A support agent pastes an angry customer email into AI, along with the customer's name, phone, and bank account. Why privacy is about respect, and why AI can help with the problem without learning who it's about.
A friend asked ChatGPT what day of the week it was, instead of opening his calendar. It is funny, and it is a big clue about where software is going.
A friend built a booking app in one weekend with AI and decided building apps is simple now. Two weeks later, he met the rest of the iceberg.
Fifteen tabs and a spreadsheet, replaced by one request to an AI browser. Why the next shift in AI is wearable plus agentic, and why today's habits matter more, not less.
A weekend proposal, an AI that called it excellent, and three obvious questions from the boss on Monday. Why "What do you think?" is the worst thing to ask AI.
A job post written by AI that attracted nobody, the same job post with a real brief, and two habits that turn AI into a real thinking partner.
Two managers, the same AI tool, and very different results. Co-Pilot mode makes you quicker. Co-Thinker mode makes you sharper.
A customer list dropped in a team chat, a group that quietly grew, and why fast teams can cut corners on code but never on data.