6. Long long time ago…
• Customer: “we need a new architecture!”
7. Long long time ago…
• Customer: “we need a new architecture!”
• Me: “A good architecture won’t save you!
You have a bigger problem than that…”
8. Long long time ago…
• Customer: “we need a new architecture!”
• Me: “A good architecture won’t save you!
You have a bigger problem than that…”
• Customer: “That is not what you’re hired
for: you’re an architect!”
9. Long long time ago…
• Customer: “we need a new architecture!”
• Me: “A good architecture won’t save you!
You have a bigger problem than that…”
• Customer: “That is not what you’re hired
for: you’re an architect!”
10.
11. Especially if they are in the way between you and the solution
Labels are Crap
12. … or that was what i thought
We’re just problem
solvers with a
common goal
42. Phase Four: The aftermath
• Welcome to Legacyland!!!
• quite a few good devs leave
#Ouch
43. More or less…
Good
developers
mostly
cleaning
Good
developers
will leave
Massive hire
of external
contractors Internal
developers
need to
coordinate
externals
No time for
coding for
internal devs
Economic
Opportunity
Enough budget
Bad code will
stay
Increased
amount of
crappy code
?
68. Salary elephant
• A good developer could be significantly
more effective than a bad one
69. Salary elephant
• A good developer could be significantly
more effective than a bad one
• up to an order of magnitude more,
70. Salary elephant
• A good developer could be significantly
more effective than a bad one
• up to an order of magnitude more,
• not to mention negative productivity
71. Salary elephant
• A good developer could be significantly
more effective than a bad one
• up to an order of magnitude more,
• not to mention negative productivity
• Salary won’t grow in proportion
99. Development team
• It’s not supposed to talk with the users
• It’s not supposed to talk with the real
experts
• It’s not supposed to talk with the real
customer
112. Long time ago
• Surveyed a huge codebase:
• 500 k lines of code
113. Long time ago
• Surveyed a huge codebase:
• 500 k lines of code
• Obsolete technology
114. Long time ago
• Surveyed a huge codebase:
• 500 k lines of code
• Obsolete technology
• Oscillating between useless and poisonous
115. Long time ago
• Surveyed a huge codebase:
• 500 k lines of code
• Obsolete technology
• Oscillating between useless and poisonous
• Strong political backing to “revive” the project
116. Long time ago
• Surveyed a huge codebase:
• 500 k lines of code
• Obsolete technology
• Oscillating between useless and poisonous
• Strong political backing to “revive” the project
• Negligible user base.