Refactoring legacy Code ?
It has been a while since my last posting - sorry about that. Actually I was - and am - really busy with the new milestone of swoodoo.com which we will (hopefully) release soon.
We did refactor nearly the whole system - starting from the database layer, over to the API and finally the GUI. Everything will be brand new - or at least massivly refactored.
As we do agile development since many years we are quite experienced with managing such large refactoring sessions. More or less the same happend in OXID eSales - the new eShop Version was refactored massively. Under the hood (and not only there) many things changed.
And how about you ? Over the last years I heard many developers, managers and companies stating that they would love to change/refactor their big ball of mud - but they won’t as they fear to fail. And in deed - the risk to fail is definitly there.
On the upcoming php Conference near Frankfurt Johann Peter Hartmann, Thorsten Rinne and me will run a full day workshop where we try to show you, where the devil in the details is creeping out of his hole.
For the ones who can’t or don’t want to attend the php Conference (which is a huge mistake but hey - it’s your decision) my friend Tomas Liubinas (Senior Developer at OXID eSales) and myself will try to give you a brief overview over the pitfalls and learnings we had in refactoring OXID eShop.
This will be a small series of articles - as otherwise it would be a monster posting 
Check back soon.
Comments
2 Responses to “Refactoring legacy Code ?”
Leave a Reply
[...] known quite some time and e. g. told here, that OXID eSales AG has spent nearly two years of refactoring the code of their software. Together [...]
OXID eShop 4 launch coming closer……
Maybe you already know that we didn’t release a new beta of OXID eShop 4 this week. The reason is simple: Development of the 4th generation of OXID eShop is almost finished now and the official release date is coming closer! We at OXID feel a little b…