Hats I Wear
Software Engineer, Agile enthusiast and modeling junkie
Ocasional Trainer and Speaker
The Good, The Bad and The Ugly
Of Enterprise Software Development
Working for 6 years on different projects and envirionments.
- from small one man show startup like projects to multiteam enterprise setups
- from simple CRUD applications to complex domain high-availability
- from flexible, empowering process to beurocratic top down hell
Today we're gona talk about...
The way we think about sofwtare
How did we get here
What can we do about it
Conclusions
It all started...
On a Big Enterprise Mission
“We're not here to gain knowledge, we're here to get shit done.” - Wise Man
Also coined "The Bulshit Assimetry Principle".
So software engineering is about typing.
There's feature manangement team
There's a functional analysis document
There's a technical analysis document
And there is somebody running the code in production
How we think about software...
IS WRONG!!!
Softare development is ...
like building a house/bridge
linear, repetitive and predictible task
The building methaphor...
“The building metaphor has outlived its usefulness. It is time to change again.” Fred Brooks, 1987, No Silver Bullet
The building methaphor...
Buildings are hard
Architects and builders
What can we do about it?
awareness
attitude
practices
Awareness
... it is nonlinear, unpredictable and creative
Cynefin
Not all problems are equal
We are in the realm of ...
complicated
complex
To be effective ...
become partners
To be effective ...
outgrow roles
expand area of expertise
become T-Shaped individuals
Old Tools
- Class Diagram
- State Diagram
- Association
- Use Case
- UML
- Sequence Diagram
- Database Diagram
That is not the point ...
highly collaborative
facilitate communication
“EventStorming is an act of deliberate collective learning.” - Alberto Brandolini
“Collaborative modeling over specification handoff.”
Recap
awareness
attitude
practices
"No matter what vegetable you are, if you spend enough time in the brine, you become a pickle."
Know what to ask for ...
organize work around customer value
authority, knowledge and skills
stop calling people "resources"
"Nothing at Facebook is someone else’s problem." Kent Beck, Culture of Personal Responsibility.
Enterprise Code Monkeys
Process and Tools
@valentin_ionita