Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



> 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.


> frelling

damn I had to dust off some cobwebs for that one




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: