Steady State Means Continuous Rewriting
brunoscheufler.com
Steady State Means Continuous Rewriting
1–5 of 5 posts
Re: Steady State Means Continuous Rewriting
#2Anyone can come up with a great strategy or grand plans for the future of the company. But it's really, really hard to figure out how to go from "where we are now" to "where we want to be".
Making big changes to your systems to enable that transition without disruption to the current products and processes is actually a really difficult thing. If you could pull it off, it would most likely appear to be continuous rewriting with minimal visible changes ;)
Re: Steady State Means Continuous Rewriting
#3A company that has no long-term strategic goals isn't in a steady state. It's in run-off mode. Anyone can come up with a great strategy or grand plans for the future of the company. But it's really, really hard to figure out how to go from "where we are now" to "where we want to be". Making big changes to your systems to enable that transition without disruption to the current products and processes is actually a rea…
Isn’t that basically Fowler’s definition of “refactoring”?
Re: Steady State Means Continuous Rewriting
#4EDIT: if your company's addiction is to rewrite, like all addictions, it is serving a need. How can you lessen the cause of that need? One major way would be good (defined at present as likely 'industry leading') employee retention.
Just imagine what would happen if your house building projects changed all general contractors and most subcontractors every 2 weeks? It would be chaos and you would end up with an over-expensive pretzel. Why we think software programs are different is beyond me.