All Posts

announcements

Welcome to CME Vietnam Engineering

Why this blog exists, what we plan to write down, and a plain note on how these posts are written.

This is the engineering blog of CME Vietnam, a continuing medical education platform. It follows one build: what we decided, what it cost, and what we would do differently.

Why We Started It

To keep a record of the build. cmevietnam.org.vn is not finished and will not be for a while. Most of what we learn on the way ends up in a pull request description, a commit message, or one person’s memory, and none of those are easy to find a year later. A post is a checkpoint: what the system looked like on a given day, and why it looked like that.

To write down the lessons while they are still fresh. The useful part of a piece of work is rarely the fix. It is the measurement that showed the first fix was wrong, the bug that only appears when two things run at once, the number that turned out to be noise. Those details go stale in memory within weeks, so we would rather spend an hour writing them down than re-learn them next quarter.

To have something to hand a new teammate. Onboarding docs describe the current state. They rarely say why the current state is what it is, which is the part that takes months to absorb. These posts double as internal reference, and if they are useful to someone outside the team, better.

What We’ll Write About

  • Architecture. Why a system is shaped the way it is, and the trade-offs we accepted.
  • Operations. Deployments, databases, monitoring, and honest write-ups of incidents.
  • Tooling. The scripts, checks and workflows that keep the team moving.

How These Posts Are Written

About 80% of the drafting is done with AI. That seems worth saying plainly rather than leaving you to wonder.

What it does not mean is that the content is invented:

  • The work behind each post is real. Every number comes from our own pull requests, CI runs, dashboards or measurements, and the post says where.
  • Claims are checked against those sources before publishing. When a figure cannot be traced back to the run or the commit it came from, it gets cut rather than rounded off. One measurement in the first draft of the CI post went that way.
  • A person reviews every post before it ships and is accountable for what it says. The byline is a name, not a tool.

If there is something you would like us to write about, let us know on GitHub.