donw

... when are large companies on the hook for anything, ever?

I mean, hypothetically, yes, but class-action lawsuits get settled out-of-court, the lawyers get paid in Ferrari-multiples, the plaintiffs get paid in McDonalds coupons that expire in two weeks.

Slaps-on-the-wrist are written into the laws; a million-dollar fine is existential for a small company, and likely not even a line-item at Anthropic.

I'm sure Omarchy will appreciate the effort, even if you're snubbed by Asahi -- being able to run Linux flawlessly on Apple Silicon is going to be awesome.

Ssssh, WeWork investors could be reading this thread!

What you want is a Garmin Instinct, or equivalent. Not sure if it does the pertinent-info bit -- mine has Bluetooth off almost all the time -- but it does the rest of what you want, and will run for over a month per charge.

It's funny how these articles always conveniently skip over the most important point: you first have to fill your city with Japanese people.

"It looks like you're trying to bypass authorized firmware. I'm sorry, but I won't help you."

We need to start teaching everything in Anglo-Saxon:

"Some of the higher samesteads are splitly. That is, when a neitherbit strikes the kernel of one, as for a showdeal ymirstuff-235, it bursts into lesser kernels and free neitherbits; the latter can then split more ymirstuff-235. When this happens, weight shifts into work. It is not much of the whole, but nevertheless it is awesome."

With me on the older side of things, believe it when I tell you that things actually used to, for the most part, Just Work.

"Simple mistakes" and "process breakdowns" were uncommon, notable, and dealt with quickly. Even the cheap stuff tended to last for quite some time, and was often repairable when it failed.

Enshittification is not only real, it is accelerating.

A substantial portion of software engineering -- and the fundamental jobs of a proper Product Owner and UX Designer -- is to turn "vague ideas about what we need to do" into "this widget, on this page, it should work like this"

It's not a pipeline, it's an ongoing conversation within any functional team, but this requires buy-in from management, who is often selected for "line must go up this quarter no matter the cost" over "hey, wouldn't it be cool if this company was still a going concern in twenty years?"

I'm really curious, what sort of work you were having it do such that you could execute multiple days of work with minimal supervision.

I also still don't understand why the author thought this was wrong?

Um... 話します is the correct conjugation for 話す, what am I missing here?

Honestly, that is just bad management. It can make sense if it's your company, but even then, the risk profile is just off the charts. What happens if your only developer leaves or gets sick?

Real engineers think about handling things when stuff goes wrong, not "everything will be on the happy path forever".

Yes, there are constraints, but to me this sounds like an unacceptable level of exposure.