Weekly Dev Update 8
RTSP Server | Serverless | Microservices | Go Web Dev
More of an update on how the year has gone nearly 3 months in, where projects are at, where they’ve progressed from, and some skills picked up along the way.
Project Pact
This is a web development project, fairly simple http server, using Go’s standard library for as much as possible in order to learn as much as I can about http servers with Go. There’s a UI for un-signed in guests, with features locked for signed-in users, as well as paying members having all the features. Users have either a ‘manager’ or ‘worker’ role, and managers assign tasks to workers with requirements. Workers complete those tasks, and submit for review. Some nice automation features along with that baseline theme.
Yearly Dev Update: 2025
Repo Status Updates of The Year
SaorsaDev Blog
complete This blog was made just this year, believe it or not! I made it to try and draw me away from LinkedIn. But LinkedIn feels so much more casual, I’ve always opted in that direction when able. This year, I’d like to get better at feeling like my LinkedIn posts could just be blogs I link to. But that means way more content on this blog, which isn’t a bad thing, it’s just a bit of a transition. Nonetheless, despite a lot of complications with configuring the Ananke theme on this blog, it seems to have worked out for the best.
Weekly Dev Update 7
More Game-Dev | Vacation | Focus
Game Dev
Since beginning to work on my game, I haven’t made many posts on the blog. I have been engrossed in the project from head to toe. I haven’t ever found any project quite so fun to build and the challenges have been enlightening.
Part of what convinced me to make a game, was watching a video by Jonathan Blow, discussing that, when you get good at one kind of programming, it creates a plateau. You tend to overcome the same similar problem over and over again. Even if there are a hundred problems you might be solving, there are a hundred thousand problems that exist, but you’ll never run into the other 99.9% of problems if you only ever program in one narrow industry.