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

  Рет қаралды 55,242

GOTO Conferences

GOTO Conferences

Күн бұрын

Пікірлер: 29
@c4tubo
@c4tubo 3 жыл бұрын
This is this most valuable video I've seen after watching many programming videos over the last month. Very well done.
@Achrononmaster
@Achrononmaster 4 жыл бұрын
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
@asafali6491 3 жыл бұрын
dear
@Runesocesius
@Runesocesius 5 жыл бұрын
Brilliant. Some really ground breaking stuff.
@vatreni8088
@vatreni8088 5 жыл бұрын
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.
@ottorask7676
@ottorask7676 4 жыл бұрын
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.
@nopara73
@nopara73 5 жыл бұрын
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
@Achrononmaster 4 жыл бұрын
Conference technical debt. X-ray the frickin talks.
@flyinggeng
@flyinggeng 5 жыл бұрын
Sounds like it was a bad microphone at start and it was corrected at 9 minutes.
@pohjoisenvanhus
@pohjoisenvanhus 4 жыл бұрын
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.
@rolfkarlsson445
@rolfkarlsson445 4 жыл бұрын
This is food for thought. Great, Adam!
@clementcazaud8040
@clementcazaud8040 5 жыл бұрын
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).
@ladefoged87
@ladefoged87 5 жыл бұрын
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
@ishanagrawal90 3 жыл бұрын
How did it turn out for you so far?
@2c7s
@2c7s 5 жыл бұрын
What is that noise? I tried to play some music to make sure it's not my speakers.
@7th_CAV_Trooper
@7th_CAV_Trooper 3 жыл бұрын
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
@trashmail8 5 жыл бұрын
Thank you! This title sounds very promising! :)
@KarenTazayan
@KarenTazayan 5 жыл бұрын
Thank you for the excellent talk!
@r3fuG4d0
@r3fuG4d0 4 жыл бұрын
Thank you Adam, it was really enlightening!
@kbrnsr
@kbrnsr Жыл бұрын
7:48 audio improves
@judgedbytime
@judgedbytime 5 жыл бұрын
zipf distribution? 19:20
@aaronlong1298
@aaronlong1298 5 жыл бұрын
This some background noise that is aggrevating
@TheForumgod
@TheForumgod 5 жыл бұрын
Just chiming saying that it was the audio source itself on the presentation, it gets fixed around 8 minutes in.
@Kienlamb
@Kienlamb 3 жыл бұрын
Lots of useful information in this talk, thanks!
@pohjoisenvanhus
@pohjoisenvanhus 4 жыл бұрын
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.
@noonesenemy89
@noonesenemy89 2 жыл бұрын
The audio is really squeaky
@hamdihadjer5691
@hamdihadjer5691 4 жыл бұрын
Thank you ;it is excellent
@sandeepsachan3729
@sandeepsachan3729 5 жыл бұрын
Nailed it! #Adam Tornhill
@ilciavo
@ilciavo 2 жыл бұрын
Making an X-ray of the X-ray machine META
人是不能做到吗?#火影忍者 #家人  #佐助
00:20
火影忍者一家
Рет қаралды 17 МЛН
Support each other🤝
00:31
ISSEI / いっせい
Рет қаралды 72 МЛН
[BEFORE vs AFTER] Incredibox Sprunki - Freaky Song
00:15
Horror Skunx 2
Рет қаралды 21 МЛН
"Good Enough" Architecture • Stefan Tilkov • GOTO 2019
41:41
GOTO Conferences
Рет қаралды 261 М.
Technical debt isn't technical - Einar Høst - DDD Europe 2019
47:37
Domain-Driven Design Europe
Рет қаралды 10 М.
Microservices are Technical Debt
31:59
NeetCodeIO
Рет қаралды 683 М.
Patterns of Effective Teams • Dan North • GOTO 2017
51:04
GOTO Conferences
Рет қаралды 118 М.
Types Of Technical Debt And How To Manage Them
17:58
Continuous Delivery
Рет қаралды 54 М.
Evolution of software architecture with the co-creator of UML (Grady Booch)
1:30:43
The Pragmatic Engineer
Рет қаралды 41 М.
Why Can't We Make Simple Software? - Peter van Hardenberg
41:34
Handmade Cities
Рет қаралды 152 М.
人是不能做到吗?#火影忍者 #家人  #佐助
00:20
火影忍者一家
Рет қаралды 17 МЛН