The amount of software in the world increases in a rapid pace, so does the amount of legacy systems. If you are a developer with some years experience I’m sure that you at some point have had the pleasure of having to do a change, like fix a defect or add some functionality, in an old, messy codebase. Sometimes, the bug fix or adding of the new feature goes well, and you move happily on to a new task or a new project. Sometimes though, the pain of working with the system might just get unbearable. Each change takes forever and you are constantly afraid of breaking some important functionality (true legacy systems have no tests). You may have experienced this too. A little over 1 year ago, in May 2011, I found myself in such a situation.
Lean Kanban Central Europe 2012
Visit our company website
- @MaartenVolders Looking forward to it! If it matches the quality of the 2011 Lean Kanban Benelux conference it will definitely be worth it 2 days ago
- Sorry. No #leancoffeeoslo for me today. Next time. 4 days ago
- RT @nerdegutt: #nerdaid og norske nerder forsøker å samle inn 1.000.000 til Røde Kors/Syria. j.mp/nGXUk7 – RT er høyt verdsatt! 4 days ago
- Kanban - the next step in the agile evolution?
- Spring WS and static wsdls
- Improving Software Quality With Kanban and XP Practices
- Create Good Looking Charts With Play, Flot and JQuery
- Spring WS and basic authentication
- Behaviour Driven Development with Mockito
- Running fitnesse from Eclipse
- A Kanban Retrospective
- Lean Web Development With Play Framework and Kanban
May 2013 M T W T F S S « Aug 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31