Working on technical debt is a necessary part of every engineering team's business as usual priority list; but how do you balance building new features and tackling technical debt work?
- Decide when to work on technical debt and when to stop
- Learn to prioritize working on tech debt
- Communicate the importance of this work to your team and the business
Register for free
Sign up today and claim a free Bugsnag mug to enjoy your favorite winter beverage or jazz up your home office.
Brought to you in partnership with Bugsnag
Bugsnag manages full-stack application stability for making data-driven decisions on whether to build software or fix bugs. Their best-in-class mobile support and diagnostic data enable teams to reproduce and fix errors grouped by root-cause, sortable by business impact and displayed alongside rich diagnostics.
Maude is a Senior Staff Engineer at Slack.