I made my passion my job, programming servers & web dev. Although it has been productive economically it has sucked the fun out of programming servers for me...so as a way to rediscover my passion I'm giving game dev a try. After a couple of weekends playing with a game engine this is what I've got, a monkey dev with a suit that jumps from project cabinet to project cabinet avoiding hazards, drinking coffee and trying to make some money (someone told me I should express myself and I took that personally).

I'm pretty much done but the hazard placeholders (a box and an arrow) don't convince me so I wanted to see if my fellow disenfranchised developers had some ideas of what my developer should be avoiding/being hit by, preferably something I could draw easily since as you can see I'm not much of an artist although I've also though of just words falling like "deadline" or something.

Anyway any feedback is welcome, take it ez I've never drawn anything more than a stickman and this is my first attempt at something playable. Small Rant plus question. Happy Monday.

Boss was advised a collar and belt by doctor when he complained of back pains. He's 18 years in this software industry.

I completed 10, occasional aches and pains, time to start yoga lessons.

Over the last few weeks, I've containerised the last of our "legacy" stacks, put together a working proof of concept in a mixture of DynamoDB and K8s (i.e. no servers to maintain directly), passing all our integration tests for said stack, and performed a full cost analysis with current & predicted traffic to demonstrate long term server costs can be less than half of what they are now on standard pricing (even less with reserved pricing). Documented all the above, pulled in the relevant higher ups to discuss further resources moving forward, etc. That as well as dealing with the normal day to day crud of batting the support department out the way (no, the reason Bob's API call isn't working is because he's using his password as the API key, that's not a bug, etc. etc.) and telling the sales department that no, we can't bolt a feature on by tomorrow that lets users log in via facial recognition, and that'd be a stupid idea anyway. Oh, and tracking down / fixing a particularly nasty but weird occasional bug we were getting (race hazards, gotta love 'em.)

Pretty pleased with that work, but hey, that's just my normal job - I enjoy it, and I like to think I do good work.

In the same timeframe, the other senior dev & de-facto lead when I'm not around, has... "researched" a single other authentication API we were considering using, and come to the conclusion that he doesn't want to use it, as it's a bit tricky. Meanwhile passed all the support stuff and dev stuff onto others, as he's been very busy with the above.

His full research amounts to a paragraph which, in summary, says "I'm not sure about this OAuth thing they mention."

Ok, fine, he works slowly, but whatever, not my problem. Recently however, I learn that he's paid *more than I am*. I mean... I'm not paid poorly, if anything rather above market rate for the area, so it's not like I could easily find more money elsewhere - but damn, that's galling all the same.