https://www.oecd.org/en/publications/pisa-2022-results-volum...

https://icelandmonitor.mbl.is/news/news/2023/12/05/concernin...

Academic performance is somewhat of a burning fire - I'd guess there is less of a translation issue with the article than a cultural and political issue around the topic.

It seems MitID isn't mentioned in The Copenhagen Book: https://www.google.com/search?q=site%3Athecopenhagenbook.com...

Iceland and the Faroes follow the same one-for-all approach: https://www.audkenni.is/, https://www.samleikin.fo/.

Things are a bit more fragmented in Finland, Norway and Sweden: https://www.norden.org/en/info-norden/electronic-identificat..., https://www.norden.org/en/info-norden/electronic-identificat..., https://www.norden.org/en/info-norden/electronic-identificat...

So, it's maybe not too much of a stretch to say that "a Copenhagen way" to authenticate is to integrate with MitID, either through a certified broker or by becoming one: https://www.mitid.dk/en-gb/broker/broker-certification/

https://cphpost.dk/2016-08-26/news/more-rocks-being-thrown-f...

- The "hard" stuff (with numbers in it...) didn't really grab me at all, I originally studied math and was somewhat disappointed in much of that part of this kind of MBA program, my hunch is that a regular full-time MBA would have been better for this, more immersion, this was all a little in the one, out the other for me because there wasn't much time to practice.

- But, the "soft" stuff on the other hand, was a goldmine, all the personal development, organizational psychology, negotiations, etc. This alone was worth the tuition.

- The best part was gaining a far better understanding and tolerance of why and how pretty much everything we work with in software is more or less "broken", it's actually not broken, it's as good as allowed by budget and organizational circumstance, and if something is to be improved, well, then that background has to allow for that improvement or else the improvement is just a pipe dream.

And you meet interesting people who will do interesting things in the community where you live, assuming you stay put, which I didn't, so I can't say much about that.

The key to not having to deal with this problem anymore, for me, was starting to proactively switch things around to break the routine of consecutive work-weeks. One of my tricks was to do some kind of mini-vacation every 6-8 weeks, go somewhere new, leave work behind for 3-4 days. Even smaller things like regular social events can work wonders - anything that breaks the weekly routine.

Back when I'd get myself into burnout periods the most effective way to recover enthusiasm was to pick up a new skill, work-related or not. I was in my mid-30s in the late aughts and not entirely sure I wanted to keep coding - so I signed myself up for an 18 month "executive MBA" program to find out if I might want to do something else, and instead came out of that with a whole new outlook on how and why to write code.

Then around 5 years later I started writing code on the side, for myself, to gradually improve over the long term, and this can be absolutely therapeutic.

Try to switch things around a little bit, do something new, see if that helps?

I decided against the 34" because I could not really figure out how to make the wide screen work out for me:

- One of those is not enough screen to put the browsers and terminal windows on either side of the IDE

- Two screens always gives me a neckache because of turning from the screen in front to either left or right but not the other...

- Putting a 34" in the center of three screens moves the edges of the side screens really far out, which I think would be odd for my field of vision, force me to turn my neck too far, and cost unnecessary desk space - I have this problem already to some degree with the three smaller screens

- I don't really feel like I have time to hassle with unexpected problems that pop up because of using a non-standard resolution, I want mainstream and simple so I can focus on my stuff; I think this is relevant both to driving the display, eg. at the OS, graphics card, drivers level, and also at the application level because it is unlikely that any UI will be designed with the wide screen in mind

- I like to run full screen, so I don't have to futz with border dragging etc.

In the end, I decided that 34" is actually not enough - I'd want a screen like this in the 50-60" range, but pixels above eye level also cause neckache, so this would be a resolution of something like 10000x2160. I'd also want better window manager support for getting the right window placements without having to that myself every time. I saw a backlit projector-driven screen like that in a research lab 15 years ago - perhaps we can actually buy one in another 10-15 years?

I also did think that the 34" might be really great if I either spent all of time in a single full screen application without the side windows, or if I went back to coding in vim and arranged everything into a smaller area - which I don't want to do, but lots of folks prefer that.