skysight-inc/HackerNews huggingface dataset:
There was a business person in charge of keeping up with any regulatory changes. The regulations at the time were pretty stable, and I can’t think of a single change order that came from it.

The most important things to consider (IIRC) were ensuring that the data was encrypted at rest and in flight, and that access to the data was audit logged and properly authorized.

We had an audit every so often. None of this was hard. Just tedious. It does help to have a HIPPA expert advise.

I don’t think public cloud vs self hosting makes a massive difference. Of all the problems such a project faces, that is not close to the top one.

Keeping machines patched and up to date is also not terribly hard.

Anyway, I’m not saying you’re totally wrong. Our project may have had more hidden risk than I realize. But it’s my opinion based on that experience.
Because a robot that do everyone's laundry is much more closer to AGI than ChatGPT. I'm dead serious.
I've had other HPs (28C, 48SX, 48GX, 33S, 35S, 49G, 50G, Prime) but the 15C is the one I keep returning to, as anything more powerful really should be handled on a computer CAS like Mathics or Matlab-like environment like Octave instead.
It is a requirement to offer lunch in public schools in the US. Very few states are free. Some kids qualify for "reduced" cost depending on the district and their parent's income. The variance in the quality can be huge depending on the district.

I was in school in the 2000s. My school's food was almost always more like fast food than actual meals. Fruits and vegetables were not a big component, or weren't available at all, and the food never seemed "fresh". A lot of kids were kind of embarrassed to be seen eating the food. I know some kids that often skipped meals to just eat candy or went to cheaper vending machine fare.
Peter Thiel [video]
> It's a terrible deal no one asked the users if they want to agree to.

Every single user of Facebook was asked and agreed to it. [0]

This was not unexpected. Anyone who read the ToS of most large tech companies in the past 10 years, and gave it more than a few seconds thought, would have realized that they were giving them access to use the data however they want - a fact many of us have been warning people about for many years.

LLMs have also been an expected evolution of technology for many years. Nobody should have been surprised about this.

[0] https://www.facebook.com/terms.php
What is it with some people these days telling black people who and what they are?

What's a "Cousin Pookie"? This sounds similar to someone who recently said a presidential candidate would make the White House smell like curry.
I can't help but feel like the author has taken some fairly specific experiences with microservice architecture and drawn a set of conclusions that still results in microservices, but in a monorepo. There's nothing about microservices that suggests you have to go to the trouble of setting up K8s, service meshes, individual databases per service, RPC frameworks, and so on. It's all cargo culting and all this...infra... simply lines the pockets of your cloud provider of choice.

The end result in the context of a monolith reads more like domain driven design with a service-oriented approach and for most people working in a monolithic service, the amount of abstraction you have to layer in to make that make sense is liable to cause more trouble than it's worth. For a small, pizza-sized team it's probably going to be overkill where more time is spent managing the abstraction instead of shipping functionality that is easy to remove.

If you're going to pull in something like Bazel or even an epic Makefile, and the end result is that you are publishing multiple build artifacts as part of your deploy, it's not really a monolith any more, it's just a monorepo. Nothing wrong with that either; certainly a lot easier to work with compared to bouncing around multiple separate repos.

Fundamentally I think that you're just choosing if you want a wide codebase or a deep one. If somehow you end up with both at the same time then you end up with experiences similar to OP.
Yes 100%.

I'll expand by saying I think there's two types of documentation: references and guides. cppreference is a really, really good reference. It's complete, highly specific, and well formatted.

But it's an awful guide. If I was trying to learn C++ or it's standard lib, I would want to kill myself.

The problem is these two types of documentation are almost perfectly perpendicular in my mind. Meaning, a good guide is a poor reference, and a good reference is a poor guide.

Hand-holding step by step instructions, popular with many js frameworks now, are great guides. But when I want to know what function X returns and under what circumstances, I don't want to prune through a guide that starts at the beginning of the universe. And often those guides will be missing huge amounts of detail to lower the complexity.

So you need one kind of documentation when you start, and then another 5 years later.
I imagine if one of these goes up on (or under) a bridge, it'll compromise the bridge if it can't be extinguished. This happened some years ago with a (diesel) semi in Oakland, I recall, and it sounds like these burn much hotter.
> a ton of water

a rare case when "ton" is an understatement. 50,000 gallons is almost 200 tons.
> One of the few domains where this is testable has also demonstrated this. Writing is about as hard to break into as anything, yet Stephen King demonstrated success writing under a completely unknown alias.

I don't think it actually demonstrates this. As your wording hints, the hard part of writing is getting yourself out of the slush pile and into an editor and publisher's hands, and Stephen King's actions relied on his existing relationship with said editor and publisher to publish under a different name. He never demonstrated pulling the feat of escaping the slush pile again.

In modern content creation, the similar metric is getting to, say, 1k views, or even as prosaically simple as being part of the 50% of streamers to get 1 view. It's not sufficient to have talent to get to even that level of success; there is a lot of luck necessary to get you there.
I should have read this thread, it would have saved me the couple of minutes to get the exact same link you just did!

I named my lawnmower Larry.
Most "Fire trucks" - I'm assuming you mean Engines - carry 500-1000 gallons, usually more on the 500 size. A "Water Tender" generally around 2000 gallons.
If it's part of some protocol then it's definitely needed.

Safety measures are put in place for a reason.
I asked him for my full archive download in October 2022, and having heard nothing back I wound up paying him another $39 to keep my archive from being deleted while I tried to get his attention.

I didn't get any response until late February 2023, when he sent me a link that produced a 404 error. I complained about that, and about a week later, I got an email from him that asked me whether I'd been able to download that archive he'd sent me the link for "in late January".

I told him, again, that the link he'd sent in February hadn't worked, and that I'd told him that, and in a couple of hours everything was wrapped up satisfactorily.

Had he been able to do that when I'd asked for it five months earlier, I would undoubtedly have a much higher opinion of the man.
https://github.com/kristiandupont/react-geiger

This plays a click when React components rerender, to make you aware of the page performance
THIS.

A big battery "fire" is not really a fire, in the normal meaning of that word.

The job the FD faced might better be described as "supply continuous cooling, until the self-powered/no-oxygen-needed battery meltdown runs low on electrical energy". Though if the FD's training & equipment is for traditional fires - then they are stuck using a "pretend it's a fire, and call in 10 more tanker trucks" playbook.
Precautions can be needed, like input validation on a web form.
Raindrop is fantastic: https://raindrop.io/.
Obligatory mention of https://raindrop.io/

I switched from Pinboard a year or more ago after using it for many years, mainly because I found the iPhone app and integration (eg share feature, to save bookmarks) to be flaky.

Raindrop has been great - imported seamlessly from Pinboard and the iPhone and Desktop app work well for me.
> and environmentally unfriendly

That's international flight in general.
there are plenty of good alternatives nowadays:

- https://raindrop.io/: Also a one-man show, but probably the best bookmarking tool out there.

- https://omnivore.app: Open source and support for newsletters.

For my use case though (I like to curate and share), I ended up building an app (https://fika.bar) to bundle bookmarking + RSS Reader + Blogging.
Great article. Oru view of history is all to common insular and compressed - it puts things in context that MLK was walking around Berlin at the same time as Hitler.
The historical timeline for the siege is unreliable, but somehow the number of soldiers is rock-solid accurate? And, further, it is known that they were able to complete their siege works unharried? This paper at best provides a best-case estimate. At worst, it's trying very hard to find evidence to support a fashionable belief that the siege was short.
I was a previous Pinboard customer. I've since moved to Linkding[0], a self-hosted solution, and highly recommend it. It's got the same feature parity as Pinboard but gives me much more confidence about the longevity of my bookmarks.

0. https://github.com/sissbruecker/linkding
One trick you could use is to abuse the fact that law enforcement often plugs in a mouse wiggler on an unlocked desktop and kill your server the moment you see a new HID device (make sure to run some kind of desktop on your server so they think they can keep the session open, best to do it in a VM).

You could also monitor the ethernet link. They can move your server but they can't move the entire network, set up an encrypted tunnel between two distant physical servers and self destruct the moment that tunnel gets disrupted.

Some computers come with gyros/accelerometers built in. My old HP laptop had some kind of head crash prevention that used that hardware. I know this, because Gnome thought it was a tablet style sensor and turned my screen upside down if I didn't disable the sensor. Maybe getting a HP server can already get you a whole bunch of movement sensors.

You could probably figure out if the server is being moved by measuring capacitance of the case, measuring accelerometers, maybe add a GPS dongle. Or you could add an LTE connector and measure any signals you may receive that you shouldn't from inside a server room. You can probably measure _something_ in the server room, though, so to make sure your LTE dongle doesn't get interrupted, also measure whatever reliable signal you can find to detect Faraday cages.

Lastly, you could put a video camera in the case on all sides and measure changes. Detecting law enforcement badges probably isn't that hard with opencv if you're dedicated enough.

You have to hide your security measures and never tell anyone, though, or they'll just leave the server as-is and use the classic rubber hose exploit to make you give up the key material.
What’s the environmental damage, as in fumes or air pollution and/or this water seeping into ground, from an EV battery fire?

Has it been studied or researched?
I worked in smaller companies and now I work at Google. I enjoyed working for smaller companies so much more. I would never make a change from a small company to Google for the same pay. I think you will be shocked by how political and non-meritocratic Google is. Living abroad is also far from being all roses.
> the only difference that you don't use RPCs

But it's a huge difference. No RPC overhead. No lost / duplicate PRC messages. All logs can literally go to the same file (via e.g. simple syslog).

Local deployment is dead simple, and you can't forget to start any service. Prod deployment never needs to handle a mix of versions among deployed services.

Beside that, the build step is much simpler. Common libraries' versions can never diverge, because there's one copy per the whole binary (can be a disadvantage sometimes, too). You can attach a debugger and follow the entire chain, even if it crosses the boundaries of the modules.

With that, you can make self-contained modules as small is it makes logical sense. You can pretty cheaply move pieces of functionality from one module to another, if it makes better sense. It's trivially easy to factor out common parts into another self-contained module.

Still you have all the advantages of fast incremental / partial builds, contained dependencies, and some of the advantages of isolated / parallel testing. But most importantly, it preserves your sanity by limiting the scope of most changes to a single module.
The solution will be to move to a safer energy storage system.

Solid state batteries as supposedly safer.
Very!

https://en.wikipedia.org/wiki/Le_Roy_Engloys
Navigation is quite good (at least in Visual Studio C#). You can see usages and go up and down the class hierarchy quite easily.

Exploration, though, not so much. But you have is "object." and then read the methods and properties. It's not awful, but if you don't know the object first you can't do it.
Lithium fires obviously need some form of chemical dousing.

Pouring tons of water is just not a good way to put out the fire.
Basically, antibiotics are causal for leaky gut in mice.

Pretty compelling findings and the ramifications are huge!
yes but its hard to argue that if you've verified that you own say... somecompany.com that you shouldn't have control over the crates.io org for the same name.
As a firefighter/paramedic, pray tell, how would you suggest we "just get more efficient"? Part of the challenge is access, between heat and explosive risk.

It's not about being more efficient - it's about kicking out one or more legs of the fire triangle, with water, that being heat and oxygen. The problem is that physics dictates that overcoming the BTUs being put out by a battery fire requires rather a lot of water.

Use of other liquids to absorb this heat is ... problematic. One, you have to transport it to the fire, and two, runoff. It's bad enough having structure fire water runoff going to the ground and water supply, let alone another (most likely noxious) chemical.
> until [..] runs low on electrical energy

How long will it take for that to happen in one of these semis? What if the fire needs to be extinguished before then because of risks it poses to surroundings?
I think listing off a set of pros and cons for interns and LLMs misses the point, they seem like categorically different kinds of intelligence.
Pretty often at work. I'm often interacting with client/vendor teams or even new people at the company I work for. Probably a few times a week I'll get an invite from someone I have never exchanged an actual email with. Maybe Teams/other chat messages, maybe exchanged information with one of their colleagues, or talked over the phone.
CrowdStrike ex-employees: 'Quality control was not part of our process'
> If you aren't aware, there is an entire universe out there of people working solely on managing dependencies so that you, a developer or user, can "just" install software into your computer and have it magically work. It is fucking hard and complicated and necessary. If you've never done packaging for a distro or a language (and I mean 250+ hours of it), you won't understand how much work it is or how it will affect your own projects.

When new employees joined the engineering org at a former employer, they were required to spend six months on the sustaining team, where they could be assigned customer-escalated bugs in any part of the codebase. Under the clock to deliver a hotfix for production customers, they would be required to learn a new area of the complex codebase, work with specialists in that area, develop/test a fix and shepherd it through review/approval by senior engineers. Those who survived this process could apply to the subsystem team of their choice.

There is much for developers to learn from a period of apprenticeship in cross-platform software packaging. Start with .deb/.rpm, then image customization, A/B upgrades, stateless systems and work up to reproducible builds with Yocto, NixOS, Guix. In the next few years, SBOMs (software "bill of materials" aka package provenance) will become mandatory in some regional and vertical markets. This will either cause a reduction in dependencies, or increased attention to software supply chain relationships that bring regulatory costs.
The longer you wait the harder the pain. The less you wait the more frequent the pain. So it depends on the function that converts intensity and frequency to suffering :p But, most importantly, the fact that LTS gives you a choice is what I was highlighting.

For the scope I operate, which is pretty standard Linux packages (PostgreSQL, MariaDB, Nginx, Docker, OpenVPN, OpenSSH) the changes between 16.04 and 22.04 have been quite OK to deal with.
Thank you, really glad to hear that!
The 20 series Nvidia GPUs with RTX were a good example. RT cores were added and took up significant die space, people said "why not more CUDA cores"

Or they could have had the same number of CUDA cores without RT at a lower price (the fabled "1180")...
I worked in the pizza business before there are some regular customers that you pretty much would call friends. similar to work friends.
> What's the academic term for "mic drop"?

I've always gone for "QED" but I'm sure there are better options out there :)
> You burn roughly as many calories walking as you do sleeping.

> Sleeping burns 40-80 calories per hour, walking 200-350.

We must have different definitions of "roughly", that's an order of magnitude difference!

> You're not gonna burn off any calories by walking.

That's a very different claim (but still not true).

To be clear: walking is great exercise. No, you're not going to walk off a 10,000 calorie/day diet with it; you need to not eat that much. Nor are you going to look like you spend 3 hrs/day doing crossfit just by walking. But 10,000 steps per day is miles better than 500.
His voting control is ~70%, it's his capital holdings that's around the ~50%+ mark.

The website you shared is most confusing. Please use some other website, its UI is frankly terrible.
What have you been using for search? The CLI app? What is your download workflow like? Is there an automated way to download a bunch of links, say pulled in from an API?
Often, a coordinator sends the invite - not the recruiter.
This is a fun article but seriously lacking in details... musical frequencies crashing hard drives, including hard drives of laptops within earshot? That's a pretty extraordinary bug so I hoped there would be more elaboration. I also wonder if that patch to block those frequencies is still in effect.
It's also worth keeping in mind that rural fire departments that all have tanker trucks typically carry only 1,500-3,000 gallons and need to continuously fill up from a pump site, drive to the scene, dump in a pond, and continue. Typical gasoline car fires will take less than 1,000 to extinguish. EVs are challenging from this perspective, and departments are just now starting to learn how to deal with them, it's a whole new ballgame.

Source: Firefighter in a rural dept
I'm currently supporting two creators on Patreon and I'll likely up my donation to them by 3 USD each.

I'd rather be supporting the creator's co-op I thought I was, but I'll have to settle for this until that exists.
> I have a friend who is a successful OF model and only a fraction of one percent of her subscribers ever DM her.

I have a friend who produces a few successful OF models and makes about 5-10x a good SF tech salary. He has a whole army of sexters who impersonate models and DM with fans. Vast majority of his income comes not from subscriptions, but from content sold in these DMs, content which is presented as "exclusive" to the buyer.
A rebuttal to that piece:

https://www.lesswrong.com/posts/7iAABhWpcGeP5e6SB/it-s-proba...

Their thesis doesn't hinge entirely on lithium, but their sloppy work and responses to the rebuttal mean people should take their work with a huge grain of salt.
Because I am tired of living in what Cory Doctorow calls a "demon haunted world".

https://locusmag.com/2017/09/cory-doctorow-demon-haunted-wor...
Eh, if you have to pay 15k to get a no-op settlement that doesn't sound like a win.

Maybe a draw but being down 15k still sounds like a loss. The other side also lost but that doesn't make you a winner.
People who have that much of an issue with sobriety have other demons they need to address in therapy.
In the United States? That discounts how resistive to change and fragmented the various municipalities that own all the roadways are. The various states can't even mandate a shared speed limit, they are not going to all agree to (and pay for) retrofitting all of their traffic lights to a single standard.
I think this take on history is a bit rough. Free markets are a fiction. Their ideal picture can only exist in a capitalist sense due to the force monopoly of the state. Otherwise, what is stopping me to shoot you to get your means of production?
And is that really a free market, given that I skipped the laws of supply an demand by taking your life?
So some governance is needed to keep things kind of orderly. Now the question becomes how much, but that is a political question.

As for your second point:
One could indeed argue in turn that they were. In both countries WW2 was preceeded by extremely harsh economic conditions for most of the population, while industrialists prospered, leading to extremist voting shares previously unheard of.
Big Industry in turn directly sponsored the NSDAP in many ways, big and small, to get them into power. Hitler especially preached terror to the masses and met with Krupp, Bormann et al. in the backrooms to talk policy.
So the previous comment had a point, yours not so much I am afraid.
one particular item of interest: https://en.wikipedia.org/wiki/Adolf_Hitler_Fund_of_German_Tr...
Doesn't fires involve lot more than just batteries and fuel? At least with many of trucks, there is the cargo and the cargo compartment. Not a big deal with something like gravel or sand... But parcels, food, so on? Traditionally you deal with fuel and that cargo at same time and it is usually done when done, but what are probabilities with battery fires that you reignite whatever is left?
> it can't answer the unmisleading version.

Yes it can: https://chatgpt.com/share/66e3601f-4bec-8009-ac0c-57bfa4f059...
I'm amending this because I've found that MM is commonly used in finance, so it's not like the author chose to go rogue.

Also

> It's so easy to stick to international units, folks. Please. PLEASE!

should be to stick to the language's usage of units. Not necessarily international units.

Even though the comment doesn't exactly apply now that I know MM can be used in finance, but I wanted to correct it to have a broader coverage.
If you haven't seen a Tesla burn uncontrollably, emitting clouds of very poisonous smoke, search for video and watch it.

Same thing happens to e-bike batteries; you can find video of a man being spontaneously incinerated after carrying his e-bike battery into an elevator.

And of course the same thing happens to battery storage for the grid. Battery farms spontaneously start burning and it just spreads and spreads.

I think of this every time somebody argues that nuclear fission can be replaced by solar/wind + huge battery farms. For example, see the recent discussion here:

https://news.ycombinator.com/item?id=41526789

Imagine the battery fire.
I wonder if anyone bothered to test some of this water runoff for dangerous chemicals… I’m no scientist, but generally the liquids inside batteries should stay inside the batteries whenever possible.

Though I guess normal car fires would have gasoline-tainted runoff anyway!
They get talked about a lot from my POV.
NotebookLM: Personalized AI research assistant powered by Google