Skip to content

docs(blog): add SuMS blog post from the prototyper PM perspective - #119

Open
guangshinhaha wants to merge 1 commit into
mainfrom
docs/sums-prototyper-pm-blog
Open

docs(blog): add SuMS blog post from the prototyper PM perspective#119
guangshinhaha wants to merge 1 commit into
mainfrom
docs/sums-prototyper-pm-blog

Conversation

@guangshinhaha

Copy link
Copy Markdown

Summary

Adds docs/blog-sums-prototyper-pm.md — the SuMS blog post written by @guangshinhaha as himself, for publication on https://transform.gov.sg/.

This is the companion to the existing docs/blog-sums-trial.md (Natasha's SWE-perspective post, #90). Same trial, the other side of it: what agentic coding actually compressed, why bringing security in early set the schedule, and where this approach should not be pointed.

Follows the same convention as the existing post — YAML frontmatter (title, author, date) in docs/.

Closes #94

Review focus

  1. Factual accuracy of the named specifics — SuMS URL, the three replaced legacy tools (Wizvision, ATFM, MIMS), TechPass, MCISO, the AWS/ALB deployment description. These are all checkable by anyone in the ministry.
  2. The "$300K" figure — see the flag below. This is the one thing that should be resolved before publishing.
  3. Tone on the PM/engineer split — the "I did not do this alone" section is deliberately pointed at the "PM replaces engineering team" narrative. Worth a sanity check that it lands as intended with the engineers named in it.

⚠️ Open question before publishing

The draft ends with a reviewer note (marked with an HTML comment, to be removed before publishing):

The $300K figure is annual maintenance for the legacy system, not a quote to build a replacement. Earlier versions of this story have used it as a build quote.

Someone needs to confirm which number we stand behind. Procurement will notice the difference.

Not included

  • No update to the trials/ tree listing in README.md — that listing is already partial (it omits reflections.md and swe-impact.md), and this post lives in docs/ alongside the other blog post, not in trials/. Happy to add a docs index in a follow-up if wanted.
  • Publishing to the Transform site itself is tracked separately in chore: publishing blog posts to Transform's site #95.

🤖 Generated with Claude Code

Companion to docs/blog-sums-trial.md, told from the PM/builder side:
what agentic coding actually compressed, why security-early set the
schedule, and where this approach should not be pointed.

Refs #94

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@guangshinhaha guangshinhaha self-assigned this Jul 31, 2026
@guangshinhaha
guangshinhaha requested a review from ivanfoong July 31, 2026 03:10

I'm a product manager at GovTech, posted into MOE's Digital Experience Division. I also write the code. In about four weeks I built SuMS, the survey management system that now runs at sums.digital.moe.gov.sg and replaced three legacy tools: Wizvision, ATFM and MIMS.

That sentence is the one people repeat back to me. One PM, coding agents, four weeks, against a legacy system that cost roughly $300K a year just to keep alive. It's accurate. It's also the part of the story that teaches the least.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Find ways to illustrate the expensive problem without mentioning about $?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

doc: blog post from SuMS experience as the Prototyper PM

2 participants