Where to Eat in Vietnam: I Built an App That Picks One Place
Where to eat in Vietnam? Ăn Gì is a free web app that picks one place near you or where you are heading, with directions and a food-by-province guide.
Writing from building software and leading teams: architecture, AI in everyday engineering, and how teams actually ship. Some are short essays, some are long guides. Career and life reflections live in Notes.
Where to eat in Vietnam? Ăn Gì is a free web app that picks one place near you or where you are heading, with directions and a food-by-province guide.
Before you draw a box: the questions that change a design, a one-minute scale estimate, how to say assumptions out loud and where the gaps between boxes hide.
Good reviews dig up commands, edge cases and reasons, then bury them in a PR thread. How to pick what's worth keeping, where it should live, and how to keep it light.
One line a day for a month: what diary studies found, what to write in each note, how to read the pile on day 30, and how 326 food notes turned into an app.
AI is great at listing leads fast and weak at choosing which source to trust. How to split search from judgment, with an incident example and a source receipt prompt.
Focus breaks down at the team level, so solo hacks only go so far. What research on interruptions shows, and the norms that give engineers real thinking time back.
Defaults decide what happens when nobody decides. How to pick ones that fail safely: closed for access, off for new flags, explicit timeouts, and fallbacks you can see.
Why "should be fine" in a handoff hides a guess, and how to label each claim as verified, assumed or unknown so the next owner knows what to trust and what to test.
"Basically done" is a risky place to stop. What finishing properly includes, why loose ends come back to bite, and five questions to answer before you close a ticket.
A practical path through code boundaries, dependency direction, distributed systems, resilience, data, and the trade-offs that appear as software grows.
A field guide to how software work changes across large companies, startups and outsourcing teams, and how ownership, process and pace change with it.
Grounded guides to agents, repeatable workflows, useful trends, everyday ideas, and the checks that keep AI output tied to evidence.
Practical habits for code review, pull requests, feedback, and mentoring that improve the work without losing care for the people doing it.
A calm path from value and stakeholder questions to models, requirements, traceability, rollout, and checking whether a solution actually helped.
Four reflections on using a small, owned set of numbers to see operating health earlier, from the Scorecard and role measurables to revenue, profit and cash.
Reflections on direction, craft, clear messages, ambiguity, and the difference between pushing people and helping meaningful work pull them forward.
How to structure source code so it survives growth, teams, and change.
42 articlesThe human side of building software — reviews, feedback, mentorship, and teams that grow people instead of burning them out.
41 articlesMaking sense of AI — from context engineering to building reliable, production-ready AI products.
40 articlesPersonal reflections from work, learning, people, and the quiet moments that shape a career.
32 articlesHow software teams actually operate and work together — from Agile and Scrum to how delivery really happens in big corps, startups, and outsourcing.
50 articles