4 ms·

> I still haven't heard anyone say what not having containers could win you. What types of code can you only write without containers? Code with one less layer

> I still haven't heard anyone say what not having containers could win you. What types of code can you only write without containers? Code with one less layer of abstraction. If that layer is buying you something you need, it's great. But abstraction isn't a positive in & of itself, it's why we get upset about GenericAbstractFactoryBeanSingleton(s).

jauntywundrkind 3y ago
What would you change about your coding because of deploying in a container? What do you tell your junior & senior engineers to do differently? I call bull frelling shit. It's not an abstraction. It's a deployment pattern. It doesn't affect how or what we code. Endless shitty pointless bullshit grousing, over nothing. It doesn't actually matter. It's just hip, you get to feel good, by pretending you are dunking on sheeples. Frivolous counter-cultural motions that people use to make themselves feel advanced & intelligent. But actually, being free of this pattern doesn't really buy you anything new or different. The same code & the same approaches are viable with our without. It just feels good to be shitty to the mainstream. If there were abstractions maybe there would be some justification for the slippery slope "oh no!" panic. And K8s is definitely some kind of abstraction. But the sloppy slippery slope "oh no abstractions" shit still pulls no weight for me, fails to acknowledge that sometimes abstraction can & is useful, allows good things.
- inhumantsar 3y ago
  > frelling damn I had to dust off some cobwebs for that one
- dwattttt 3y ago
  > What do you tell your junior & senior engineers to do differently? I tell junior & senior engineers to be careful about what assumptions they make of their environments, and to consider everything they depend on a potential liability.
p_l 3y ago
Containers on kubernetes are major part in allowing me to put less abstractions into code directly, if only because I can reduce bits that would be built-in or in messy companion scripts into more or less standardised patterns in k8s
birdiesanders 3y ago
Containers are not code abstraction, they are environment encapsulation.

jauntywundrkind 3y ago

What would you change about your coding because of deploying in a container? What do you tell your junior & senior engineers to do differently? I call bull frelling shit. It's not an abstraction. It's a deployment pattern. It doesn't affect how or what we code. Endless shitty pointless bullshit grousing, over nothing. It doesn't actually matter. It's just hip, you get to feel good, by pretending you are dunking on sheeples. Frivolous counter-cultural motions that people use to make themselves feel advanced & intelligent. But actually, being free of this pattern doesn't really buy you anything new or different. The same code & the same approaches are viable with our without. It just feels good to be shitty to the mainstream. If there were abstractions maybe there would be some justification for the slippery slope "oh no!" panic. And K8s is definitely some kind of abstraction. But the sloppy slippery slope "oh no abstractions" shit still pulls no weight for me, fails to acknowledge that sometimes abstraction can & is useful, allows good things.

inhumantsar 3y ago
> frelling damn I had to dust off some cobwebs for that one
dwattttt 3y ago
> What do you tell your junior & senior engineers to do differently? I tell junior & senior engineers to be careful about what assumptions they make of their environments, and to consider everything they depend on a potential liability.

p_l 3y ago

Containers on kubernetes are major part in allowing me to put less abstractions into code directly, if only because I can reduce bits that would be built-in or in messy companion scripts into more or less standardised patterns in k8s

birdiesanders 3y ago

Containers are not code abstraction, they are environment encapsulation.