herr_gurke

Calisthenics is the way to go. You can start without any equipment and you can do it indoors and outdoors. There are plenty of calisthenics tutorials on youtube. Apart from that I suggest making a 20-30 minutes walk around lunch break

They implemented it before it was mandated by EU. IANAL but they didint have to implement it, since switzerland is not in EU

Time to set up is comparable, or even better for linux. The issue starts on the longer run, the moment when after one update hibernation stops working or bluetooth has issues and needs to be restarted with rfkill. I fully understand that its not fully linux fault - those are proprietary drivers and so on, but from the user perspective I would love to have a system that just works.

It's difficult for any of us to really tell how much truth is in every statement. For example readability - its difficult to asses it without looking at your code.

It's nothing personal, but many developers tend to think about their skills higher than they are in reality.

What i can suggest you, is to ask for feedback after interviews. You will get more specifics there

EDIT: I forgot to actually add a verb in the first sentence and some punctation

Im not sure if really the simplest test would catch it. You would need to go over n primes and check them, but you might always finish too early.

There is also a question of impact - i think that 19 does not really cause any harm there.

You can also get really creative with frameworks, specially if you need to quickly overcome some strange limitations imposed by framework. There is also a long term risk with using frameworks - somebody here mentioned method renames in Laravel, that makes upgrading difficult.

Im not talking about writing your own http server, or building the whole database access library. You can use some ready made libraries. As long as you keep proper boundaries between IO and business logic, you can fairly easy change the IO libraries.

Of course there is quite some overhead there, and for some projects it makes not sense.

I did some Django but in the days, and I completely agree that as long as you have CRUD, Django shines. The issue starts when you cannot really fit your uses cases into simple CRUD and you start to fight against the framework to achieve this.

The author also made a point of negligible gains - even if you spend a week to setup auth, sessions etc. if still negligible for longer running projects

The issue starts if you start with Django, but later on you discover that there it does not support your use case anymore.