Last “impossible thing:” quantifying tech debt as financial debt.
It’s a metaphor, not identity!
There is not repaying technical debt, only suffering (that’s my word) — paying the carrying cost.
How do you take a legacy system toward fast flow of change? @suksr takes us through an evolution
using wholistic approaches including DDD, Wardley Mapping, and Team Topologies #QConLondon
The Wardley Map is only part of Wardley Mapping. There’s a whole strategy cycle
It’s not about how fast the team can program.
It’s about how fast the team can find solutions to each problem, uncover organizational secrets for how the domain works and should work.
There’s a conflict between cross-functional teams and the organizational hierarchy.
Enforcing the same JIRA workflow doesn’t make developers interchangable.
“It takes me weeks to develop rapport with teammates, months to learn domain and code, a few hours to learn a JIRA workflow.” @ntcoding#QConLondon
Smooth devex, sustainable flow:
“This is working in the government, six years ago.
No one else has an excuse anymore.” @ntcoding#QConLondon
They found best practices like: wrap each unit of work; report errors in a standard field; use span names that are specific enough to tell you what’s happening but general enough for useful grouping.
A deep Java performance talk that I don’t have enough context for, by @PeterLawrey
Project Panama is about replacing JNI. Meantime, if you want to share memory between processes cleverly and safely, you can use their chronicle-bytes library. #QConLondon
“If you go down to the low level for too long, you wind up writing systems that can’t be altered.” @PeterLawrey#QConLondon