Tech Now Pay Later
Warning
Technical debt is what you owe when you put off maintenance, updates, or cleanup to hit a deadline or ship a feature first. And like money debt, it grows interest. The code gets more complex, the team gets slower, and things break more often.
We always think tech debt is terrible. But as Soojin Ro pointed out, we learn a thing in Finance.
Businesses intentionally create debts to boost liquidity. Similarly, you get a functional code right away by incurring a tech debt right now. This significantly reduces the Time to Market, which is more important than brilliant engineering. Alas, your service must first serve someone for that elegant code to run!
Engine Equation comes handy here.
An engine takes time (a type of resource) and assets to create utility, and this Engine Equation (Metapage) is a function that takes time. If you want to put in less value (help or time) right now, you need to pay it later. Incurring technical debt is an optimizing technique for the engine function equation, prioritizing time over other resources in the short term.
Similar but different from Service Shimmings (faking a service until you make it), but what is the same is creating market value (liquidity of the service) before the tech is ready.
In that sense, Tech Now Pay Later might be better terminology.
technical debt
- bad vibes word
- implies bad things
- tainted by its capitalist counterpart
code now pay later
- unproblematic
- fresh
- cool
-- clip studio pain (@freezydorito) January 29, 2023
The initial version of https://t.co/7lv0YYHdVO used TXT files as its "database".
Instead of worrying about which DB to use for your project and/or if it scales - sometimes you just gotta ship it and iterate later.
"Avoid Premature Optimizations" - wise words by @Levelsfyi 👏 https://t.co/QTT9qIoVHS
-- Steven Tey (@steventey) February 19, 2023