That’s an interesting description of lemmy.ml

I’ll just say that hiding not only the instance, but also any comments from any user registered with that instance has made my Lemmy experience about 1000 times better.

Edit: oh shit I’m thinking lemmyGRAD.ml lol

Yeah I got a pretty nauseating explanation of “The June 4th Incident”

That’s not really responding to their point. Are you saying that there are no project resources that aren’t (or couldn’t be) encoded as text representation in any conceivable project that is stored in a git repo?

I agree with your general point. I’m just curious if you have some unique project pattern techniques that allow you to draw such a hard line so confidently.

If it depends on how ES6 is received they still have another 6 or 7 years

Somewhere in an ancient crypt, the bones of Luther begin to twitch to life…

I agree it’s not a blockchain, (although it has chain properties) but it is kinda decentralized. By convention projects almost exclusively have a single remote, and by convention that single remote is treated as an ultimate source-of-truth… But you can absolutely have the same repo with multiple remotes defined, and one could establish different schemes to determine which branches on which remotes represent what in terms of “truth”.

I’m not in a place to actually help as I’m on vacation: but since it’s a compile issue, if you posted a minimally failing-to-compilr version (no credentials) of your full YAML someone could conceivably be able to troubleshoot it

Can I vote for obsfuscators not holding a language hostage?

Where I am the charging infrastructure is terrible and electricity prices are bad. I was considering a hybrid but I guess if it’s no better I’ll just grab a regular ICE

I think pretty much everyone views their political ideology as “the one that stands for freedom”, and it just comes down to what it means to be “free”, and the follow up of free from what.

I feel like libertarians would love the concept of FOSS and decentralization, and I don’t think anyone would argue they skew left.

So, I disagree that FOSS is inherently left wing. I think it’s attractive to the left wing for many good reasons. I think people project their own politics onto whatever they love, and things can be loved by very different groups for different reasons.

Here, take this cigarette!

You don’t want a department that you throw it over the fence to, you want them embedded on your team. Keep those feedback loops TIGHT bois

Dan you sound like a rad dude ad I’d love to have a beer with you

Any thoughts on a set of APsystems DSL3-L inverters? That’s what I’m quoted for. I’m in Canada so no idea what the inverter market is here

This is amazing, because I do have HA running and I do want to pull data. I’ll look into what their plan is to see if I can make any last minute adjustments.

Assuming data is sent in the clear over any medium which I can get a receiver for I think I’d be ok, I am planning on getting a software defined radio on my HA in the near future

Yes, I’m looking at the paperwork and I’m realizing that you’re right, 80% at 25 is the warranty guarantee, so I’m guessing they’re confident it’ll typically be much better than 80 at 25

I’m getting some new panels installed this year, and I think they’re suggesting they’ll be at 80% after 25 years.

It looks like there is disagreement between the title and content of the article. Title says 75.9, content says 79.5

Either way, does this suggest that new panels might do better than expected over a 30 year timespan?

I mean, I’ve never seen a real platypus but I’m not going to use that as a justification for why they can’t exist.

I don’t know what to tell you. It’s a spectrum. I’ve worked in shops that claimed to be agile but to them, that just meant JIRA and story points. I’ve worked at places where agile meant having daily standups.

And I’ve worked places where there actually was a genuine attempt, and that was an awesome place to work.

I’ll rephrase them, except in good faith:

1. Talking directly to the people about the work is better than a 95 state JIRA pipeline

2. Document your finished working work, not every broken POC, because that’s a waste of time

3. If the contract isn’t actually going to meet the desires of your stakeholders, negotiate one that will

4. If you realize the plan sucks, make a better plan.

My company paid to have Kent Beck come to workshop with our Sr devs. I expected to dislike him, but he won me over pretty quick.

I don’t remember what it was, but someone was like “Kent, we do X like you recommend in the manifesto, but it creates Y, and Z problem for us”

And he was like “So, in your situation it isn’t providing value?”

Guy was like “No”

“Then stop doing it.”

It’s not hard. It’s the most fucking common sense shit. I feel bad for them because these guys came from a world where there were these process bibles that people were following. So they wrote like, basically a letter saying “if your Bible doesn’t serve you, don’t follow it”

And all these businesses dummies were like “oh look, a NEW bible we can mindlessly follow”

Ok, I think I see your position more clearly now:

You’re thinking about people who are interested and installing based on technical interest and curiosity.

In those cases, I think you’re probably right. There is probably some base competency at play. A desire to learn. Probably someone in their sphere to support.

I’m thinking more about the type of people who would buy a Chromebook. Or my cheap ass parents who want to squeeze another 5 years out of an ailing laptop. They don’t want to spend any money and just want to use Facebook and YouTube. Send some emails. Connect to wifi. Print their boarding passes. Not have their machines riddled with viruses within minutes because their windows OS isn’t getting security updates anymore. I think this is actually a massive use case, and I want Linux to be accessible to them without needing to use the terminal for anything.