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.

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.

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.

• My self-hosted docker server is called Ark.
• My NAS is called NAS.
• The two remote servers are simply called the name of the country they reside in.
• The OPNsense router is called, wait for it, Router.
• The TV client is called TV.

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.

See this is the kind of shit that bothers me with Git and we just sort of accept it, because it’s THE STANDARD. And then we crank attach these shitty LFS solutions on the side because it don’t really work.

Give me Perforce, please.

Could be the VPN provider or the NAS (cpu)

Yeah I stumbled on this too. Surely the joke should be const mutable, not const volatile.

Thing is, I can express in Excel in 2 hours what takes two weeks to develop in production. And I’m not arguing against moving things onto a production footing. But hot damn, as a prototyping tool for how to treat data, Excel and Jupyter is near flawless.

In many countries the term “engineer” is a protected title.

Ninjas, super-heroes, black-belt and terms like that are known gender-excluders. I’ve been through a couple of adjustment sessions for company standard job descriptions and it’s unreal how you can change the applicant mix by wording.

Happy to see some alternatives, but I’m a very happy user of PhotoPrism (+PhotoSync) so will stay there for now. Agreed that encrypted at rest isn’t all that helpful for a self-hoster.

Oh right. The last three business I’ve worked in have all been fully public services; assume the intruder is already in the LAN, so don’t treat it like a barrier.

Funnily enough it’s exactly the opposite way of where the corporate world is going, where the LAN is no longer seen as a fortress and most services are available publically but behind 2FA.