In the past half hour, two things happened that made me raise an eyebrow.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano Dear lord, most people in this industry have no fracking clue anymore.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano is this what the LLM is telling him what to do?
-
R relay@relay.mycrowd.ca shared this topic
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano "...and if the host gets dirty it doesn’t matter, it only has to run the containers"
This makes absolutely no sense and makes me wonder if you're being trolled. No one could be this ignorant of how computers and operating systems and containers actually work, while maintaining employment in the field.
I hate car-computer analogies, but it's the equivalent of saying "so what if I lock up the engine, the trunk still holds my stuff". Sorry mate, you're still going nowhere if you break the engine.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano I am of the opinion that a few years spent in IT Operations is a darn good prerequisite for other roles in IT.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano you need analogies …
That’s installing a GUI on a router so you can debug a web app.
-
@stefano you need analogies …
That’s installing a GUI on a router so you can debug a web app.
@stefano That’s like reprogramming the airport’s radar system so one passenger, a dev of radar apps, can test a new phone radar app.
-
@stefano That’s like reprogramming the airport’s radar system so one passenger, a dev of radar apps, can test a new phone radar app.
@stefano Containers are musicians; the host is the conductor and the sheet music stand. You can hand one musician a weird experimental instrument, but if you start swapping out the conductor’s brain mid-performance and it crashes, the whole orchestra stops.
-
@stefano Containers are musicians; the host is the conductor and the sheet music stand. You can hand one musician a weird experimental instrument, but if you start swapping out the conductor’s brain mid-performance and it crashes, the whole orchestra stops.
@stefano Containers are the train cars; the host is the locomotive. If you keep bolting random test equipment onto the locomotive and it fails, all the cars stop, because none of them move without the engine.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
I wonder if this developer understands anything
-
@stefano Containers are musicians; the host is the conductor and the sheet music stand. You can hand one musician a weird experimental instrument, but if you start swapping out the conductor’s brain mid-performance and it crashes, the whole orchestra stops.
@matuzalem @stefano I like that analogy!
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano@bsd.cafe Was that his idea, or was it from some SlopGPT agent?
-
I wonder if this developer understands anything
@angel It's probably one of those IT guys who has already been replaced by AI. Or at least his brain was.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano oh dear, and it is only Monday!
-
@stefano Dear lord, most people in this industry have no fracking clue anymore.
Many of them often think that when they came from computer science school, they know all the important things of The Craft
In reality they won't even be able to start up a server park
-
@stefano@bsd.cafe Was that his idea, or was it from some SlopGPT agent?
@adnan his, unfortunately...
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano Thank you for the smile
-
In the past half hour, two things happened that made me raise an eyebrow.
The first: a developer, who uses Docker on both a dev and a prod server, asked me to install a huge number of dependencies (on the host) to test a workload. When I hesitated and suggested using a container instead, he replied that this way he "keeps the containers clean, since they’re what run in production, and if the host gets dirty it doesn’t matter, it only has to run the containers".
I tried to explain, but... no, we're not getting anywhere. My brain is short circuiting.
The second will follow later.
@stefano *chef's kiss*
️
