Hier kommt btw auch Wiederstand gegen Digitalisierung her. Ich hab hier mal im Hotel mit ner Altenpflegerin geredet.

Und, rein technisch ist die Digitalisierung erstmal ne Erleichterung. Ok, jemand komplett erfahrenes kann so nen Formular über nen Patienten in 5 - 10 Minuten ausfüllen, und die Software mit der sie gearbeitet hat war halt Scheisse, darum hat das 10-20 Minuten gedauert. Aber, dann muss man keine Formulare leer rumtragen, ausgefüllt abgeben, sortieren, Leute anmotzen um die Formulare rumzuschieben.

Aber… aus Gründen der grossartigen Digitalisierung und Integration von IT-Systemen im Land wurde aus einem kaputten System 2 Systeme, dann 3 Systeme, dann 4 Systeme. Dann kümmert man sich ne Stunde um nen Patienten und statt 10 Minuten auf nem Formular zu dokumentieren hat man dann 80 Minuten Dateneingabe vor sich. Und man gibt 4x die gleichen Daten ein. Komplett die gleichen Daten.

Und, wenn man das sorum strickt, dann versteh ich vollkommen warum Digitalisierung scheisse ist.

Ich frag mich aber auch, was man zu sich nehmen muss um das derartig hart zu versauen?

Wobei es da auch genug Stories gibt. Erfahrene Admins mit physikalischer Arbeitskomponente, die ehrenamtlich anbieten in einer Schule mal nen Wochenende Access Points an Decken zu schrauben und Strippen zu ziehen, aber das darf man nicht, weil da “gesicherte Netze” im Spiel sind und so. Krampf-Thema.

Inside, I like Abyss, similar to the OceanDeep theme of Vim.

When I’m on the balcony, it’s hard to see anything, so them I switch to Solarized Light.

I just enjoy the scene of the oldtimers strutting in like true chads and showing the youngsters how to take care of the big lady. It’s so wonderfully corny. And it’s such wonderful bullshit, and when you learn how many hands were necessary to run such a ship, it’s even more fun.

Well, you’re looking at a method, and imagine two things.

The first is a link to a confluence article. You click on it. Nothing loads. Ah, right. Activate the VPN. Click the link again. You have no access. So you send your IT a ticket to gain access. One week later you get a mail you have access know. For what? Who’d remember last week?

Alternatively, there’s an inline comment, or a markdown file in the same repo so you click on it and your IDE opens it. And then you modify the piece of code and you realize you still have that markdown file still open, so you adjust a few things and also note down a weird quirk you found during debugging.

However, in the first case… well, you finally had access to the documentation, so you want to modify it to bring it up to date. Well, guess what. You have read access. So back to another ticket with IT that you’re actually working on this and you’d like to update the documentation. After a week, you’re notified: Well they need approval of the documentation owner for you to get write access. They are on vacation. When they get back after 2 weeks, they approve the request, and it goes into a second round of approvai with your teamlead. And guess what? Right, he’s not in for the next 2 weeks. By the time you finally have write access, you’re not working in that department anymore. And no, that other department doesn’t use that confluence.

Overall, documentation tends to be somewhat of a chore for many people. If it’s close - it’s in the same repo, you can open the file in your IDE, you can commit updated documentation with your code in the same PR - there’s a slightly higher chance for folks to update documentation. If you put in the hellscape of a process some companies have for their tooling there, no one will ever touch the documentation.