A presentation at Let’s make software great again! meetup in in Gdańsk, Poland by Paweł Lewtak
How legacy projects are created?
Paweł Lewtak TECH LEAD @ EG @pawel_lewtak
chaos
planning
coding without planning
WHAT first, HOW second
“it’s developer’s (mis)understanding, not expert knowledge that gets released to production” Alberto Brandolini
not what to BUILD - WHAT PROBLEM to solve
“Change is the only constant” Heraclitus
estimations are hard
estimation is not a deadline
estimation is like a model; perfect one doesn’t exist, good enough is useful
transparency
leader and responsibility
growth
let’s do Agile!
“Agile now means, we do half of scrum poorly and use Jira” Andy Hunt
code quality
it works for me so why write tests?
I don’t write tests due to lack of time
I don’t write tests due to lack of time I do write tests due to lack of time
documentation
what? how? who? where?
not invented here
silos and rock stars
silos and rock stars
git
burnout
legacy?
legacy?
thank you
slides: noti.st/pawel-lewtak twitter.com/pawel_lewtak
We’ve all seen this: a legacy application (maybe a rewrite) that was supposed to be a hit that became a burden and a pain to maintain. We’ve seen them, we’ve worked on them and promised ourselves to never allow for such project to happen again.
Why did it happen? That’s what I want to talk about during this talk. I will present the reasons for poor code quality. We’ll start briefly with technical side but the managerial side is as important and equally to blame. I’ll talk about things like leadership and responsibility for a project, leaders and team communication.
Using real-life examples I’ll show how project slowly died and why. We’ll analyze reasons and try to find the answer to the question how could it be avoided?
for free. You
can too.