I would like to add that Control-IQ still underperforms open source DIY artificial pancreas systems like Loop (https://github.com/LoopKit/Loop).
The guys that built Loop and the Riley Link (https://getrileylink.org/) (bluetooth to RF adapter relay to control wireless pumps that were reverse-engineered) are heroes.
I think that's where policy + manager discretion for overages is the better approach. Your manager should know if you and your team are killing it.
"Unlimited PTO" just sounds like make believe land.
And if it's not an actual, usable, guaranteed policy that doesn't negatively impact your career... then why are we deluding ourselves and creating a policy vs culture mismatch?
Years ago, when I was first married (like several months after getting married), my husband needed surgery. The surgeon thought it might be pancreatic cancer.
The board gave me all the time I needed, no questions. And, the day of the surgery, a colleague from work spent the day at the hospital with me. A free day from the board and director.
Now it's true that I worked every day husband was in the hospital - I mean, he was sleeping most of the time so why not work? But they knew I would work since that's what I did. I delivered for years.
I was incredibly grateful they allowed me to take the time. Am still grateful. But I was also in a position where I could take an unpaid leave or quit. Neither optimal, but family comes first.
Would the organization have done the same for other staff? I don't think so. I had been there the longest and busted my ass for them, loving the work every single day.
Coincidentally, I quit a consulting job that wouldn't give me (unpaid) time off to be with my mother through surgery for pancreatic cancer (positive outcome, so far).
Had saved enough that finances permitted, and I still feel great about the decision.
You can find a customized version of it on web.de / gmx.net / mail.com under the product name of "Online Office", once you login with a registered user.
One downside to this announcement is that this may become an excuse to stop open-sourcing features to Gitlab CE.
We (Debian) use Gitlab (salsa.debian.org) but we wouldn't switch to the free Gold/Ultimate version because we don't want our infrastructure to run on proprietary software.
It might be that the majority of free software projects accept to use the free subscription and therefore lower the pressure to add new features to Gitlab CE.
As implied in the OP we understand that some projects (like Debian) are not comfortable running proprietary software. We'll continue to listen to their wishes. And the increasing adoption of GitLab open source by open source projects might lead to more contributions to the open source code base.
I think that is is best to open pull requests to Gitlab instead.
You may object and say that it is a bit lame to re-implement something that is already in the paid version. However, it is best than re-implementing everything from scratch.
Also, I have heard that Gitlab is open to open-sourcing features when you show interest to have it in the free version.
The guys behind the Gitlab company move the community edition pretty fast too, possibly faster than what we would achieve by duplicating efforts.
However, as I mentioned in another comment (https://news.ycombinator.com/item?id=17241209), this may change because the new free Ultimate/Gold subscriptions could become excuses to stop open-sourcing features to Gitlab CE.
I don't see any requests to 1e100.net when loading Google sites like google.com or youtube.com. I see domains like gstatic.com and apis.google.com, but but not 1e100.net.
You can think of all user-facing domains in a system as an interface or API, which abstracts away implementation details about which specific servers are behind them.
This allows flexibility in infrastructure — you can swap machines in and out (e.g. by updating public DNS records, updating the machines’ IP addresses, or adding them to (or removing them from) a load balanced pool behind a reverse proxy). But you still need a way to reference individual machines regardless of whether they’re serving or not.
That’s where domains like 1e100.net come in — a system of concrete (non-abstract) references to specific machines in your infrastructure.
The guys that built Loop and the Riley Link (https://getrileylink.org/) (bluetooth to RF adapter relay to control wireless pumps that were reverse-engineered) are heroes.