Systemd is more important than GNU.

They are both pretty extreme.

Do something fun and nourishing in your free time.

Complex work projects will always suck in one way or another. Just accept it. Do what good you can. It’s all you can do.

Be kind to yourself. No need to hold on to unrealistic expectations.

Fossil scm does that

There have been major protests by key members of the military like pilots against the planned judicial reforms before October 7th. That event unified the country like nothing else since the Yom-Kippur-War.

Israel is loss averse because of their citizens army. That bleeds over in their tactics as well. This manifests for example in destruction of whole houses and roads instead of clearing explosive traps, mines, and IEDs one by one at a higher risk to soldiers.

A large part of the secular left in Israel hates sending their children to defend fanatical settlers in the West Bank.

The war against Hezbollah in 2006 was cut short because of losses and protests.

Universal conscription isn’t a perfect solution, but it creates stronger bonds between military and the general population.

That’s one of the better ideas in the paper. It could lead to lower willingness to go to war.

It’s necessary because people develop software with Macs.

macOS just makes you jump through a hoop every time you run an application that’s not notarized.

In practice that means cross platform open source projects don’t want to pay money to join apple’s developer program and set up code singing and deal with certificates.

So after download an unsigned app, macOS refuses to start it until you go to system settings > security > and allow.

You have to do this again after every update.

It’s very annoying and does very little for security.

Not if you’re doing it while traveling.

Hitchhiking and couch surfing is a thing.

Scripts and aliases make this easy to set up.

What do you mean by natural? Do you want stateful APIs?

Leather can last for many decades if treated well. Vegan leather aka plastic lasts a few years tops.

No, you tell about management the problem and how only their amazing social and people skills will be able to do something about it.

Multiplying by Pi is what I do. :)

This kind of social behavior is corporate politics and a failure of management of course.

Code presentations are great for that.

One or two people present their code before the merge. Others watch, ask questions, etc. Small changes and improvements can be done immediately. Ideally the change is merged after the presentation. It can speed up things immensely and more people feel ownership. If a simple ticket stays in review for a week, it can be very detrimental.

Read the JSONL into a real database like Postgres.

Dysfunctional engineering teams, that have no empathy for end users is an issue as well.

A good alternative is code presentations.

You present your changes to a group of engineers. Then discuss it.

argue

Yes, it happens too often. That’s a failure of leadership or a social problem.

Techies often try and fix human and social issues with technology, but that doesn’t always work.

Code review helps spread knowledge about the code base through the team. Without it, you easily end up with disjointed fiefdoms ruled by petty code lords that don’t share information.