I kinda want to play this game.

I haven’t watched the video, but two things I wonder:

• Surely he signed an agreement when he was hired promising they could hit him with an enormous lawsuit if he ever spilled “muh trade secrits.” I’m wondering how he got away with this unless all he’s sharing is public info.
• Is anything Atlassian has done really that non-obvious that anyone couldn’t just reproduce (or improve on) it from scratch just given some thinking and elbow grease? (Like, Confluence is a glorified WYSIWIG editor. Bamboo is Jenkins slightly spiffed up so it doesn’t still feel like something straight out of 1991. And Jira can be easily procured by anyone willing to travel to hell and request the next steaming shit Satan takes.)

Just get hired at any company that’s heavily pressuring employees to use Claude or whatever and employees are drinking the Koolaid. You’ll spend much of your time fixing LLM fuckups.

Very probably if you can’t think how it would be beneficial for your use case, it won’t be beneficial to your use case.

“Website” (as opposed to “web app”) sounds like something static with no server-side logic (save serving up static content) which further makes Docker not seem very useful for your use case. In your shoes, if I haven’t inferred too much, I’d probably first think of some CloudFront/S3-based solution.

Typically, Docker is used in cloud infrastructure (AWS or the like) in situations where there’s a lot of server-side resource usage and you want to be able to scale up on very short notice. It can also be useful for on-prem sort of situations, or for if you want to run server-side software in a “contained” sort of way where you don’t have to install your software’s dependencies on the host machine. (Running a Java app on an EC2 node without installing a JRE on the instance, for instance.) Docker is also good (particularly relative to PaaS options) for minimizing vendor lockin (though, again, only really if you have server-side logic to contend with, and if you’re dealing with a static website, it’s hard to imagine vendor lockin being an issue.)

I suppose you could shoehorn it in. Stick your static website on an EC2 node with a Dockerized Nginx to serve it, or even bundle your static website into a Docker image, but I’d imagine you’d pay more for such a solution than just using CloudFront with S3 or whatever.

(And yes, I keep mentioning AWS, but there are lots of hosts out there. For the more focused LAMP-stack-providers rather than IaaS options, Docker would be of even less use.)

Now, even if you do intend to have server-side logic, I’m not sure Docker really adds much to the conversation unless your server side logic is expected to use a fair bit of CPU and/or RAM, you’re expecting to get a good amount of request volume, and you want to be able to scale horizontally very quickly.

Seems like the sort of thing that Nintendo will want to shut down. There are legal loopholes that can be taken to avoid copyright infringement in such cases (such as releasing a game engine without any reasources/assets a la the Super Mario 64 decompilation project), but it doesn’t look like this SM64-on-GBA project is doing anything like that. (Which is unfortunate. Other projects like the Link’s Awakening PC port that got shut down not too terribly long ago also didn’t take precautions.

Don’t get me wrong. I hope this project sees the light of day. I just don’t think Nintendo will let it. And I wish the creators of these sorts of projects would take the necessary precautions to avoid being shut down on copyright grounds.

Just try to be very very slightly above average. That should do it. Don’t go too far or you’ll get a B-.

(I’m sorry. I couldn’t resist.)