Making internets great again - a story of working with legacy code
summary
An applicant‑tracking app moves from frequent crashes to stable production by concrete changes: splitting front‑end and back‑end repos, introducing CI/CD with TeamCity and Octopus, linting with Husky and ESLint, upgrading AngularJS 1.3 → 1.6, hosting static assets on CloudFlare CDN, and adding Sentry IO with releases and source maps for error triage. Results: uptime 99.97%, engagement ~96–97%, duplicates 7% → 0.7%, and technical debt 314 → 77 days.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:15Question
- 2:30Background
- 4:25Expectations
- 5:20Goals
- 7:13Implementation
- 11:45Improvements
- 16:14Conclusion
- 18:15Questions
related talks
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization
51mGet up to speed with DevOps using modern development practices
11mThe easy way to Full Stack
23mDevOps and Legacy Code
11mWorking with sharp tools - A case study of Continuous deployment
27mLessons from a Year with Backstage: What Worked, What Didn’t...
43mOld code doesn't stink - Refactor or Rewrite
41mASP.NET Core in Production: Lessons Learned