The idea is that the string of lights has a male end and a female end. That way you can have several daisy chained and just plug the one with the male end into the outlet. But if you plan it wrong then you may end up with the wrong end in the wrong place, in which case yeah, use an extension cord or hang the lights all over again.

Oh and it’s actually relatively safe this way… Each string of lights normally has a fuse in it, so it prevents the cords from carrying more current than they are designed for.

Yep! That way you can daisy chain several in a row.

That makes about as much sense as saying that pip, gem, npm, cargo, or nix should called be the default package manager on Mac OS…

The default package manager is the default because it manages the system’s software. RPM, Deb/apt, pacman, etc. Homebrew is like pip or docker or cargo or snap or whatever else. You can set it up if you’d like but it’s certainly not a default. (Though I’m not trying to dispute that it’s good 😊)

Mac OS doesn’t have a good default package management solution (though they would if they just opened up the app store and added a CLI). It’s ok to admit it, and say that third party folks (who Apple does not support unless I’m missing something) are powering a pretty good third party experience. If only Apple cared about people who wanted a truly free an customizable computer, they could make a great OS :)

The closest analogy is specific tech skills, like say DBs, for a small firm its just something one backend dude knows decently, at a large firm there are several DBAs and they help teams tackle complex DB questions. Same with say Search, first Solr and nowadays Elastic.

Yeah I mean I guess we’re saying the same thing then :)

I don’t think prompt engineering could be somebody’s only job, just a skill they bring to the job, like the examples you give. In those cases, they’d still need to be a good DBA, or whatever the specific role is. They’re a DBA who knows prompt engineering, etc.

I have an air compressor which is powered by the 12V DC outlet in a car. They are quite cost effective and easy to buy. I use it all the time to refill my tires. Much better than some odd exhaust pressure solution.

I’m totally willing to accept “the world is changing and new skills are necessary” but at the same time, are a prompt engineer’s skills transferrable across subject domains?

It feels to me like “prompt engineering” skills are just skills to compliment the expertise you already have. Like the skill of Google searching. Or learning to use a word processor. These are skills necessary in the world today, but almost nobody’s job is exclusively to Google, or use a word processor. In reality, you need to get something done with your tool, and you need to know shit about the domain you’re applying that tool to. You can be an excellent prompt engineer, and I guess an LLM will allow you to BS really well, but subject matter experts will see through the BS.

I know I’m not really strongly disagreeing, but I’m just pushing back on the idea of prompt engineer as a job (without any other expertise).

Lol

What’s wrong with homebrew?

Crappy default package management.

This kills the clutch

It’s also a mechanism to sandbox applications, which static linking can’t do.

But it’s actually not that bad… It’s not good beer but whatever it is, it’s nice 🙂

Yeah, but they require somewhere in the neighborhood of a thousand pounds of batteries to do so. Some of the more egregious ones need multiple thousands, e.g. the electric hummer whose battery alone is heavier than an ICE Honda Civic. Whereas a dozen gallons of gasoline (roughly 72lbs at 6lb/gal) can power that same ICE Civic for a nearly equivalent range, while causing much less wear & tear on the roads, and likely releasing less tire particulates due to the reduced weight. Of course it still releases CO2 and other nasties…

But yeah, the energy density of EVs is still super bad. It’s just “good enough” that we’re making it work.

It can be both, and I’m not sure I see the distinction. It’s a coping mechanism, and that’s not actually an awful thing.

Growing up in church, nobody was creating hypotheticals and then trying to explain it using religion. It’s just not what it was about. But I guess if you brought up babies with cancer, then yeah the “mysterious ways” argument would have been a prime cop out to avoid challenging faith too much.

Most commonly, people just wanted to know how to handle the (typically less hyperbolic) challenges in their own lives. They believed they were good and faithful and didn’t understand why God would allow bad things to happen in their lives. Ultimately the “mysterious ways” line was just a coping mechanism, that came with advice to search for the silver linings, and think about past challenges and how they resolved, as evidence of the mysterious ways. Of course it also served to avoid challenging their faith too.

At the end of the day, religion has its very bad elements that I won’t defend. But it’s silly to ignore that for most people, they’re looking for ways to interpret life in order to find meaning, or maybe cope with struggles. For myself, I’m not religious, but if I were trying to help a friend dealing with something difficult in life, I would still encourage them to look for silver linings and to reflect on past challenges. Not to use it as evidence for some god working in mysterious ways, but just to give them perspective to realize that they have the strength to overcome challenges.

As I understand it, the big issue is energy density? A tank of gasoline takes you quite far compared to an equivalent tank of hydrogen.

And don’t get me wrong, lithium batteries are super bad at this too, but I do think that has been a limiting factor for H cars.

And then there’s the whole tire dust issue which is definitely a conversation worth having.

Usually it’s a bunch of different string hashes of the text content. They could be different hashing algorithms, but it’s more common to take a single hash algorithm and simply create a bunch of hash functions that operate on different parts of the data.

If it’s not text data, there’s a whole bunch of other hashing strategies but I only ever saw bloom filters used with text.

People aren’t misunderstanding the issue. Third party cookie support is being dropped by all browsers. Chrome is also dropping them, but replacing them with topics. Sure, topics is less invasive than third party cookies, but it is still more invasive than the obvious user friendly approach of not having an invasive tracker built into your browser. No other major browser vendor is considering supporting topics. So they’re doing an objectively user unfriendly thing here. This is the shit that happens when the world’s largest internet advertising company also controls the browser.

A classic use for them is spam filtering.

Suppose you have a set of spam detection systems/rules which are somewhat expensive to execute, eg a ML model or keyword blocklist. Spam tends to come in waves, and frequently it can be as simple as reposting the same message dozens of times.

Once your systems determine a piece of content is spam (or you manually flag content), it’s a good idea to insert the content into a bloom filter. This means that future posts of the identical content will be flagged without needing to execute the expensive checks, especially if there’s a surge of content stressing your systems.

Since it’s probabilistic, you can’t use this unless you have some sort of manual reviewing queue or system, as it’s possible for false positives to be flagged. However, you can also run more intensive checks once you’ve flagged content, to detect false positives.

The false positives can also be a feature, not a bug: with careful choice of hash functions, your bloom filter can actually detect slightly modified content, since most of the hashes may still be the same.

I’ve worked at companies which use this strategy so it’s very real world.

I once heard that argument in a different, yet equally rage inducing context: “outlawing same-sex marriage isn’t discrimination! Everybody has the right to marry someone of the other sex” 🙄🙄🙄

I’d argue that’s not true. That’s what the extern keyword is for. If you do #include , you don’t get the actual printf function defined by the preprocessor. You just get an extern declaration (though extern is optional for function signatures). The preprocessed source code that is fed to cc is still not complete, and cannot be used until it is linked to an object file that defines printf. So really, the unnamed “C preprocessor output language” can access functions or values from elsewhere.

I know this is a joke, but assuming you’re the author, then you’re under no obligation to follow the license. Only people to whom you transmitted the code are bound by its terms.