Great subject, but not presented as great.
Some remarks (intended as constructive feedback - don't shoot me ;-) ):
- You can make your point in a few slides, but not go on about it. ;-)
- Your talk has some gaps in terms of explaining what some terms are (jargon)
- Your code examples miss some context / syntax (and "I had to fit it on a slide" is not a very good argument when there's plenty of space left - others didn't have this problem)
Thanks for this talk. It's always nice to hear you're doing it 'right' from others. Also learned a few new tricks.
I'll update my packages as soon as possible to evade the Kraken. ;-)
Funny side-comment: you told dev-master is bad and you should do tagging, thought Composer doesn't do tagging itself... :-)
Great first talk. Was really interesting to hear things from a 'junior developer' point of view.
You might be able to expand upon this with your opinion on how we might be able to improve resources (eg. documentation) and/or be better teachers.
Interesting topic, but the talk really wasn't what I expected it to be. It was more on the 'how' and 'what' and not much on the 'why'. So, I couldn't really learn from it. And because it was more about workflow / process, the coding examples were only a distraction. You might be able to improve it by visualizing the workflow.
And I can imagine why, as you said during your talk, you got into a heated discussion with another speaker. ;)
Very entertaining talk. Although, I didn't like the spoiler about this thing called 'Rubik's cube'. ;)
Sorry I didn't have time to talk to you about me raising my hand and not think about a debugging moment. Hopefully some other time.