This year I have been participating in the Advent of Code, a yearly (for obvious reasons) event where a new puzzle is released each day of Advent which requires some coding skills to solve. It has been fun so far and I’m sure it’s only going to get harder. It’s an excellent opportunity to practice some algorithm skills and also to learn some new things. The Day 4 challenge titled Giant Squid involved playing some games of bingo against a giant squid.
Cookie banners suck, and a lot of websites do them very badly. When I launched unravelled.dev I included Google Analytics since I wanted to know what posts were the most read, you know to give me an indication of what my audience was most interested in. However given that this is a developer centric blog I suspect that a good amount of visitors have browser based ad blockers or use something like NextDNS to block analytics from being collected.
Earlier this year I decided I wanted to get back into blogging, and nothing screams getting back into blogging then changing the platform you’re using! I had been a long time user of Wordpress and blogged regularly from 2013 to 2016 and figured adopting a new platform is exactly what I need to do to get back into the swing of things. Side note: changing tech is not the answer, I spent waaaaay too long working through various issues related to Hugo, I got there in the end but I should have just stuck with Wordpress and spent the time writing posts instead of tweaking toml files 😱
I’ve been hearing a lot about Cloudflare lately, a few weeks about I read a post by Troy Hunt where he talks about one of his recent experiences using Cloudflare Workers. Prior to this I had read about doom scrolled past tweets about Workers, but never had a chance to try them out. And again this weekend someone I follow on Twitter posted about Workers again, so I figured it was now time to give them a try.
Lately I have been building a socket server for one of my clients, this has taken the form of a Windows Service since there is no Azure PaaS offering that allows you to accept raw TCP socket connections. The socket server is for an IOT device to send raw TCP packets to for processing. As part of the project I’ve also been working on the automation side of things. This is an important aspect of the project, since I don’t want to waste time building the project locally, zip, connect to virtual machine, copy file across, unzip, update Windows Service over and over again.
Putting time and effort into developing Azure ARM templates for infrastructure deployment pays off in the long term, especially when all teams across an organisation adopt the same patterns. Recently at DrDoctor we’ve been developing an approach to generating boilerplate templates for new projects/service areas, but more about that in another post. So I thought there must be a way in the ARM template to conditionally add an access policy when running the ARM template in our test environment.