Reconstructing Taiwan’s Internet-Based Party Politics
summary
A legacy Rails system is rebuilt on Ruby 3 and Rails 7 with normalized schema, ASM state machines, and Active Job replacing manual Rake tasks; an independent election site is developed in one month with two people and achieves >80% test coverage. DevOps uses GitLab CI, Docker review apps, and automated CD; a custom migrator engine moves data and attachments, migration runs in ~30 minutes with ~2 hours manual verification and no data loss. Sensitive voter records get ActiveRecord encryption.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:16New Power Party’s internet ops
- 9:21Legacy system challenges
- 11:32Rebuilding with clear goals
- 13:21Database schema improvements
- 15:36Legacy election system risks
- 16:44Independent election website
- 19:58DevOps automation goals
- 21:03CI/CD with GitLab
- 24:17Review apps workflow
- 25:22Data migration process
- 28:22Conclusion
related talks
37mHigh Performance Political Revolutions
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
34mIndustrial Rails
26mKeeping the Rails Magic Alive After 18 Years
14mWhat About Ruby On Rails? ... From A PHP Guy
09mMicrotalk:A House of Cards - The Perils of Maintaining a 7-Year-Old Codebase
24mThe Rails Features we Loved, Lost, and Laughed at
31mSo Long, Hoboken: Migrating a Huge Production Codebase from Sinatra to Rails