Good information. I picked up a couple of things and I have been a sys admin for years. One element of the talk I would caution. The auto creation of firewall rules. If I was a hacker and found I was being blocked I would suspect auto rule creation. I would renew my attack and spoof my address as his default gateway.
I think the speaker had somewhat underestimated his audience. This was good information for an audience who had no idea what accessibility is. As it was however, this was very basic info.
The demo application was awesome, but I feel this talk suffered from trying to stuff 6 talks worth of information into a 45 minute session. Nate tried to cover TypeScript, React, ES6, Functional Programming, JavaScript architecture and a very cool in-memory object registry and ended up with a talk that left me asking a ton of questions with no time left for any answers.
I feel like this would have been a highly challenging talk to keep up with even at a JS conference where you could reasonably expect most attendees to be at least passingly familiar with most of the tools used.
great talk, great speaker
Loved the talk, engaging, funny, and entertaining. It wasn't really a talk that you would walk away from with an epiphany and that's ok. Hearing others stories of dealing with disasters is alway a good reminder that we are all in the same boat.
Well presented, and well designed talk. Mike's a repository of SOA knowledge, there's a lot more I'd like hear from him on this topic. Perhaps a series on SOA? The code samples got a little hard to follow due to formatting constraints, and I would have benefited from a little more, "here's the wins you get from SOA, and here's why this wouldn't have worked out without it." The CLI example was particularly helpful. Sharp, clean looking slides were appreciated as well.
Engaging talk about the human element of software development. After a weekend of technical talks, this was a great reminder that (to paraphrase) we are humans making software for humans, and to err is human. Recognize that mistakes are going to happen, and plan for them.
Very good tips, very good talk. Came away feeling inspired. I'd still like to hear more of how to take those first steps, even if it's by way of example. Sort of like, I've decided to freelance, I've never freelanced, now what? What do I do day 1, week 1, month 1, year 1? (Maybe I just need conference talks as a service...)
Anyway, thank you, very helpful, very well done!
Shout outs to RFC 2616? Clear explanation of what defines a REST API? Engaging presentation? Check, check, and check. Well done!
My only ask would be some discussion of what alternatives to REST are out there. (I often feel like every API is a REST API, that varies in the success of its implementation. Some high level coverage of for example, SOAP, would have helped me. But maybe this is better left to another talk? *hint hint*)
This tied for my favorite talk of the weekend. Great information and at just the right technical level. I finally figured out what I was doing when I was copy and pasting in a TLS setup string. --And, even more valuable, found out i was doing it wrong!