Avoiding migration migraine with Doctrine


Comments are closed.

Thanks for the talk last Saturday.
For your first talk I think you did very well.

Some small critics: I missed some code samples though.
I understand that it's hard to fit all of the code on a slide, but you could switch from your slides application to your code editor and show samples from there. I've seen this with another speaker Friday morning too.

When attendees ask you questions, it helps to repeat them through the microphone (for attendees in the back of the room). Fortunately I was sitting more to the front ;-)

Anyway, I found it a good talk.
Can you please upload your slides to Joind.in?


I'd cut back on the part on data normalization -- you've spent quite an amount of time on that which would probably be better spent on a bit more extensive advice on the migrations themselves. The presentation itself was quite solid - I'd love to hear this talk a bit more focused on the main subject.

A good subject and you did very well for your first talk. Keep it up and do more talks!

Some room for improvement: I was expecting you would talk about data definition migration, not about transforming actual data. In the end, i think labling this talk as "Doctrine Migration" is putting the wrong focus. It was much more a talk about refactoring a legacy database. Doctrine Migrations was merely a tool to that, but there is not that much to say about it. Try to structure the talk around migrating a legacy database: Explain some database design principles (there is also theory for normalization levels which could be mentioned and used to structure that part a bit more) and then be more specific on the data cleanup steps, with concrete examples. Explain how you in the end did the incremental migrations, ...
Database refactoring is an interesting topic and you have interesting insights and hands-on tips on that.