Have you ever needed to give a presentation to your local user group? Do you need to present a topic to your team? Have you ever wanted to speak at a technical conference? If you answered yes to at least one of those questions then we are presenting Day Camp 4 Developers #5: Public Speaking for Developers just for you. We have selected 4 presenters that we feel are great at presenting technical topics. Each of them is a developer, each of them has a history of public speaking, and each of them has agreed to share what they have learned over the years.

This edition includes talks from some of the top well-known PHP community speakers:

• Laura Thomson of Mozilla
• Lorna Jane Mitchell
• Elizabeth Naramore from Github
• Keith Casey of Twilio

It's an online day-long event so you can participate from wherever you're at. You can still pick up tickets for the event from the main site - $40 USD for a single ticket, $100 USD for an "office party"

Recently in a conversation on Twitter the topic of what a successful conference proposal - one that gets accepted - looks like, came up. I thought I would expand upon the conversation and the "3 key takeaways" advice I gave, by providing the raw submissions I entered, in this case, to PHP Tek 12, as well as some lessons learned and additional commentary.

He shares his thoughts on what kinds of things it takes to get accepted (note: one is "luck"), what some of his example proposals look like, how to deal with some of the pre-conference jitters and a few final tips on getting that "accepted" email.

Some of the conversations I had during the weekend were around technical presenting at conferences and usergroups, so I thought I'd collect a handful of the tips that were discussed into a post, and use a few of my favourite speakers at the event to illustrate them.

He has it broken up by speaker, first David Zülke, Rowan Merewood and David Coallier, each with their own highlights of what they did well in their presentations. The list includes:

• Make concepts concrete with examples and demos
• Care About The Visuals
• Project Confidence
• Engage The Audience

Ian provides summaries for each of the points, describing what the speaker did to accomplish it and how it could be put into practice by other presenters.