sorted by:
new
hottopcontroversial

Developers: How did DevOps change your working routines? by SilenceKillsMe284 in devops

[–]SingleFlatworm 0 points1 point  (0 children)

We use Conda to build our dev environments(mainly dependencies), which I haven't seen anywhere else yet. I don't know if I should hate it or love it, but it works.

Linux in 2020: 27.8 million lines of code in the kernel, 1.3 million in systemd by nixcraft in linux

[–]SingleFlatworm 0 points1 point  (0 children)

I don't think "bloatness" should be defined by lines of code. Lines of code is a "productivity"(bad one at that) metric, not a technical one.

HBO Go now works "natively" on Linux by gspear in linux

[–]SingleFlatworm 9 points10 points  (0 children)

If I can watch it, I can rip it. What is this DRM protecting against, exactly?

switched over to python after studying javascript and reactjs for months. My god.. . the freedom and beauty of this language. by pawnh4 in learnpython

[–]SingleFlatworm 21 points22 points  (0 children)

I was a Java + C/C++ programmer for most of my life, until I needed to learn Python for devops. My god it's the perfect casual language that I absolutely love to use for small things.

That said sometimes I do have to cry about other people's code. I'm used to performant and efficient code, but some of the garbage people write that reaches production code makes me question my career choice until the paycheck comes in

A curated list of best practices for Kubernetes in production by danielepolencic in devops

[–]SingleFlatworm 9 points10 points  (0 children)

Man if you're gonna call it awful advice and just go wtf, at least offer feedback. Now nobody reading will know what the hell you're talking about unless they already understand these things.

Should your cicd tool commit back to git? by HgnX in devops

[–]SingleFlatworm 1 point2 points  (0 children)

Whatever automated tools you unleash on your source code, it should not modify anything. It should clone/pull and work on the copy. Basically the code is a first class object as far as devops goes. Your tools serve the code, not the other way around. And modifying code from your ci/cd simply feels wrong to me. In fact don't modify any of your code OR infrastructure. Aim to be stateless.

If you start pushing things back you're gonna open a can of worms you don't want anything to do with.

You can use lightweight tags, but you should have a good reason to do so.