Writing
Case studies written here, and short posts on building, deciding and AI first published on LinkedIn.
- SEO didn’t die. The reader changed.What changes when an answer engine reads your website, and what rebuilding Transit Education taught me to keep doing.
- Getting a two-location restaurant foundHow I think about location profiles, menus and reviews for a restaurant with counters in Fontana and Redlands.
- What I check before calling a site search-readyThe checks I take from Transit Education’s rebuild, from old URLs and canonical pages to honest structured data and readable answers.
- Two buttons that should have been oneWhat working on Sociora taught me about cutting steps, cutting themes, and telling people the truth when a post fails.
- Moving a website without losing what it had earnedRebuilding Transit Education’s site from WordPress to Next.js, and the unglamorous work that decides whether a migration helps or hurts.
- What running a clothing brand taught a software personGymcell started as a personal idea about showing up. Building it end to end changed how I think about products that aren’t made of code.
- A loyalty card nobody has to installHow I designed Naan Cafe Rewards: what the research said, what I cut, and why the counter never waits on the software.
- The hardest part wasn’t building itIt was deciding what mattered. Good engineering is also about what you choose not to build.
- Beautiful doesn’t always mean betterA product can look incredible and still be frustrating to use. Good design makes the right things easier.
- Everyone can build. Not everyone can choose well.AI has made it easier to build software. Has it made us better at building products?
- The same six questions, for almost every problemWhat the business needs, what the product should do, how it should feel, how people will find it, what the data says, and what AI should take off someone’s plate.
- A research day on voice-first healthcareVoice interfaces, conservative triage rules and simple escalation logic for patients in low-resource settings.
- It started with a scary Instagram reelHow a late-night worry about a bad habit turned into TapStop, and a designer opening VS Code.