- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or register to comment.
10 years ago this meme said “compiling” shows how much docker has made things more “efficient”
We’ve created this hell for ourselves
Tbh, all of web development has become this… efficient. I remember the days where I could create a website in PHP and have it done in a couple of hours (per page), and now the only way I can do that would be using AI and going full on “vibe coding” mode.
What do you mean? You can just make some react/typescript template and fastapi server thing, or any of dozens of equivalents, extremely quickly. I’m by no means an expert on web stuff as I develop software for controlling machines, but we used the above for some internal services in my last job and I could get a clean and functional site running in a day with no prior experience. I get that for public facing stuff you’ll have some higher requirements but I couldn’t imagine those wouldn’t apply just because you’re coding in PHP…
PHP still exists though.
Maybe it’s time to go back to the good ol’ days
Yeah, but why would I use it when much worse options exist
Someone doesn’t know how to leverage Docker BuildKit
Is there more to it than using multistage builds when appropriate?
Not really, no.
Visual Studio is starting
Any minute now…
I was going to watch a tuto on how to be more efficient but YouTube is still buffering
DevOps, not programmer.
I wonder what the dev part of devops means.
Devil 👿
At my previous job, we had a “Devops” team. We even outsourced some ops to a third party in the worst possible way (I’m talking “oh you want to set up an alert for something related to your service? Send us an email and we’ll look into it” and so on). All the pre-devops pain magnified by an order of magnitude. Sometimes devs would do their own ops (I know, big shock!), and they would call it “shadow devops”. Nearly fell off my chair when I first heard it. Kinda glad I’m not with them anymore.
Short for devine
Most programmers are interacting with containers these days.
The real question is why their build is taking so long.
Because of a few strategically placed wait commands.
Why not? Why doesn’t the programmer want to test a container?
True. Nothing beats running your unit tests in the actual container image that will be run in production.
Race condition that only happens on the much faster production hardware: Allow me to introduce myself
Or an issue that only appears when using ARM and not on my AMD64 dev machine
Unit tests can’t win ’em all. That’s where things like integration tests, staging environments, and load testing come in.
The final layer of protection is the deployment strategy, be it rolling, canary, or blue-geen.
I mean, isn’t that kind of the point of containers? To basically have the same environment everywhere.
Yeah, and it’s useful to just check everything so you don’t forget to add some essential system package for e.g. SSL, especially when working with Alpine.
Guess I must turn in my programmer-badge.
Apparently doing more than one thing makes you not a programmer 😔
what if I’m doing my programming inside a devcontainer?
Devops isn’t a role.
Platform Engineer maybe, but even then I’d say they were “developing” the platform.
