Unfortunately I can't have that chat ever. I'm the one (in most of my career, not now) responsible for telling my folks what the customer wants, and not in a sales way.
Oh, they can, they will just force some other poor programmer to read your code and figure it out. A profoundly miserable process, but someone is willing to do it.
I’ve seen a “temporary fix” serve as a core element of a service stack for a company with annual revenue in the hundreds of millions for like at least 5 years.
This applies to lift-and-shift migrations too. “We need to migrate this now, let’s fix it as a next phase”, then it never gets fixed; instead of taking the opportunity to fix stuff as you build on a clean slate.
I loved agile as an analyst, we used to use waterfall and you'd hear about incorrect designs months later, or not at all, where in agile you can work out the details with the programmers and get both nearer the business requirements, and better designs
Also I absolutely love the job of scrum master which had no equivalent in waterfall
I love waterfall as an developer, I’m using agile now and we have incomplete, conflicting designs every sprint, or spills which affect our metrics, where in waterfall you can workout all the details and have full vision of product and better design with less reworks.
Not to mock you. My point is that methodology is not import when team consists from responsible professionals
My conversation with the moronic MBAs that lead my org today. Who cares about doing impactful work when we can just do useless busy work that makes the nontechnical morons happy.