TkDodo Dominik Dorfmeister • 3/25/2022

Use Urgency

Read Original

This article discusses the challenge of getting approval for major architectural refactorings that lack immediate customer value. It argues that creating or leveraging urgency (e.g., from performance incidents, deprecated APIs, or security concerns) is key to aligning stakeholders and prioritizing these essential technical investments within larger organizations.

0 comments
#software architecture #technical debt #refactoring
Use Urgency

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Introducing RSC Explorer
Dan Abramov • 1 votes
2
The Pulse: Cloudflare’s latest outage proves dangers of global configuration changes (again)
The Pragmatic Engineer Gergely Orosz • 1 votes
3
Fragments Dec 11
Martin Fowler • 1 votes
4
Adding Type Hints to my Blog
Daniel Feldroy • 1 votes
5
Refactoring English: Month 12
Michael Lynch • 1 votes
6
Converting HTTP Header Values To UTF-8 In ColdFusion
Ben Nadel • 1 votes
7
Pausing a CSS animation with getAnimations()
Cassidy Williams • 1 votes
8
From Random Forests to RLVR: A Short History of ML/AI Hello Worlds
Sebastian Raschka • 1 votes
9
You Gotta Push If You Wanna Pull
Gunnar Morling • 1 votes
10
The ABCD framework for feedback
Cassidy Williams • 1 votes