F-W-M

I live in germany and work in an international company. I am the only german on my team. A lot of the younger colleagues blame their difficulties on making friends on german racism and stay in their expat circles, but the truth is: it's hard for everyone here.

It requires good familiarity with code base or domain knowledge to know that one has to grep and for how long. The abstraction triggers you to look at the right places.

That said, I am firmly in the camp that requires at least three instances.

> for instance, I'm a deep introvert, but I'm able to socialize for long periods of time and talk to strangers easily now, but only after I kept practicing for a period of 2 years -- I discovered it's possible to "bend" your introversion if you don't put yourself in a box and are willing to make an effort

How did you practice?

Rebase (with or without -i) is one of my most used git commands. The one thing I still get confused with is whether I have to commit to continue or not.

This must be how dwarf fortress does it

They play a big role in hardware design and verification as well. All in all, SAT solvers became very good, so the solution to many NP-hard problems is to encode them in SAT and solve them this way.

Package manager, Static Analysis, Model Checking (like TLA+), probably scheduling software.

I'd concur that these are interesting but maybe seldom used pieces of software, except for package management.

The Corps still exists. Less of them, with less members, and less fighting. But we still get fat from drinking too much beer.

Am kind of using this at work. All IO is isolated in an imperative shell layer, that communicates with an core via event. The core is kind of a state transformer, but actually does in place mutations. All state (of the business logic) is kept at one place, which has some nice benefits.

Functional programming is not too important in the core, a lot of benefits arise without it, e.g.: I can replay a prod session from the events generated and get the exact same behaviour. Makes debugging a breeze.

One advantage of having the state in one big place is that I can serialize it, send it to another thread that serves a UI from it.

Same, had the two most productive years of my working life, worked my ass off, build them a system that now makes my salary 20-30 times. Now I am forced to come back in the office (and man did they fail that communication), don't see any real appreciation for the work I did, and I am like 20% as productive as prior.

Funny thing: I am still meeting expectations.

I was going to get treatment for burnout. Turned out the best treatment was a private office.

I learned that the hard way, that I am at a place where people are on the left side of the bell curve and that you shouldn't be developing your own stuff with such a team.

Cost me some credit. Now I am trying to get us away from the awful mess we produced.

I once found

``` if (var) assert(var) else assert(!var) ```

in the outsourced test suite for a level A air plane software.

I am using Rust's insta to do the same (but not as streamlined).

I want a meaningful commit history, that actually enables me to find the useful commit message. My coworkers often create PRs where the branch itself contains merges and a lot of bad commits that are not centered around a single piece of functionality or activity (like formatting, refactoring).

I try to have them clean it up but often the best thing I can get is a squash.

> At least here in Denmark, companies like Lego and Vestas are doing some really groundbreaking money making at a much lower cost, by not going to "standard" systems for everything.

Do you have an link to an article about this somewhere?nn

What are you using instead and what are the main criticisms of kubernetes from your seniors?