3 ms·
I thought the same thing until I listened to this podcast. https://www.youtube.com/watch?v=hQNe7nSgcrw https://www.youtube.com/watch?v=hQNe7nSgcrw I can see h
by jsrober 1y ago
I thought the same thing until I listened to this podcast.
https://www.youtube.com/watch?v=hQNe7nSgcrw https://www.youtube.com/watch?v=hQNe7nSgcrw
I can see how in some organizations/bureaucracies that you have to destroy it before you can have any hope of fixing it.
When there are a significant number of people in an organization trying to stop progress, it's impossible for change to happen.
- nicbou 1y agoJust like rewriting a code base is sometimes the best approach. However there is a significant risk off learning the hard way why things were done a certain way. There is a lot of experience embedded in old, running systems. If you don't understand it well enough to change it in place, you can do a lot of damage trying to replace it.