Although I have never been an engineering lead in big tech, Rule No. 43 is what you play with client work in consulting or freelancing.
Nobody wants to pay extra to upgrade to Next.js 13 or refactor because you think TailwindCSS is cool.
However, if you think a change objectively speeds up future work and the client agrees, you can make incremental changes in preparing the app for an eventual transition to a new tech/stack.
here is one from marketing: "It takes far longer to acquire a reputation than than to lose one" (Alchemy book)
How it applies to Engineering Leadership: building a good reputation and trust as a leader takes time, patience and repeated positive behaviour. One bad call and you can lose it.
ngl I love the Rules of Acquisition.
Although I have never been an engineering lead in big tech, Rule No. 43 is what you play with client work in consulting or freelancing.
Nobody wants to pay extra to upgrade to Next.js 13 or refactor because you think TailwindCSS is cool.
However, if you think a change objectively speeds up future work and the client agrees, you can make incremental changes in preparing the app for an eventual transition to a new tech/stack.
Kudos for taking the risk and posting about it - I enjoyed the read! For me it's Harry Potter, and I'm afraid to share that with the world 😅
here is one from marketing: "It takes far longer to acquire a reputation than than to lose one" (Alchemy book)
How it applies to Engineering Leadership: building a good reputation and trust as a leader takes time, patience and repeated positive behaviour. One bad call and you can lose it.