Prioritizing Technical Debt as if Time & Money Matters • Adam Tornhill • GOTO 2019

[@c4tubo]

This is this most valuable video I've seen after watching many programming videos over the last month. Very well done.

[@Achrononmaster]

I'd say, "May the code sense be with you." Adam's work has gotten in to technical work in our government, it's improving government support for businesses who have social responsibilities, so I hope Adam knows how much he is improving whole segments of society beyond just software development. Thanks dude, funky Swedish accent and all.

[@asafali6491]

dear

[@vatreni8088]

Great talk! You analyzed your own code at the end. Identifying the power distribution and where to go is powerful and makes economic sense. The connections between services, components are true leverage.

[@Runesocesius]

Brilliant. Some really ground breaking stuff.

[@flyinggeng]

Sounds like it was a bad microphone at start and it was corrected at 9 minutes.

[@nopara73]

I was thinking about unsubscribing from this channel due to the many hype topic content lately, but this video and the previous one convinced me to stay... for now. Great content!

[@Achrononmaster]

Conference technical debt. X-ray the frickin talks.

[@ottorask7676]

The main idea is stupidly simple now that I saw it, thanks! Does not remove the need to good old team work or communication, but is an immensely great conversation starter.

[@ladefoged87]

This was one of my favorite talks from this years GOTO Copenhagen! We are trying to adapt the methods in a few of the teams I work with.. Good stuff!

[@ishanagrawal90]

How did it turn out for you so far?

[@clementcazaud8040]

Brillant, thanks for sharing your experience. The conclusion sums up the problem and solution pretty well... Desgin your application after business, not technology... Otherwise, you're likely trying to force your way against Conway's law. That's also a problem that Uncle Bob approaches with his Clean Architecture solution which is use cases centric (business features centric).

[@rolfkarlsson445]

This is food for thought. Great, Adam!

[@2c7s]

What is that noise? I tried to play some music to make sure it's not my speakers.

[@pohjoisenvanhus]

I can certainly testify that code that one isn't familiar with can feel way more complicated, scary and legacy than it is after you get acquainted with. Having good documentation of it lessens the impact thought as it makes it possible to get into it through having a way gentler learning curve.

[@7th_CAV_Trooper]

The problems Adam discusses are exactly what my client is working through right now. It's all very painful. I've shared this video. :p

[@trashmail8]

Thank you! This title sounds very promising! :)

[@r3fuG4d0]

Thank you Adam, it was really enlightening!

[@KarenTazayan]

Thank you for the excellent talk!

[@Kienlamb]

Lots of useful information in this talk, thanks!

[@kbrnsr]

7:48 audio improves

[@noonesenemy89]

The audio is really squeaky

[@aaronlong1298]

This some background noise that is aggrevating

[@TheForumgod]

Just chiming saying that it was the audio source itself on the presentation, it gets fixed around 8 minutes in.

[@judgedbytime]

zipf distribution? 19:20

[@pohjoisenvanhus]

So you fix the technical debt only where it's slowing down development and when it's worth it according to cost-benefit analysis? Locality of change based modularity kind of just sounds like modularity based on separation of concerns where the reason to change is in most cases a changing requirement. I'm not confident though that it's easy to weave an application together from modules encapsulating features if they tend to crosscut each other. I'm not sure which technique, language and tooling would allow for what I'm imagining mainly because if that's the way we cut it to pieces I'm not sure how I can easily get a bird's eye overview of how it all ties together. I'd love to hear any ideas on this.

[@hamdihadjer5691]

Thank you ;it is excellent

[@sandeepsachan3729]

Nailed it! #Adam Tornhill

[@ilciavo]

Making an X-ray of the X-ray machine META