slumpa

> a new name for System Administrator.

Yes, this is definitely happening.

I try to frame "DevOps" roles not as "doing DevOps work", but instead "enabling DevOps work". So, for example, setting up systems to make it easier for developers to take control of their own deployments and environments.

I spent the last 3 years teaching at a software bootcamp, after being a SWE for 8yrs. It's been super rewarding - you're working with adults who are often in a hard spot financially and personally, and you get to help coach them through a major challenge, and see the positive outcomes for them.

The pay will likely be much higher than teaching elsewhere (though I still took a 30k cut). Some bootcamps are more legit than others, so just do your research first

Ever tried running JS libs with C bindings? You're going to run into the exact same problems as you have running python code with C bindings.

Exactly, thank you! This article just read so bizarre to me - who thinks that venting is supposed to change your opinion about the matter? It felt like reading a headline like, "Researchers find that cardio vascular exercise doesn't help increase shoe size"

That's not what it's for. It's for getting thoughts out of your head, having the opportunity to articulate strong feelings that might otherwise be fuzzy, and for feeling heard and supported.

If changing your opinions is the goal, venting is pretty clearly not the way to get there.

I love the idea behind this - as a software engineer, it's your job to build good processes, and not something to ask permission for.

But wow, some of this post is incredibly toxic and passive aggressive. Create your own personal bug tracker, then refuse to fix any bugs unless everyone else uses it? "Neutralize the bozos" by sending them incessant bug reports, until they're no longer productive? Can you imagine working on a team like that?

I totally agree that you should incrementally work towards hardening your systems. Inasmuch as it's something you can fit into your workday, I'd say that's just part of your job.

Before I rebase, I always create a "backup" branch (`git branch backup`). Then if I mess up, I can always reset back to it (`git reset --hard backup`). Maybe better than trashing and re-cloning :-)