breakalot

The problem is that devs simply can't accept that ops exist.

We spoiled devs way too much.

Software are still being thrown over the wall and ops takes all the blame.

The problem is that many devs can get away with spawning servers and doing the easy parts of ops, when it requires rules and discipline, then we all know what happens, over engineering and security holes.

Nowadays employers fail miserably at fulfilling basic needs like, believe or not, giving someone a Linux computer.

Yes, can relate.

Working in a field where people can get frustrated very easily is though. Specially if you are in the receiving end.

I worked with a lot of nice colleagues that makes the job more enjoyable, try to focus on that and ignore all the negativity that come from the loud ones.

Try to grow with the pain to the point it goes away, for example, for me it was soul crushing discussing something infrastructure related and having someone who doesn't know much about it suggesting serverless, using low effort arguments, instead of paying attention to the subject of the discussion. After some time I realized that people can be jerk for the sake of it and in the corporate world you are gonna find many of these. So for me what worked is to think that people are passionate about different things and it's your job to keep yours alive and ignore people who likes to create havoc.

Then do your job and when is time to go, simply go. I know it sucks to have a pile of code to review because people without social life are working during the weekend, but you will have to establish some boundaries to protect your time.

RIP Deis

That is great! I wish xrdesktop would be updated to gnome 42 and upstreamed one day.

The resource IS the state!

Perhaps using guard you can automate that https://github.com/guard/guard

Perhaps buildbot as a Jenkins replacement https://buildbot.net/

Usually codebases are organized into modules/classes/etc and most test suites can run specific test cases (or groups of tests, specific domains, etc).

I think if you can't do that in a codebase, then one has bigger organizational problems than the technology itself.

Also assigning many developers to work on the same set of files is a recipe for disaster (if said developers cannot get along or organize themselves) while working on the very same place/file.

Microservices was always a solution to the organisational problem of getting more developers working on a system at once.

Wasn't Continuous Integration (CI servers) created long ago to solve that?

Where developers can test and release their own changes, incrementally, without stepping on each other toes?

What is next?

You mean "duplicate"?

I think we, collectively, should strive for avoiding making other people's life stressful.

Just by having a different role, title or label attached to you can be pretty stressful by itself, specially if you are out numbered and decision making is done by number of hands.

The majority not always get that. Also is so common to be exposed to other people's frustration when explaining things, or denying a request, balancing between letting someone shoot their own feet, explaining once again why that is not a good idea, or just restoring a backup later.