Then change the keyboard shortcuts of your terminal so that it does that. If you can’t, then switch to a terminal that lets you change the keyboard shortcuts.

A neat thing is that a lot of command line programs use readline. So learning and configuring it will also be useful in for example the Python REPL and calc.

Here are some neat configuration options you can put in ~/.inputrc

set completion-ignore-case on
set show-all-if-ambiguous on
set completion-prefix-display-length 9
set blink-matching-paren on
set mark-symlinked-directories on

And if you are a sensible person who is used to vim

set editing-mode vi
set show-mode-in-prompt on

I could change it in the settings. I just hadn’t used it in a long time and it took me a bit to realize that this default was why I suddenly had trouble telling the tools apart.

But if the differences are that big I’m probably still on 2. Looking forward to seeing what 3 will bring then :)

I found Inkscape when I needed to make some diagrams, and even though that’s not really what it’s for, it blows dedicated diagram tools out of the water.

Inkscape is actually fun to use because it strikes a nice balance between easy and powerful.

My only problem with GIMP lately has been that by default it’s used monochrome tool icons which are really hard to tell apart. Which seems like a real form-over-function decision (likely made by the distribution though).

My experience with Jetbrains was that they did not rely on vendor lock-in, but on actually making a product worth paying for. I could move my projects away from their suite easily, the build tools and scripts where all third-party open-source. I just didn’t want to.

But perhaps things are different in other spaces. I can imagine using Kotlin might lock you in more.

Just shifting the tax burden from salaries toward capital should make it less of a problem. When capital income is taxed less than salaries wealth concentration gets worse as workers are replaced.

But hey, GDP line goes up, so it must be good right?

Completely depends on how you live.

Someone who lives in a house with plenty of storage and a 30 minute drive to the nearest store will have a lot of food at home. Whereas someone who lives in a tiny apartment with a five minute walk to the store will not.

In general, places like American suburbs, with huge single-family homes, no stores and complete reliance on cars, are rare in Europe.

Moving fast doesn’t have to mean poor workmanship.

To make an analogy, if you want to be able to make a cup of coffee fast, you need to make sure that the coffee beans, the water, and the brewer are all near each other, that there is electricity and that the water is running. These are all things that enable you to move fast, but they don’t decrease quality, if anything they increase quality because you aren’t wasting time and effort tackling obstacles unrelated to brewing.

Which is in fact the point of the article. That you should make sure you have a good development environment, with support systems and processes, so that you can work effectively even if your developers are not savants. Rather than trying to hire people who are good enough to do a decent job even in the worst environments.