Technical Debt: why it is crippling you and what to do

Comments

Comments are closed.

Rated 3

Bart Reunes at 16:36 on 29 Jan 2016

Interesting talk, maybe spread the analogy to personal financial debt a little bit more.

Rated 3

Niels Cor at 16:46 on 29 Jan 2016

Got me thinking! But I missed some personal introduction (the personal financial analogy was nice though). The new insights like good debt were interesting, but for me there was a lot of obvious stuff.

Good talk. Interesting to hear about good debt...

Rated 3

Toon Verwerft at 13:58 on 31 Jan 2016

Interesting content. Maybe you could lighten it up by using some more examples?

Good talk, escpecially for the uncon track. Learnt a lot and the discussion afterwards was enlightning :)

Rated 3

Omar Reiss at 11:30 on 1 Feb 2016

I enjoyed the talk, because I like the topic and I like the passionate way you addressed it. Quite nice to be reminded of how useful value objects can be!

I have a suggestion regarding the structure of your talk:

The solutions part of your talk contained three elements: separation of concerns, method extraction and value objects. These are not all of the same order. Separation of concerns is a general principle whereas method extraction and the use of value objects are more concrete solutions for specific problems that can exist in code and can be part of technical debt.

I would advise to choose a more coherent set of pillars for the talk. Either go for a more philosophical talk (talk about separation of concerns, modular vs connected architecture, trusting on framework vs pure OOP etc. etc.) or go for a more concrete talk (talk about three useful refactoring strategies for tackling technical debt).

In any case, I think some more code examples and actual usecases could save you a lot of explaining.

Final point of feedback, I think you can spend less time introducing and explaining the problem and get to the heroes of your talk sooner.