ahnberg

I appreciate your comments and hugops! This is what the community should be about! <3

I totally love it!

I think the biggest issue is people who claim it can't be done and that the only way to accomplish this is to physically meet.

I feel like the biggest hinderance to making the most out of a remote option are the ones who prefer going to the office or explain all kinds of issues with "it's because we don't meet in person".

One just have to embrace and apply the mindset that it is possible. Different, surely, but still possible!

I'm not saying there is something WRONG with going to the office, it is lovely to hang out in person with lots of people, but it is very limiting in many ways as well. Just limiting in other ways than remote. You learn to deal with both, when you need to, though. The issue is mostly that people deal with the office-problems but don't care much about dealing with the remote-problems.

Sadly the fact that it HAS been written about for so long just fuels the fire (no pun intended) for the sceptics.

Something I often hear when trying to talk to people who refuse to believe the impact we have: "See these domsday prophets have been ranting about this for over a century and we're still here enjoying life!"

I'm one of the few persons I ever heard of that actually enjoyed being on-call. I believe it goes with my puzzle problem solving mentality to an extent. Being randomly challenged with a problem to look at where you might not know the solution, simply excites me.

Combining on-call duty with an approach of weeding out repeating issues, build better systems and ensuring that unnecessary calls don't happen is key of course, being woken up 25 times for silly predictable errors is pointless and draining.

And finally having an employer that doesn't expect you to be in at 8am if you've been up all night is also very important, catching up on sleep is necessary to manage your balance and health. But given this freedom, I totally dig it. :)

The issue isn't so much that one single separate service is priced in a certain way. When you add up dozens and dozens of services for various split needs for the business, and each one of them has a $/user/month thing and then to build decent security into it all, you double or triple that amount per service. It adds up, very quickly.

For the good of the Internet, the security of the global entirety of things, it is very very wise if everyone makes an attempt to make the defaults sane and secure, including things like this. It surely is a differentiator between "individual" and "business", but it shouldn't have to be. I agree wholehartedly with the sso.tax site that it's just one way for business to attempt to make revenue out of a basic need that any modern company would have.

Make the profit of real value added services for enterprises, automation, integrations, support, advanced features that gives insights or saves money or whatever; but don't be sneaky with the security aspect, is basically what I'm saying.

Compare it with streaming services. No one can argue against Netflix being particularly expensive. Anyone can afford it. It's just one latte per month. But when you not only want to consume what is on Netflix, you have to get another service, and another, and another, and another. Very very soon the aggregated cost starts to be very noticeable for a lot of people. And piracy makes a comeback.

No.

This is such a valuable recommendation. I've been doing the same since 20+ years back. On and off I've been bad at it, but I always end up coming back and continuing.

I think of it as more of a daily diary though, I mix random notes of things I've done, thought of doing, or interesting links and/or command-lines I've found useful so I don't have to reinvent them as often in the future.

It has proven to be immensely useful for myself. Can highly recommend!

My way is mainly org-mode files through Emacs over the years. Now having switched primarily to VScode I use a simplified org-mode version to get similar feeling, and it works pretty well. Everything is mostly text anyways!

Noteworthy security fix:

- On Windows, if a server sent control sequences at high speed to reconfigure the terminal window title repeatedly, PuTTY would pass on all those title changes to Windows itself at high enough speed to make the window system unresponsive, resulting in a denial of service to other local applications.

Noteworthy UI fix:

- The terminal was unable to display Unicode characters in the range U+F000 to U+F1FF (part of the private-use area).

This latest one is amazing for the ones of us who like to pimp our terminal using nerdfonts, fancy icons in the terminal and such. This now finally works well!