Good overview talk of the Microservices concept, although I would have liked a bit more examples of how (and where in the architecture) the services are tied together.
As a tip, Stephan (if you don't mind getting one from a noob), I'd say that you could cut down on the terms "and what-not", "whatever" and "or something". You really know your sh*t, but those words hide that fact a bit.
[4-out-of-5. Filing a but report with joind.in that ratings dissapear when you edit a comment.]
I had an absolute blast, and I especially liked how the social and the sponsor area kind of blended together for a choice of activities and a super ambiance.
It was great for my because I'm really interested in seeing PHP evolve as I learned programming in C, C++ the things I found so great about these languages are being briught to PHP. And overall it was nice.
Good talk, really enjoyed it.
Nice balance between theory/philosophy and real-life (the latter includes the hangover-y bit :P).
I'm such a huge fan of Mathias, I always think the next presentation *must* be the one where he slips, and doesn't manage to hit that high expectation. And yet, once again: 5 thumbs up. In content as well as presentation.
If there is anything to improve this talk, I'd say that the technical debt bit should include a little bit more of the background (like the uncon talk at DPC14). But hey, that's just a teeny tiny bit of personal preference...
It was the talk I liked the most. I do mis a lot of background information on why something happened or why a decision is taken around things told in talks. Joeri gave this great intro so I did understand why something happened. This is a better thing for other speakers to concern about.
And ofcourse it was an interesting topic overal I really enjoyed.
Thanks for the talk, it was really interesting and I appreciate you raising awareness that hacking of sites happens.
And that there are things you can do about it, when it has happened and also before (the next time) it happens.
I also appreciate you taking time to interact with the audience and make us share stories about hacks. This really made the possibility of a hack more real to the everyday developer, I think.
As a pointer I would like to say, maybe, in the beginning of the talk sketch the options you have when one of you're sites has been hacked.
Including, but certainly not limited to:
- just redeploy the application and cross fingers.
- forensically check all files, the database and the OS.
- go nuclear and make a backup of the hack for forensics, wipe the server and start with a fresh OS, fresh deploys and a forensically rebuild database.
- or just hire a professional, as mentioned by Ike.
And maybe touch upon in what situation you would advise the different options + the cost associated with each one.
Also you might explain a bit about the different metrics one should take into account when choosing an option. Like:
- confidentiality of the data used on the site
- impact when the site is compromised
- maybe risk of fallout, when some infection slips through the clean-up process
And maybe gloss over the most common infections people face when getting hacked:
- google ranking hijackers (like shown)
- ad injection (maybe)
- spam bots
- rootkits/root access
The above are all suggestions, I am by no means an expert in this field. But these were things going through my mind when thinking about improvements for this talk.
I really enjoyed it as it is, though, and I appreciate you getting on stage even when you were a bit under the weather.
I like the talk subject and content, but the execution was a little troublesome. There is quite a lot of code, and the slides don't fit so you needed to scroll *during* the presentation. Even you missed the next step at some points.
Plus, you're taking people along on a build where they have to keep track of the changes in their mind... hard work for tired minds ;-)
But: I feel if this presentation was a tutorial, you would have rocked it 100%!