This is the 3rd blog post in my LINQPad Tips and Tricks series. The first two posts can be found below. If you haven't read them already, I'd highly recommend having a look through those as well as this post...

One of my goals this year was to do a talk at a developer conference. I did a few talks at .NET Oxford last year, and wanted to take my public speaking a little bit further, and the fantastic Developer Developer Developer conferences gave the perfect opportunity! For those that haven't heard of these conferences - there are a number of them throughout the year at different locations. They're always free to attend, and always on a Saturday. This means that most of the attendees are there because they want to be there, not just because they've being sent and paid for by their work. I've been to a few now, and there's always a really great community vibe.

UPDATE: Since doing this lightning talk, I have also done an extended hour-long version at a couple of the DDD conferences. The full blog post about the hour-long version of the talk can be found here. That includes everything that is in this post, plus a lot more. So probably worth reading that one instead of this!

I'm a heavy user of Workflowy, which is an amazing tool for taking notes. Due to the very hierarchical nature of Workflowy, I had a random idea that this would make a very cool Neo4j visualization! So I made a thing, and put it on GitHub.

On Tuesday it was our fourth .NET Oxford, and this time we had a slightly different format ... In order to give more people the opportunity to get up and talk, we decided to go with a lightning / grok talk event. There was actually quite a lot of interest, and the speaker slots filled up very quickly with a really good line-up ...

I was recently investigating issues in some scheduling and dispatching code, which was actually quite difficult to visualize what was happening over time. So I decided to reach for the ELK Stack to help me see what was going on using time based charts. I've only used this briefly in the past, but given the very simple setup thanks to Docker, and also the power and flexibility of ELK, it made a huge difference in my investigations!

This is my second LINQPad Tips and Tricks post. If you haven't read my first post, I'd definitely recommended reading that one first, and then coming back to this one ...

(Also see LINQPad Tips and Tricks - Part 2, and Part 3)