Making Architecture Matter - Martin Fowler Keynote

preview_player
Показать описание
From OSCON 2015 in Portland: In the software world, architecture often gets a bad reputation. I’ll talk about why it matters, and how we can pay attention to it without falling into traps.

About Martin Fowler:

Follow O'Reilly Media:
Рекомендации по теме
Комментарии
Автор

I love that he was able to give an important lesson on the “How?” of software architecture at the very end: delegate decisions to those with the time to focus on them.

armorsmith
Автор

Bringing Martin Fowler only to talk 15 minutes. Poor man.
Excellent presentation as always :)

thelonearchitect
Автор

Having read couple of books by Martin Fowler, but seeing him for the first time here, don't know why it surprised me to find what a great speaker he is. So articulative and smart!

shrutitanwar
Автор

All managers should see this video before they would crash their company.

tibordigana
Автор

Very nice and straight-forward talk about the value of software architecture

Ankushkushwahachd
Автор

CSCI 4/5448 OOAD Quiz 9:
Right answers:
One part of an application is good modular design, which is internal quality, not visible to users
Architecture is… The decisions that you wish you could get right early
One part of an application is a pleasant UI, which is a measure of external quality and is visible to users

catgirl
Автор

One can appreciate the point of this presentation when one's sense of code smell is trained, functional and utilized. Those controlling the budget as well as developer leads should understand the design stamina hypothesis, so that the appropriate focus and priority is given to internal quality - otherwise pay a high price soon.

georgeobada
Автор

It's amazing when you rewind the talk at 1.5 the normal speed and still hear the conference speaker hit home with razor sharp precision and clarity. Well said!!

baggiowong
Автор

For me, architecture is the distribution of complexity in a system. And also, how subsystems communicate with each other.

lematindesmagiciens
Автор

Very useful explanation about architecture. Amazing thoughts by Martin as always.

ManojTyagi
Автор

Only 275, 435 people got lucky to stumble upon this wonderful video. Thanks OReilly for sharing this video !!

maverickmusic
Автор

A super smart man. It's a pleasure to listen to him. Ok, he's a huge weight in software developing, but as a man it's a pleasure to listen.

Equilibrier
Автор

Jesus, this is amazing. These old guys do speak wisdom.

kaypakaipa
Автор

This is such an engaging presentation!

elizabethakpan
Автор

Just found out about Martin, and I must say he is a very good speaker.

Marius-vwhp
Автор

Software Architecture
+ Ask what things are hard to change later on
+ The "Important Stuff" - what is the most important thing about code base I have to be mindful about, each time I'm working on this
+ Good software architecture is a long term ECONOMIC investment. New features being added later on can take longer and longer, which will put our customers at a disadvantage
+ Good architecture can keep our customers competitive because we can create new features later on that takes WEEKS instead of MONTHS, which happens in a badly architected project

wh
Автор

These shirt 👚 pockets are designed to hold 3.5” hard drives each. Love it.

AI-xijk
Автор

I would really like to see a commercial measure or a sort of customer-facing indicator that can help:
1. Vouch towards actually preferring to buy the $100-more software get more preference over the other

2. Promotes good architecture practices among software teams and organizations towards creating better quality products/features knowing that their products will be profitable given their hard work and future vision
My 2cents!

firasabughazaleh
Автор

Monstro sagrado! Always brilliant and elegant.

joaopedrogoncalves
Автор

The Design Stamina Hypothesis reminds me of the Change-Cost Curve to an extent which I, myself, frankly can't spot the precise difference between them.
I do see, however, that whenever some "thing" has more than one name.. then that thing must be pretty darn important.

Nonetheless, the presentation was astoundingly informative for it's shortness of time.
Who'd expect less than that from this man, anyways?

pietrotavares