Middleware in Laravel 5 - Talk Abstract.md

#Middleware in Laravel 5

Middleware is a powerful feature of Laravel 5. In this talk, we'll briefly cover what middleware is, it's place in the Laravel lifecycle, and how to create it. Then we'll look at some real-world, in-production use cases that demonstrate the appropriate use of middleware to examine incoming requests, and situations where you might modify the out-going response headers or body content. Finally, you'll learn some use-cases where not to use middleware, and how to test it. Phillip is a web developer with 16 years of experience currently building solutions with Laravel for Cisco Systems, Inc.'s Learning@Cisco team.

Overall good, but you can make the ideas clearer by stating things more succinctly. It probably sounds obvious to say, but people are coming for what they can learn, so phrasing things on those terms can be more powerful. Example:

"In this talk, you'll learn what middleware is and how to create it. We'll go through real-world use cases to help you understand where middleware is appropriate, and where it isn't."

Also, I didn't really understand the 'bonus' call-out. I'd either explain why it special or just say you have 4.

• Would prefer not to use the word "heck".
• Is it 3 or 4 cases? Don't call the fourth case a bonus.
• What is Learning@Cisco? Should clarify so people understand what you're building.

Thanks for the feedback folks! I appreciate it. @nateabele you kinda nailed it @khromov good questions - Learning@Cisco is where I work, actually, but I'm not going to mention it in the abstract.

If my abstract can be longer, do I go into specifics?

For those who are following along, I've updated this abstract after having given the talk for the first time, based on what ended up actually being in the talk. Any further feedback is appreciated! 👍

Added a quick bio - is that appropriate?

I think a problem with this abstract is that I could have guessed everything in it. You say you're going to what this thing is, what its place is, how to create it. Then we'll look at some use cases, and situations where you might want to use it. Then we'll see where not to use it, etc.

This is all stuff that I could have guessed you would talk about in a talk about almost any technology.

Do you want to talk at all about why I would be excited about learning about this tech? I think you need to say something about why it's useful. At the moment this abstract is a bit like a bullet point for the talk, but an abstract needs to be a pitch. Why should I care about Laravel and why should I come to your talk?

If I was using Lavarel, I might be interested in this talk, especially since you also mention disadvantages which is quite rare (but very welcome). I do agree with Chris that you need to pitch the topic more. Maybe a catchier title? Or mention why exactly middleware is a "powerful feature" (or maybe even mandatory)? Or better use cases (as far as I can read from the abstract, you just work with the request and the response, which kinda is the same case)?

Also, do remove the bio. Most conferences have a separate field for that in their call for papers. The bio doesn't help the abstract.