I just have a smaller dataset using the same settings, which I try to recover a couple of times/year.
It’s not perfect as recovery exercises go … but it feels safe enough for me.
I just have a smaller dataset using the same settings, which I try to recover a couple of times/year.
It’s not perfect as recovery exercises go … but it feels safe enough for me.
I’ve used backblaze for years and regularly run recovery exercises. Never had a problem.
However, to avoid any fears, I store remote backups in two locations (the other one being OVH, a large French cloud provider).
My data retention regime:
Yeah, I agree that might work if the marketing team isn’t that connected to the product. I’ve not worked with a marketing team where that would work, but maybe it will for some. It doesn’t change the “massive customer will only renew if” scenario, though.
The challenge is, in a real org of some size, you’ll suddenly get marketing or customer success asking you for commitments that are very far out, because ad slots have to be booked or a very large customer renewal is coming up.
And some of the normal coping mechanism (beta-branch that spins off stable feature to the general release branch) don’t work for all those requests.
Try as you might, you are going to get far off deadlines that you have to work towards. Not for everything but for more than you’d like.
But what if I don’t have an MEP? (Cries in British)
I mean you did claim Sweden was being occupied. Words do matter, you know. It’s how we understand what you believe.
Dunno about affordable but you can usually find some decently priced 1L Dell Optiplex micro systems. I’ve got one running under my desk 24/7. Great Linux support.
Are you referring to the US? In the country I live insulin is available for free for those who need it.
How can I take this news and turn it into a class struggle?!
But it’s inheriting classics, breaking through!! What’s not to be excited about?!
<breathy> Bigme </breathy>
Well, different floats for different boats I suppose.
I do think Zig is better for this kind of thing.
const ret = try do_thing();
if( ret ) | result | {
do_something_with_result(result);
}
The try keyword returns any error up; the if-unwrap works with what came out of a successful call. Normally you wouldn’t have both, of course.
do_thing would be defined as a union of an error (a distinct kind of type, so it can be reasoned about with try, catch and unwrapping) and the wrapped return value.
I’ve already paid for a lifetime license of Plex. Is it worth considering a switch?
If you fund, you influence.
Scale. Look at a programming language like Zig … tiny, but managing to have three people full time.
It’s not very colourful :)
Yes I’m aware, of course. But then you take on another set of trade-offs. It’s not like shallow cloning SOLVES your problem.
Yes but Perforce is a (broadly) centralised system, so you don’t end up with the whole history on your local computer. Yes, that then has some challenges (local branches etc, which Perforce mitigates with Streams) and local development (which is mitigated in other ways).
For how most teams work, I’d choose Perforce any day. Git is specialised towards very large, often part time, hyper-distributed development (AKA Linux development), but the reality is that most teams do work with a main branch in a central location.
I know - it’s unreal how much people confuse Swiss banking privacy with Swiss privacy laws in general. FADP is weaker than GDPR IMHO.