Nice introduction to phing and to see working examples on how to run and configure a build.xml file.
But a couple of hints:
1. don't stand in front of the projector or in front of your slides
2. use either another background color for your terminal or use a movie in your slides
3. don't be nervous
Little hint: keep your phing targets small and DRY (saw a lot of similar lines running a target), use the phing-force Luke!
Very good talk in which many of Phings power is covered, I loved to see the live examples. And just like DragonBe said, keep the examples small and DRY. It definitly got me interested to run Phing sometime soon instead of Ant. The less packages on my server the happier I feel, so if I won't need Java I can save myself a few updates of server software :)
Liked the presentation. Knowing Marco, I'd really like to have seen a presentation about UML (why, how etc :)).
Especially in a short timeslot like yesterday, maybe either focus on the global idea behind phing and then have only 1 or 2 more in-depth items, instead of trying to fit everything into 30 minutes. Doing AND phing AND jenkins AND own plugins AND etc.. might result in not getting any info over to the public at all.
The content of the talk was good, but rushed. Obviously, squeezing a subject such as phing in half an hour of time will make sure that you have to rush to the talk. Perhaps it would be better to generalise and give an extensive explanation on *why* things like phing exist, and how you benefit from using it, instead of showing build files. That's not to say that build files aren't interesting, but that's something the audience can simply look up once they get home. Getting to know the theory behind seems more important. Mind you: this is in my experience only. It might well be others prefer a much more hands-on approach.
When it comes to the presentation itself, I'm delighted to say that I liked it. One thing to be aware of is that you don't speak all too loudly (even with the microphone on), and being deaf on one side made your story a little harder to follow from time to time. The second, as I'm sure you'll now be aware is that it's not a good idea to position your laptop straight in front of the beamer; if you put it *next* to the beamer, chances are (much) slimmer that you'll stand in the way of the screen.
Also, make sure you have more contrast on the screen, or a higher resolution beamer. It was extremely hard to read what was going on in gnome-terminal. Luckily, I understand what phing means when it comes back with red and/or green text :)
All in all, good talk, nice introduction to those unfamiliar with phing.
Comments
Comments are closed.
interesting talk. did not convince me to switch from Ant to Phing, but good to hear about it :)
Nice introduction to phing and to see working examples on how to run and configure a build.xml file.
But a couple of hints:
1. don't stand in front of the projector or in front of your slides
2. use either another background color for your terminal or use a movie in your slides
3. don't be nervous
Little hint: keep your phing targets small and DRY (saw a lot of similar lines running a target), use the phing-force Luke!
Very good talk in which many of Phings power is covered, I loved to see the live examples. And just like DragonBe said, keep the examples small and DRY. It definitly got me interested to run Phing sometime soon instead of Ant. The less packages on my server the happier I feel, so if I won't need Java I can save myself a few updates of server software :)
Presentation was reasonable although at times it felt a bit tedious when going over basic stuff.
Liked the presentation. Knowing Marco, I'd really like to have seen a presentation about UML (why, how etc :)).
Especially in a short timeslot like yesterday, maybe either focus on the global idea behind phing and then have only 1 or 2 more in-depth items, instead of trying to fit everything into 30 minutes. Doing AND phing AND jenkins AND own plugins AND etc.. might result in not getting any info over to the public at all.
The content of the talk was good, but rushed. Obviously, squeezing a subject such as phing in half an hour of time will make sure that you have to rush to the talk. Perhaps it would be better to generalise and give an extensive explanation on *why* things like phing exist, and how you benefit from using it, instead of showing build files. That's not to say that build files aren't interesting, but that's something the audience can simply look up once they get home. Getting to know the theory behind seems more important. Mind you: this is in my experience only. It might well be others prefer a much more hands-on approach.
When it comes to the presentation itself, I'm delighted to say that I liked it. One thing to be aware of is that you don't speak all too loudly (even with the microphone on), and being deaf on one side made your story a little harder to follow from time to time. The second, as I'm sure you'll now be aware is that it's not a good idea to position your laptop straight in front of the beamer; if you put it *next* to the beamer, chances are (much) slimmer that you'll stand in the way of the screen.
Also, make sure you have more contrast on the screen, or a higher resolution beamer. It was extremely hard to read what was going on in gnome-terminal. Luckily, I understand what phing means when it comes back with red and/or green text :)
All in all, good talk, nice introduction to those unfamiliar with phing.