ctrlaltdev

I do prefer mechanical - but I have an hybrid one (that reduce the sound) and have smaller key height. I feel i kinda have best of both world.

KeePass is an excellent solution. You can even store the kdbx file on a remote server and access it on different devices.

I've run into back-end developers completely helpless when asked to do anything front-end - and even those mingling with it usually do not know the struggles of cross-browser compatibility and accessibility.

So no, being fullstack (that is being mediocre on many things, and excellent in none), I do not consider front-end to be less serious.

I think that opinion takes roots in the apparent simplicity of good ol' HTML vs the requirements of a complex algorithm riddled back-end.

Especially with the rise of complex front-end frameworks, that difference in 'seriousness' tends to fade away in my opinion.

And for the sake of the argument, there's a deeper complexity to satisfying users and clients with front-end (and the fact that everyone's a critic) that back-end folks do not encounter.

In a previous position, our slack was organized by project channels.

In another position, it was organized by teams and sub-teams when relevant.

But in both cases, knowledge was stored somewhere else - like a wiki, or knowledge base. Slack was always used for immediate concerns.

I guess that paper is still relevant then D: : https://panopticlick.eff.org/static/browser-uniqueness.pdf

Some adblockers also blocks tracking scripts from social media sites

I feel that the goal behind #deletefacebook is not only to 'hurt' FB, but for the user to benefit from the deletion as well.

I don't see that much benefit in getting badly targeted ads for the user.

I tend to continue to think educating the user is the only long-term way.