Some local plants might be edible and even delicious, but they are either way to costly to grow or harvest, or they are nigh impossible to preserve. Or they simply are edible, but not sustaining, like sucking nectar from stinging nettle blossoms.

Some are acquired tastes like e.g. turnip tops. You could probably harvest tons of them, but there is no real market for it.

Or take edible flowers, you basically can’t preserve them, and all you can do is put them on a dish for decoration.

Pearl Onions are a borderline case, for example. Between harvest and sitting in the pickling juice they only have a few hours (3-6, IIRC), or they are a case for the compost heap.

If they have one.

This could be vibe coding, or just an intern “doing the web site”.

Neither should have write access to production code.

I did not switch to Linux. I simply never did Windows. I use Linux since the old days of Slackware where you really had to compile ones kernel. That was with kernel 0.97.

Who would have thought that such a thing could happen? Apart from anyone knowing enough about computers, I mean?

If he mentions it, one has to assume that he knows enough about it to lie.

The ultimate red flag. They probably lie about paying you, too.

If push comes to shove, you can still use Notepad++ under Wine. It works.

I use Kate for my editing needs, fast and good regexp work, which is important for me.

I’m angry about all five castings. Same about the casting of an african-american as Heimdall in the MCU - What would be whiter than a nordic god? But using while actors for non-white roles is the vast majority of miscasts.

Yes, you are not wrong here.

What I regularly have to deal with is about as bad. Big project, and every upgrade replaces one key element. They have never heard of backwards compatibility. If they don’t like a subset in their system, they replace it. Complete with different API calls, structures, and calling conventions. And they may document parts of it three versions later. If at all. Some documentation is basic Doxygen - just list the function parameters, and that’s it. I’ve seen cases where the documentation of the rather critical parameter “flags” was just the word “flags”. I’ve seen cases where the return value was documented only as “status”. Not even with a notion whether 0==success and 0!=failure or vice versa.

And no, it is not a closed application. They have an “extension” folder for user-supplied extensions. The problem: If it is not a core extension that has been updated with the main project, the first thing after an upgrade is finding out where your formerly working extension critical to your project now fails, because they just happened to think that the call interface for the boogaloo object need a complete overhaul. Maybe it needed an overhaul, but then at least keep the older interface alive for at least a few versions after documenting the new interface and marking the old one as deprecated.

Yeah, the concept is nice, but it tells me that the Big Bang doesn’t explain what happened before it (the leading hypothesis is that the Big Bang started time, so there is no “before”)

Which is entirely correct. Time as we know it is an “inside” parameter of our universe, and therefor any causality only exists inside our universe, too. Because causality always contains a temporal element as in “Event A happened, which caused Event B later”. We cannot make any assumption of “before the big bang” and therefor no assumption of “what caused the big bang” either.

At least not in any way we could relate to.

the common myth about Daddy Longlegs being highly venomous

Quite a childrens tale, even back then. Two reasons for it: First, the “Daddy Longlegs” has no ability to bite us. Even extreme thin parts of the skin, e.g. the lips, are still way to thick for it to penetrate with its teeth. Second, even if it could inject its venom (which really exists!) it would need to inject about half a cup of it into a grown adult (IIRC about the amount, it could be a quarter cup or a whole cup or something, but still in the range of “thousands of total spider weights”).

Autism diagnosis rates. Quite a difference.

Looks like it.

No idea what exactly was used. This was done when they built the building, way before my time in the company.

I can tell you it does work. I’m working in a lab painted with such stuff. No, we are not doing anything nefarious, but we had developments stints into wireless and radio technology, and having a properly shielded room to work in helps avoiding trouble with the neighbors. I don’t think they would appreciate getting their wifi jammed when someone here is trying to find a bug in a sender or something like this…

Absolute easy here in Europe. Got two sets, installed them on the south wall (we have no balcony), and now we get up to 700W, usually 2-3kWh per day.

That’s what conservatives do. Everywhere. Ignore the problems, hen try to do a diversion.

but what you’re saying sounds boggers.

Believe me, it isn’t. I program about anything for forty+ years now. I probably have forgotten more programming languages than you can list, and if there are constants in programming, then a) while compilers get better at catching bugs, they never got over the basics, and b) a good programmer will alyways be better at preventing and catching bugs than a compiler.

Once you have aquired a good mindset about disciplined programming, those buglets a compiler (or even code review systems) can find usually don’t happen. Be wary of those bugs that evade the seasoned programmer, though…

For the mindset, it is good to read and understand things like the MISRA standard. Stuff like that prevents bugs.

The “common bugs” that the Rust compiler prevents are those a good programmer should not make in the first place. It’s the bugs that even evade a seasoned programmer that poses the problems, and there, Rust won’t help either.

Remember ADA? A programming language frankesteined by a committee to make programming safer? The programmers using it still produce bugs. And ADA is way more whips and chains than Rust.

With such a codebase, once it is settled to a certain point, you stop adding things. You write new things, and carefully interface with the old stuff.

Imagine a bank. Their software core is usually neolithic, i.e. written in COBOL or even worse, FORTRAN. You don’t add the “online banking” or “web client” interface in the original language. You add them in something more contemporary, which interfaces to the neolithic core via files, pipes, libraries, whatever, and translate it into a frontend as needed. As long as the core works, nobody needs to touch it.