Legacy Code and Teams Series: Composer

After talking about Technical Committee and Training Sessions in the previous post of the series, today, I’ll carry on with adding Composer to legacy projects without pain.

The day I left Emagister, I was sat down with Eber and Christian having beers and talking about all the cool things we did there. We were reviewing each of the changes, it cost, benefits, feelings in the team, etc. When I said, “what about composer? that was cool!”, Eber said, “Composer is not just cool, it’s a must.”. As always, he was too right. It has been also the first thing done at Atrápalo.

Starting with a brand-new project using create-project command it’s easy, but, what about those developers dealing with a big legacy project, with custom autoloader, PEAR dependencies, hardcoded fixes in a external library, non PSR-0 code, etc. Don’t worry, you can also take benefit of Composer. However, there are some tricks you should take care of in order to face those issues.

Continue reading

Legacy Code and Teams Series: Training Sessions and Technical Committee

(Next: Legacy Code and Teams Series: Composer)

When talking with some friends about how we are improving Atrápalo legacy code and development process, they asked for creating a presentation and give a talk about the steps we are following, hows, whys, and so on. It sound to me interesting so I would like to help sharing my experiences, not just the Atrápalo ones because when working at Emagister we did something quite similar with Christian, Eber, Dario, Lluís, Jordi, Jose Luís and the rest of the team with great results.

Before jumping into a talk, I would like to start a serie of posts about my way dealing with legacy projects. I’m really interested in listening from you and your comments in order to enrich the final result. So, any suggestion or experience is really welcomed.

Continue reading