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

yes get some olympic rings. look into the (free) app You are your own gym(Yayog) Buy overcoming gravity (or join the reddit group where the author answers many of the questions). Working out with bodyweight is fantastic imo

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

But Galaxus is also active/targeting Germany/Austria so they would have to implement it

Germany and Asutria are a different instance of the shop with different stock. There are several differences between these shops. That wouldn't be the issue

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.

> the moment when after one update hibernation stops working or bluetooth has issues and needs to be restarted with rfkill

I'll hype Fedora Silverblue/Kinoite once again for solving that.

Don't like the new update? Messed up /etc in any way? Tried a questionable third-party RPM and what a surprise, it doesn't do what you wanted? Roll back in a single command, even from the boot screen.

If 'ostree admin' was usable from the GUI [0], showing a screenshot of it would blow the mind of people using other operating systems.

The downside is that upgrading RPMs now requires a reboot, but your apps are going to be Flatpaks (or AppImages, or Podman services) so they don't have that limitation.

[0] Which will hopefully arrive soon to KDE: https://invent.kde.org/plasma/discover/-/merge_requests/166

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

Maybe better to do mock interviews if you can? Lots of places won't give any feedback on no-hires for legal liability reasons.

Don't take seriously any feedback you get from an interview. Unless you already trust someone involved in the process.

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 would need to go over n primes and check them, but you might always finish too early.

I mean sure, but it's pretty simple to at least enumerate the primes < 100 and test those...

Whats the problem with letting it run for a weeks on 5$ vps

You better have your crypto _primitives_ rock solid

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

I've worked on to many long dead projects with scant doco and the best ones are always where people colored inside the lines. Remember google web toolkit? That flamed out hard 15? years ago.

I've recently had to make a mod to a decaying app written in GWT. It was easy because no one got creative. I think theres a long term risk with rolling you're own that you box yourself into a lot of corners without knowing it.

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.

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

It’s impossible to predict the future. I would rather start with rails and rewrite portions later on, than start with Sinatra and shoddily reimplement rails features.

I also just think Django is terrible compared to rails, and that may be why the author has such a dim view of frameworks in general.

It’s worth noting huge companies started with frameworks initially. Just looking at rails: Twitter, Shopify, Airbnb, Basecamp, ..