That "wet dream" was only possible after several years of hard work of dozens of people, and only because many other small pieces fitted in their proper place.

Hi, manager! You said you want environments for your developers without needing my intervention in every step? Of course, here you have infra and config automation: this is how you can create (and backup! and restore!! and destroy!!!) DEV, TEST, QA, PRE and DEMO environments, all ready with your specific stack and versions and code and data. And this is how much will it cost to you, and this is how you define a budget limit in case something gets out of control. Everything is repeatable and 100% reproducible in seconds, so please do not hesitate to test and test and test. (And no, sorry, I won't let you touch PRO on your own, because that can cost a lot of money and we need to keep proper security).

So, you are asking me if we have heard about code versioning? Yes, of course! Here is a proper git structure, with predefined branches, segregated groups and permissions, and strict (and automated) revision requirements for every PR. I own the organization, you own the repo, QA owns the tests, and your developers own their branches and are self sufficient. Oh, and please remember we freeze the main branch 48h before the deployment, and time only begins counting after all the automated tests have passed and QA has given their final approval! No cheating!!

Oh, you have a picky customer who wants a guaranteed instant recovery in case THE WORST happens? Here you are, a highly available blue/green deployment, so you can deploy the new version without touching the old and only switch when everyone gives the final OK. And please remember to warn them it does cost DOUBLE the money!

Believe me, is not a wet dream, is just a lot of initial effort and A LOT of trust and confidence in the work of those around you.

And you have no idea how satisfying was begin work a Tuesday at 9AM sending a message "Hi, we are starting deployment in PRO" and then less than 5 minutes later reply saying "Hi, all is finished and checked OK from all parts, thanks to everyone and see you next week".

I worked for a loooong time in a medium size development company (about 200 developers, mostly doing large web portals). My team was some kind of central DevOps in charge of architectures, cloud, technology stacks... we were ALWAYS involved in EVERY deployment, and we were directly in full charge of the big ones.

After many years of constant work alongside the DEV/QA teams my team had gotten REALLY good doing deployments (we mostly sailed on each of them, since all was well tested, prepared and automated), and the project leaders simply trusted us. In the scarce occasions we said "sorry, this is not ready for prod" they knew it was true and didn't pressured us. And our customers were happy, since needing a rollback was EXTREMELY rare.

One of the most important things we managed to agreed with all the team leaders:

1. Fridays are read only.
2. No, that doesn't means we all can go home: Friday is now "Documentation Day".
3. Of course, if shit hits the fan, we are ALWAYS ready to deploy fixes.

I think in about 10 years I only had one call on a weekend.

"Space(d) Billionaires" would be a great sci-fi series to binge watch.

The article states "this operation involved chips made to convert analog signals to digital". So not GPUs, or even CPUs, but specialized ADC (Analog-to-digital converter) chips.

I love that "door open" warning of my fridge, and I also like that I get a notification when the fridge unexpectedly disconnects from the network (which usually means that the power has gone out, so I can go and check before all my food has died).

Also, the notifications when then laundry machine finishes are handy (so I can unload it and avoid smelly clothes).

Just yesterday it requested me to verify my account (with a full UAC dialog) before opening the clock app. I guess it was trying to sync (?) the custom alarms/timers (??) between my devices (???) but... WTF, Microsoft.

I have a micro-bakery (I run it completely alone) where I make everything from scratch, and every day I get customers who enter and immediately leave disappointed because I only have 6 or 7 different breads at most, when the big-name franchise store in the main street has literally dozens of varieties. Once one woman asked me why I wasn't baking fresh baguettes every hour like them. I don't know, lady... maybe because my baguettes take more than 3 hours just to do the first proofing, while they simply have to put industrial made ones in the oven?

Sad news! A mythical character from my youth, I have enjoyed so much reading his books. Without doubt, he has been an inspiration for a whole generation of security professionals.

Fuck cancer.

Thanks! Fixed

I use it quite often, but only recently began contributing. And as they (very) wisely say at the bottom of the wiki (https://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions ):

WARNING: OpenStreetMap is highly addictive Take frequent breaks, there is a lot to be done.

I am not sure what are the conditions/benefits provided by MetaARPA level, but my guess is that any NC access would be provided only to your specific SDF account, and with limited space/bandwidth.

And if you plan to offer family/friends with access... Well, I wouldn't want auntie Alice to see uncle's Bob backup folders and say "oh, I don't need any of this crap, I will delete it so @jdh knows how a nice user I am".

Save yourself some headaches and consider the basic plan from hetzner (https://www.hetzner.com/storage/storage-share), and just create a user (with quotas!) for each member that needs access. The service literally takes care of everything, and you only will need to remember to check that your apps are still properly enabled after they perform any updates or maintenance (and they will be perfectly fine 99% of the times, with the other 1% just requiring you to click on enable/update for some specific app).

Learn from there and then you can grow to bigger plans or, if you really feel the need to it, go full ahead hosting your own instance (maybe initially a cheap droplet in digital ocean, or a compute instance in scaleway, so you can learn the basics and break things). Next level? Pick a bigger instance or one of the real servers from hetzner's auction and go nuts. But always remember: auntie Alice won't be happy if your tinkering risks her collection of funny cat pictures. Always keep a backup of the backup (and test that it works!)

Always consider that just moving into nextcloud gives you much more control over your data than with any google/microsoft/somethingsomething service, since you can always just launch another nc instance anywhere else and move everything there. But at the end you ALWAYS must trust someone (your providers, your vendors... your users) and if you REALLY are paranoid about some unauthorized actor accessing your information, then self hosting in your own dedicated hardware is your only way, and that costs time and effort.

Regards!

Kepass (and Keepass2Android) + Nextcloud instances to keep sync and backups