sierisimo

Its the tolerance paradox: https://en.wikipedia.org/wiki/Paradox_of_tolerance

Not bare tribalism, just trying to keep everyone's freedom.

I own a voyager and you are correct, the switches are too close so I frequently press things by accident.

But is completely Firefox fault? Some companies just test compatibility and optimize with Chrome in mind, forgetting that sometimes some browsers (Firefox as well) dont respect some standards. Or even adding some features only available in some browsers.

Yes, is not as bad as it was in the 90s or 2000s, but is still a common issue

I think this defines it. It's an spectrum.

I made my jumps in the last 4 years...

I got really burned out while working in a MAANGA company and move to a smaller company but the poor management of the projects made me quit.

I then joined an startup and there was practically no automation and no consistency across the codebase so it was really messy and hard to follow, every new task required to re learn the module/code where you were working and the management was not interested on changing anything. Even I got called out for "not contributing enough to the product and focusing more on automating stuff"

I'm going to start soon again at a big corp MAANGA style, the interviews showed the engineers are more happy and challenged there and there's not a big rush/demand as in the previous MAANGA I worked on... So yeah, it's a matter of searching what works for you

(Yes, I haven't found what works for me, but I still have hope)

Can you elaborate on the painful edges and the benefits of frameworks avoided?

I wanna understand better as I do kotlin in daily basis, some with spring, some with ktor and some with android and I don't get your points.