Yeah, I get this a lot, especially from non-southern in-laws who think it's a hoot that they've "cracked the code" and can "speak southern". Being repeatedpy stereotyped to your face gets old pretty quick.

For folks who don't know, here's the best explanation I can offer from growing up in the Atlanta area (but well outside the perimeter):

"Bless your heart" is most commonly an expression of sympathy.

Sometimes, it's sympathetic towards the hardship someone's going through (e.g. "and right after his grandma passed, bless his heart.")

Sometimes it's sympathetic to the trouble someone went through (e.g. "oh bless your heart, you didn't have to go out of your way to bring extra! Thank you so much!")

And yes, sometimes it's an expression of sympathy for the fact that life must be hard for you because of your ignorance, stubbornness, stupidity, or arrogance (or some other such stunting quality) (e.g. "and he thinks he can graduate from Tech with those grades, bless his heart," or "bless his heart, I just don't think he's ever had anyone tell him no in his entire life.")

It's almost all by the kWh here, but perusing PlugShare I've seen a few level 2 chargers here and there that charge by the minute. Usually that's a sign of a charger that was set up a while ago and is owned by someone who hasn't checked on it since.

Interesting, perhaps the message was too narrowly, directly-focused and was missing necessary social context?

This feels like a koan about the subjectivity of which details are important to include.

>Also, that would imply a never-ending wack-a-mole game for me since people obviously keep doing this. I think I have better things to do in my life.

Uh-huh, and what makes that any different if someone else is doing it?

This feels like someone who discovered package managers for the first time.

I worked at Pardot around the time Salesforce started using this same language in internal announcements about Pardot.

Our Pardot leadership translated for us and provided the necessary context: Pardot is being killed. The plan was to start building the product that would replace it, stop selling new contracts, rename Pardot in the meantime so the change wouldn't be as noticeable, and in a timeline of "by 10 years from now" Pardot wouldn't exist anymore.

This is Salesforce for "last call for the lifeboats, we're gonna capsize the boat."

The text of the second amendment, as written, would seem to indicate that the premise of the second amendment is to arm "a well-regulated militia" (which was relevant to the government that adopted the second amendment, as it had no standing army).

It was basically crowdsourcing the military. We've been running through all the various problems with that idea ever since, including:

- oops, turns out not enough people volunteer and our whole army got nearly wiped out; maybe we need to pay people to be an army for a living (ca. 1791)

- oops, turns out allowing the public to arm themselves and be their own militia can lead people being their own separate militia factions against the government, I guess we don't want that (e.g. Shay's Rebellion, John Brown and various slave rebellions fighting for freedom)

- oops, turns out part of the army can just decide they're a whole new country's army now, guess we don't want that (the civil war)

- oops, turns out actually everyone having guns means any given individual can just shoot whomever they like (like in hundreds of school shootings and mass shootings)

- oops, turns out we gotta give our police force even bigger guns and tanks and stuff so they won't be scared of random normal people on the street having guns (and look where that's gotten us)

Honestly, the whole thing should've been heavily amended to something more sane back in 1791 when the Legion of the United States (the first standing army) was formed, as they were already punting on the mistaken notion that "a well-regulated militia" was the answer instead of "a professional standing army".

I've had quite a few folks in my semi-rural north Georgia deep-red county (where our congressional rep wins landslide elections while literally saying Trump is like Jesus) who are convinced by my F150 Lightning.

It's not a hard sell: no more oil changes, no more annual emissions-testing bill, no transmission to ever worry about, and a massive chunk of storage under the hood where the gas engine would be – plus a bunch of outlets all over for powering or charging tools. When I then tell them that I spend about $30/month on charging the thing (at home) compared to my former gas budget of ~$150-200/month, it becomes even more of a no-brainer.

And none of this has anything to do with climate change. It's just plain and simple practicality.

They tend to ask about range. I get around 300 miles on a full charge when road-tripping, and Buc-ees has some pretty cheap chargers (still cheaper than gas would be) that get me back on the road in about the time it takes me to use the bathroom, grab and eat some brisket, and change the baby's diaper. I've done some shortish road-trips a few times now, and not had any problems. I've got some longer ones planned this year, now that I know that I can find chargers along the way.

I looked into PHEVs on my last vehicle shopping go-round, since few pure EVs met my cargo size requirements (stroller/baby life is a whole thing).

Ultimately, it was way more worth it to go all the way up to an F150 Lightning than to go with a good PHEV, partly due to up-front cost, but mostly due to ongoing cost: I will need to change the oil on the electric motors maybe every 150,000miles, and I never need an emissions test again. PHEVs require keeping the gas engine up, and getting it emissions-tested.

A whole category of cost just straight-up disappeared, for cheaper than I could get a RAV4 Prime too.

The cost to maintain and inspect a PHEV engine in most vehicles is so minuscule as to be a rounding error. Engine oils last a long time these days.

When you've got kids, there's no such thing as "rounding errors" in terms of time costs.

It's an entire chore I never have to do. That time savings is significant when I'm already underwater all the time.

Oof. That's pretty gross: just throw away all typesafety?

A `Result<T, E>` return type is way better.

This feels like it'll be viewed like Java's `Date` class: a mistake to be avoided.

The Bible is too well-known a text that is too represented in training datasets for this _not_ to be skewed towards poorly reproducing existing translations.

Beyond that,

>there are hallucinations and issues

seems like a deal-killer for a religious text. Yes, all translation by humans is an act of interpretation on some level, and so there's lossiness in all translation – but the difference between a human carefully weighing their reasoning for a particular choice of rendering vs. an LLM that is basically weighted dice that might land totally wrong is a categorically-different thing, not a question of degrees.

This is definitely one area where the training set for the LLM is liable to be polluted by existing translations and even straight memorized english biblical text.

Not to be too much of a devil's advocate (ha!), but I kindof think I _want_ it to have biblical translation data in the dataset. So long as it's not simply copying something like the KJV or ESV into the output, then this should be a good thing, right?

Because much of what it produces (especially in the "poetic" mode) does seem to be very much "off the beaten path" for a good number of renditions.

I don't think that the goal would be to have a dataset that is completely free from scholarship on the topic of Biblical translation, but rather to synthesize the rules and principles from the collected body of knowledge and apply it (with steering) to the entire Biblical text.

Thoughtful critique.

No one is suggesting you replace your ESV or NKJV with this for your religious study. This is as much a technical project of interest as it is a faith-based one.

In terms of your view of the priors on the Bible, you've described in my experience the process all translations go through. We're all skewed by default toward reproducing (poorly) previous translation through word choice modification.

That is, in many ways, the whole thing. My guess is an iterative approach can actually yield a better approach as words shift meaning socially over time.

But we will see!