Buy food that you can eat without cooking it. Or where cooking is extremely easy.

Meal prep? Just cook more than you need when you cook. Then you have leftovers.

Buy: eggs, tomatoes, carrots, bell peppers, fast cooking pasta, canned fish, bread, cheese

Systemd is more important than GNU.

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

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.

Scripts and aliases make this easy to set up.

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

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.

Why do engineers do this?

Simply fix the relevant technical debt as part of implementing a feature or fixing a bug. That way you can chip away at it over time.

Waiting for the big removal of technical debt will never come. It’s an ongoing process.

Leave the code base better than you found it – always.

due date next Thursday

The answer is to say “We will try our best, but this is very ambitious.” Then you let the deadline pass, usually it’s artificial in the first place. When the deadline passes say: “As we feared this took longer than we hoped for.”

Thanks for the reminder to take a few deep breaths.

Yes, but it’s possible to make it fun and be happy.

Scales according to five year plan.

It probably runs on Wine/Proton.