Did you know that you can navigate the posts by swiping left and right?
I recently attended Progressive .Net Tutorials by Skills Matter. A colleague and I got booked into the conference at super late notice and had to manically rush to find a decent deal for a hotel, most of which had sold out of twin rooms. We discussed broadening the search to include double rooms but sadly the prospect of spooning was not to be, as we lucked out and got a cracking deal on a twin room near kings cross, winning.
Progressive .Net Tutorials was ran over 3 days, with a varying format for each day, but consistently had two talks on at once, meaning we had to split up for the majority of the blocks so that we could get the most out of the conference.
Skills matter have recently moved digs and they are pretty shweet.
Main points where timeouts, caching fallbacks, retries, circuit breakers, decoupling through message buses.
This talk was well delivered, well structured and useful. I didn’t get as much out of the talk as some of the other attendees may have as I work for a high volume consumer facing tech company, so a lot of the patterns are already in use at UNiDAYS.
However the retry’s coupled with circuit breakers was something new that I’m definitely going to do a workshop on within the company soon. I’ll upload the workshop as a blog post in the near future.
Ian used his own open source library throughout the talk, giving an overview, showed the code in action then took Q&A after each section. I felt that this was definitely the best structured talk of the event and that the pace was on point.
Links to github repo, Ian’s twitter and blog:
This talk was probably my favourite of the whole conference.
The talk was relatively high level and I would have loved a longer talk so that we could have got into the gritty stuff, like dead locks, synchronisation context, how the framework breaks up the async await code into multi-methods with call backs etc. But async await is a beast of a subject, and within the time frame it was a good level of detail.
Even though this was high level I did get rumbled on a small bit of syntax, as did my colleague. I did manage to resolve the issue quite quickly without googling but it really struck me that I need to code more outside of my natural habitat.
Links to github repo, Dylan’s twitter and blog:
Overall though these talks definitely left me with a sense that I need to get cracking on my own stuff, outside of the day job. Thus far it’s been a great success, this blog is an example of that, I immediately got cracking after the conference decided to use jeykll with github pages and here we are.
I think I’ll conclude here for episode one. Watch this space for episode 2 shortly.