Got my missile launcher, right here! Got my missile launcher, right here! Got my missile launcher, right here! Got my missile launcher, right here!

Thanks. I’ve legit never understood how to navigate Twitter. Both Twitter and Snapchat gave me a good dose of what I imagine my grandmother feels when faced with operating a desktop computer…

Is this a real post? I can’t seemed to find it on that website “X, formerly known as Twitter.”

Code never lies; comments sometimes do.

deleted by creator

🫡

Wow! I’ve been thinking about making something like this and I’ve even poked at a few “hacker/terminal/code” themed games. However, every time I get serious about giving this type of game my time, I think to myself, “I could just be programming and hacking something more useful than this, and I could just look at that experience as ‘the game’ rather than programming and hacking on something less valuable (the game, in this case).”

This train of thought has me working on an FPS built on Bevy. I’m hacking, learning, and convincing myself that this is the hacker game experience I wanted. Heck—I might even come out of this with something tangible that could generate money one day. At the very least, I’ve up-skilled my programming knowledge. 🤷‍♂️

That probably sounds uber boring and having said all this, I think I’ll still have to give this game a go!

I’ve found Docker helpful when I want to use it to build binaries or use CLI tools that may not be available directly on the CICD platform. Also, Docker makes it easier to run the same code on MacOS that I ended up running on a Linux CICD server.

What would you consider to be overuse of containers?

Most of those things mentioned aren’t bona fide needs for me. Once a developer is deploying their project, they’re watching it go through the pipeline so they can quickly respond to issues and validate that everything in production looks good before they switch contexts to something else.

I see what you’re saying though, depending on what exactly is being deployed, the policies of your organization, and maybe expectations that developers are working in another context once they kick off a deployment, it could be necessary to have alerting like that. In that case it may be wise to flex some features of your CICD platform (or build a more robust script for deployment that can handle error alerting, which may or may not be worth it).

Real talk- I agree with this meme as truth.

The more and more I use CICD tools, the more I see value in scripting out my deployment with shell scripts and Dockerfiles that can be run anywhere, to include within a CICD tool.

This way, the CICD tool is merely a launch point for the aforementioned deployment scripts, and its only other responsibility is injecting deployment tokens and credentials into the scripts as necessary.

Anyone else in the same boat as me?

I’d be curious to hear about projects where my approach would not work, if anyone is willing to share!

Edit: In no way does my approach to deployment reduce my appreciation for the efforts required to make a CICD pipeline happen. I’m just saying that in my experience, I don’t find most CICD platforms’ features to be necessary.