CodeConnexx 2013
7 - 9 Nov 2013
at Hotel Van Der Valk
Talk comments
In my opinion, the part about papers and pens was a bit too much for the audience, because most of them probably don't use paper so much for taking notes. It was very, very specific, like the focus was on the notes and not in what we want to achieve with them.
The techniques were interesting, I also liked the slides very much, but I found it difficult to keep concentrated on the talk. If you could get some interaction with the public it would be nice.
A strong and gifted speaker! Giving and taking advice is a skill as well. The reasons for taking and giving advice came across very well. However you're such a powerfull and authoritarian presence that I didn't even question or analysed your story at the time; it all made sense.
In hindsight I missed how to handle people that do not want, or recognize your advice. and how do you recognize and filter advice that might not be favourable to your case. How do you know where to put them on the graph you showed?
Strong speaker, but I already use Sass (and Less, I'm not a Sasshole like you've called yourself) so the actual talk didn't gave me any new insights, but it was entertaining nonetheless.
Would have given you 4 stars, where it not that you've Rick-rolled us.
Good talk, I think it's good to get a reminder regularly to keep thinking about what you want in stead of settling for something less. I just quit my job for that exact reason.
You where obviously nervous and there are some tricks to remedy some of that. Things like try to pour your water and fix you mic beforehand, or take some time to fix it. You could get a cheatsheet so you do not have to look at the screen so often.
Great talk I will use vagrant! About puppet: when being pushed by other people to include other systems, I would do some research on them, or leave them out. Your approach resulted in me being impressed by the ease of puppet, but not sure if I should use it or not.
There where some great tips in the talk, and features in google that I didn't knew existed. They where however spread over quite a long talk. The stuff that I found interesting could have been told in 10 minutes.
Still I've ran into a lot of people that use google totally wrong and don't know how to format a query to it. Even some seasoned developers. So I think it's a good thing to explain, just not to me.
Liked the talk, clearly explaining that http-headers and -reponse codes are there for a reason. We share the opinion that a lot of APIs don't use them or use them wrong.
You did appear to go in defence mode when questioned about the DELETE call response codes. Always returning 200 might be the best practice, but I thought the others had good arguments as well. You seemed to avoid a discussion on the topic.
The best developers miss one hand and hold a sword in the other (how do they code?). Great talk giving great advise for some of the potholes I might run into the comming years, thanks!
Good and mind-opening talk. Localization is a lot more than sending text to a translation company and replacing the original. The examples where well chosen and clarifying. And the best practices of implementing i18n in PHP will be very helpfull.
pointers:
Volume, If you decide to go on stage without a mic speak up.
Although the standards define the correct way of implementing internationalisation, pointing them out once should be sufficient.
Your slides are great for re-reading everything, but that much info on screen during the talk was a bit distracting.
I really enjoyed this talk and it especially made me think of and realise the skill gap. It is nothing I really thought about. Her presenting style and slides is also flawless, another great talk well done!