The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Maintaining a consistent environment from development to production is one of those challenges that's always easier said than done. It used to be that a small hiccup—like a version mismatch or a misconfigured setting—could have you scrambling to figure out why everything worked perfectly on your local machine but started falling apart elsewhere.
Until fairly recently, software releases happened once or twice a year, maybe once a quarter. This gave IT teams plenty of time to verify and manually sign off on every change before they were released in big batches during a bank holiday weekend or off-peak hours. Typically, they’d produce paperwork to show that all changes had been properly tested, and then those changes would be approved for release in a change advisory board meeting (CAB).
Since 2020, I’ve been working on an Express (Node.js framework) application to power viewer interactions and events that happen whilst I’m streaming live coding on Twitch — my Twitch bot. Since using Sentry for error monitoring and crashes using the Sentry Node SDK, I’ve already squashed quite a few bugs that were entirely a result of my own terrible code.
