Building resilient frontend architecture — Monica Lent

Change is inevitable. So is legacy. And too often, we as developers (who love to solve problems by coding) fall into the trap of believing the only way to fix it is by rewriting everything again and again. But how can we design an application architecture that is more resilient to change in the first place? In this talk we’ll look at specific techniques you can use today to keep your app from turning into that infamous ball of mud.

Gold Sponsors: Digia, Gofore, Futurice
Silver Sponsors: Alma Media, Elisa, Nightingale Health, Reaktor, Solita

[aquarius]

1. technical debt
recurring tech debt
second effect system
“Legacy code” often
difers from its suggested
alternative by actually
working and scaling.
”
...
2. arch has become a dirty word

17:03 after some meta info, architectural stuff starts at 17:03.

ways for org of deps
- big ball of mud, layered, modular
differences - dependency organization
shared components
decoupled > dry
dependency trees
dependency tests
3. you dont have to derive architecture from first princtiples

[sumitb]

after some meta info, architectural stuff starts at 17:03.

[akalrove]

The talk about DRY code is so true and I also firmly believe in it.

[paramharrison]

Very good presentation skill, reasonably good talk too

[prov]

This talk is great, but a little opinionated.