skysight-inc/HackerNews huggingface dataset:
I always use websites when possible instead of installing yet more spyware disguised as a useful app. My bank, however, has the TOTP built in the app. You can't make a transaction without the phone app connected to the internet.
I am not the author, and am sharing feedback because you asked with honest curiosity.

Your writing is not clear to me. Using the word “really” is extraneous. Using “I think” is also extraneous; I assumed these are your thoughts.

As the author notes, replace “it” with “the article”, or better yet a specific quote or idea distilled from the article.

Helped “my write” should be helped “me write”. You use two -ly adverbs, which could be avoided by restructuring the sentence.

You also have a list of two (succinct and clear) and then a single item (better understood). Consider breaking these two thoughts into separate sentences.
Lindsay: Well, did it work for those people?

Tobias: No, it never does. I mean, these people somehow delude themselves into thinking it might, but ... But it might work for us.
Remember NFT? those were the days...
They’re opposites though?

Someone underwriting their own risk might as well not have actual insurance, as they’re just on the hook for actual damages correct?

So if they get sued for $1M, then they are on the hook for $1M (as an individual).

If everyone is sharing the risk, then everyone is on the hook for $1M/number of people.

So the individual that gets sued for $1M in a large state, might only be on the hook for a couple cents for their own lawsuit. Though they’d also be in the hook to the same degree for some other asshole getting sued.

Which is why insurance creates moral hazard (for things someone can control), and reduces catastrophic damage to individuals (for things someone cannot control).
Exactly, why not! Love it.
People who have aphantasia know right away something must be off for them when others enjoy things they don’t, such overly descriptive prose and so on. It is indeed very difficult to compare one’s internal experience with others’ and that’s one reason aphantasia flies under the radar.
But that's brutalist "web design" not architecture.
You aren't required to purchase a home or drive a car. If you chose to, as most Americans do, then yes: the demand is inelastic.

But that doesn't imply what you're saying unless the supplier has monopoly power, which they, by law, do not.
You're also free to find companies whose contracts don't have binding arbitration clauses. Good luck.
Votes are the sort term answer. People are losing their houses in Florida. Mortgages require insurance, and if you insurance goes up thousand a year, and hundreds a month, some people can't afford it, and lose their houses.

Longer term, this is bad for a society in general, and politicians do know this.

There are all sorts of potential societal consequences to people losing homes that cost the society (us!) money (homelessness, vandalism, entire neighborhoods going the way of Detroit suburbs, and much, much more). Society doesn't want this to happen.
(We've merged the thread into https://news.ycombinator.com/item?id=39955057, which does link to that.)
Interesting to see this pop up on HN. I once did some work with a large international data broker who had recently acquired a company which specialised on aerial photography and ML for identifying potential insurance risks.

I'm an infra guy by trade and really enjoyed learning about the tech while on their team. Mind blowing stuff to me!!
Very few people hate having insurance in case of accidents but a lot of people hate having guns stuck in their back and told to pay up for other people.

I pay a rate based on my risk factors which I actively work to maintain as low as possible. I don't want to be forced to pay for every reckless idiot in my country (of which there are too many to count).

But I also hate non-voluntary anything, so I'm weird.
There is no black and white “this will fix it” in cybersecurity. It is a continual arms race. Arguing “X will stop cybercrime” is so naive it hurts.
A recent defense of the Bayesian approach: https://www.astralcodexten.com/p/in-continued-defense-of-non... (and Kling's response: https://arnoldkling.substack.com/p/what-is-probability)

Likelihood statistics is another approach that combines the classical and Bayesian approaches. Its main benefit is that it does not rely on prior probabilities about an event. Instead, you can use MLE (maximum likelihood estimation, https://en.wikipedia.org/wiki/Maximum_likelihood_estimation) to estimate your parameter, with certain guarantees based on which estimator you choose for the parameter and how you calculate it. The downside of this approach is that it requires a strong assumption: that you know the distribution of outcomes in advance.

Side note: the only time you'll know the population parameter is if you set it yourself (i.e., in a simulation).

edit: Title should also probably be changed to the article's title ("How I Teach Statistics")
Maybe you're right, probably this is really just a matter of perspective and personal opinion of what "left" and "right" mean

All I know is that for a lot of people that I've spoken to they used to vote for leftist parties, and now they think those parties don't represent what they want anymore

The reason you never see anyone offer support for this is because of cancel culture, by the way. People are not going to state publicly which of their beliefs or opinions disagree with the current cultural shifts because large groups of people have proven they will target you, try to get you fired, try to get SWAT called to your house, and other such stuff

There is no upside to sharing potentially volatile political beliefs and some pretty serious potential downside

And yes, a lot of that behavior is coming from people with very vocal leftist attitudes
Apparently in your book anybody that isn't effectively negative on assets (everyone needs a place to live) is so rich they're not entitled to an opinion on insurance rates? This kind of weird aggro-dismissal seems like an inevitable result of "privilege" politics based around dragging everyone down to the lowest level. Having a place to live where one isn't burning heaps of money on rent should be our expected societal baseline, not some exceptional thing to be attacked.

But back to the topic - a total catastrophic structure loss would indeed be a problem. But from what I've seen, most insurance claims are not for total losses but rather things like water leaks and roof damage that have much higher sticker prices than what it actually costs to maintain/triage/mitigate/calmly repair. I've known people that have submitted claims for ice dams, oil burner blowbacks, new roofs ("wind damage"), finished basement water damage, etc. I will never submit an insurance claim for those type of things, and so it makes sense to at least consider self insuring, especially when rates are doubling every few years.
> Who are you writing for?

This is the hardest part of writing for me, especially blog posts.

I can never decide if I'm writing for a) highly technical readers who know 95% of the concepts my idea is based on, and I just want to connect the concepts together in a way the they might not have thought of, b) generally technical readers who have a grasp of the concepts my idea is based on, but will need some details to tie them into the idea I'm building on top, or c) readers who are not-especially-technical in the field, who might be nevertheless be interested in how a few things works, and my idea too.

I feel like part of it is that I am all these readers, depending on the subject. I enjoy reading articles about the areas of software dev I'm deeply interested in, but also about the odd idiosyncrasies of software that is used in fields I don't normally cover, but I also enjoy reading articles about e.g. the challenges involved in developing geothermal drilling systems, or elevator systems in 80+ story buildings, despite having very little experience in either.

I keep going through cycles of "If I just explain this part in a bit more detail, the post will be accessible to an order of magnitude more readers" to "this is way too long, I should cut some explanations, or add footnotes, or more wikipedia links" to "I'm assuming way too much previous knowledge here, or asking the reader to do too much extra work to follow my point".
I think the issue is that you rarely get to see a neat new solution to a given problem. Usually you'll see some kind of half-baked attempted solution that's worse than the already existing alternatives.
This tells you how well-argued the post is:

> The creepy, dissolute and rodent-looking BfV chief
No. Injection attacks have held the top place for literally decades. They are kindergarten level: validate your inputs. Lazy or incompetent developers still fail to do so.
If you are such a risk when driving no insurer will touch you, I would like you off the road.
Yes. Credit is inflationary.
That sounds like informal underwriting. If you are forbidden by law from better underwriting, then selecting by conscientiousness is a sensible proxy.
With ROCm 6 I think new-ish AMD GPUs are pretty good too.

https://ollama.com/blog/amd-preview

With that said, I dont think you need anything special to run LLMs these days. I can run 7B models on a 4 year old AMD or Intel CPU (no GPU), for programming tasks.
Right on both counts
I've enjoyed writing a few projects in x86-64 assembly as well, for what it's worth. Even though I'm sure that any C compiler would generate better assembly than my handwritten one. Flat assembler is great, by the way.
Injection attacks AFAIK have held the top place since forever.

It is why people keep buying WAF's.
It's because Microsoft has OKRs to hit that have nothing to do with UI customizability or even giving users what they want.

I realized this in the 90s. Windows 9x, theoretically, should never have existed. I knew this because a DOS subsystem with great speed and compatibility, DOSEMU, existed for Linux. You could play Doom with sound at full speed in DOSEMU on contemporary Pentium hardware. If the open source community could do that, Microsoft, the developers of DOS, could develop a DOS layer for Windows NT that was much better than the sluggish, feature-incomplete layer they did ship. But they didn't prioritize the effort it would take to do so, especially since dividing the Win32 ecosystem into 9x, NT workstation and NT server allowed binning of different Windows versions at different price points.
Might want to look it up before getting set on your definition. Sibling comment has it (mostly) right: it’s literally “raw concrete”.
Hashing Infrastructures
I ended up learning about PID's when playing the game From the Depths, where you have to use PID's alongside thruster mechanisms to keep your craft balanced. It felt like I picked up how they worked better by using a 'hands on' example of them, in this case a game.
If I ran the world I'd completely get rid of the expectation your parents should pay for college.

Right now tons of people who's parents just refuse to provide financial information don't get any aid at all. This is very common if you have a bad home life. I fell into this category.

I grew up on welfare and I'm at the level were if it worked out with either of my last 3 partners we'd be at 300k or more. Life is funny...
Running on a VM on Debian 12 with 6.1 kernel. Got this:
"failed to detect overwritten pte: is more PTE spray needed? pmd: 00000000cafebabe"
It's called brutalism because brute is the French word for concrete. To many being made out of concrete would be a defining feature of brutalism, to others it's the exposed building materials without façade.
This might be great as an art piece, but I doubt it's something most HN users would use on a daily basis.

Usability and readability first!
I was reading "50 years of text games", and one game (Hunt The Wumpus) piqued my interest so I decided to reimplement it in go, based only on the description of the book, initial (working) commit took a few hours over the weekend, then I fell down a rabbit hole when I found out the original source code, and description of its sequels, so I took a few more weekend to implement that then even more features. Probably nobody except a friend played it but for once it felt good developing something outside of work or the advent of code.
https://github.com/Koumbaya/wumpus
So Netflix and such DO NOT work on phone? That's really frustrating
This is much less readable than classic HN, which is already plenty brutalist.
Not coding, but my daughter Aelyth and I are a musical duo. Our first album (https://sidesister.bandcamp.com) took four years to complete thanks to COVID lockdowns and living in different cities.

On Thursday evening we rendezvoused at an equidistant AirBnB to sketch out our second album. It's now Sunday morning, Aelyth's just caught the train home because she's working today, but we have a concept, a title and ten songs for the new album!

There are admittedly another seven song ideas we've not had time to explore, but we've accomplished much more, much more quickly, than either of us thought possible. We've also committed to an overall musical style, plus boundaries on arrangements and instruments with the intention of keeping the production phase as concise as possible.
I made a hundred million TVs boot in half the time.
>This whole thread is about the ruling on this case.

So you are saying no one can discuss the 5th circuit in general in response to one of its rulings? One might even say "this ruling is reasonable, but that court sure hasn't been lately" and you'd still say the same. Get a grip!

>Incidentally, nobody including you has mentioned what about this ruling is "wild" and "twisted" yet despite numerous requests to do so. Are you aware how discussions on a subject matter are conducted?

I never said any of those things. You are really picking the wrong bone with me.
Excel on windows is an javascript application too right? No ?
Based on the other comment thread, it seems like Play Integrity and SafetyNet do not succeed and as such, can't really use Netflix, is that correct?
Models learn so you don’t have to :)
Consequences are happening.

People just don't see them because this happens well above the IC pay grade and takes some time to percolate down and no one wants to publicly announce you shitcanned 5-10 people in middle management and security leadership because you enter thorny employee litigation territory.

That said, I agree with the author about mismatched expectations, though I can safely say that $500k year is VERY HIGH for a CISO. I know CISOs for publicly listed F500s who earn around 200-300k at most after 15-20 YoE.

The bigger issue is CISOs, VP Security, and Security ICs are not enabled institutionally.

If I'm honest, most security engineers suck. 90% are crappy IT Admins or Compliance Monkeys who did CISSP and maybe worked for PWC or an MDR for 1-2 years and don't know the difference between NFTables and NTFS. Most CISOs and VP Sec are former security engineers in turn.

Security Engineering NEEDS Security Minded Engineers. Now that development teams own Platform Management and Deployment, they should also be enabled to own Security, and a Security Team of 10x Engineers with a Security background should help with implementation and guidance internally. At least this is the model I've seen in tech forward public companies (some of whom HNers wouldn't even realize are tech first).

I also agree with Scarlett that data protection laws are critical and need to be enforced. That said, it's not enough (wouldn't protect against a vulnerability disclosure or misconfigured ACLs), and several Security ICs I trust recognize that as well. That said, the tone of the author and a couple well intentioned security minded engineers can impact this larger effort. You trap more flies with honey as they say.

A security minded engineer cannot present this kind of an article to their non-technical leadership, as it opens multiple questions about liability, ownership, and potential incompetence.

> Absolutely no amount of gentle pleas disguised as executive orders from the White House urging people to use memory-safe languages will solve the problem. CISA, despite all the phenomenal work they do, can't charge people who mishandle data with negligence; critical infrastructure involved or not

Amen to that! There's a reason why pushing for cybersecurity insurance might be a good push - hurting the bottom line is a good forcing function for change.

----------

Also, Engineers need to stop being shitty to QA and Platform Engineers.

Treat QA, IT, and DevOps as a first class citizen.

I don't give a rat's ass that you like using Mosh or xyz project on GitHub (not trying to pick on Mosh).

I don't care that you feel restricted by having to use MacOS laptops and SSHing into a CoLo protected behind ZPA when you'd rather use ArchLinux on your work laptop.

Every bug, misconfiguration, or non-standard platform deployment needs to be treated as a potential security liability.

Sure it might slow down the deployment of your "yet another wrapper around an LLM SaaS" but there absolutely needs to validation.
>For an efficient enough company, a project like this needs just one or two dedicated engineers.

Maybe for a research project or a hobby project, but not for a real, high performance database to be used in a business-critical application.

FTA:

"Databases are a nightmare to write, from Atomicity, Consistency, Isolation, and Durability (ACID) requirements to sharding to fault recovery to administration - everything is hard beyond belief."

>Engineers should be their own PMs.

For small projects, sure (your "one or two dedicated engineers"). But once you start tackling projects that require larger teams, or even teams of teams, you need someone to track and prioritize the work remaining and the work in progress (as well as the corresponding budgets for personnel, services, and other resources). Similar to the way a sole proprietor can do their own accounting, but a multi-million dollar business probably should have an accountant.

As an aside, I wonder if this might be a use case for a bitmap db engine like Featurebase (https://www.featurebase.com/).
This is a pretty hyped-up optimizer that seems to have okay-ish performance in-practice, but there are a number of major red flags here. For one, the baselines are decently sandbagged, but the twitter posts sharing them (which are pretty hype-y) directly says that the baselines are "highly tuned" and that there's no benchmark trickery (which is flat-out wrong). If someone has not had experience with said benchmarks, it is a plausible statement, having worked with some these datasets very closely, some of the baselines are simply terrible, I don't know where they came from.

Additionally, the optimizer does actually appear to have a kind of momentum, despite claims directly saying the contrary, and uses it with a nesterov-like step (line 2 of 3 in the inner loop). Finally, it is 'schedule-free' because the schedule is actually hardcoded into the algorithm itself -- 1./steps_taken which is not necessarily a rare learning rate schedule. This is a decently robust but sometimes suboptimal schedule, and I find it sketchy to make claims that it is 'schedule-free'. This also cripples the optimizer by tying performance to the number of steps taken -- which is potentially a problem if you are using any batchsize+lr scaling strategies as I understand.

There is a mixture of hype and substance here, and I wish the author was more straightforward with their approach and claims. I think there is the potential for a good "bolts-included" optimizer with some of the ideas being presented here, but the amount of overhyping and deception makes me not want to trust any of the following work coming.

Unfortunately, hype is what sells best on Twitter, and some of the claims being made here appear to be at the very best deceptive, and at the very worst, untrue. I could be wrong -- these are just my personal opinions from my own experience, but I do occasionally find myself distraught about the things that tend to catch wind in the technical news cycle.

-Fern
Interesting, but I do wonder what the result would be if you excluded _test.go ?
Unfinished concrete, specifically. I would translate "brut" as "bare" or "unrefined" here. English brutality is related to French brut, but in French it means more like crude, unrefined, raw, blunt, with no particular sense of animalistic or violent.
Run-Time Polymorphism in Swift
If I could I'd delete my original comment since I did more research and you're right.

https://stackoverflow.com/questions/14861908/apdu-command-to...
447 pages? That is like multiple semesters of course work.

There should be some rule about how the rules can't be longer than that the drafter can recite them by heart.
Nassim Taleb was right again.
Websites have spent the last 20 years removing user customizable functionality (think RSS feeds and making API private). While the tech may be possible, I don't see this being a reality without a major reversal in app development philosophies.

Companies want to control what you see so they can control their revenue. Why would they want to expose their data and utility to UIs where they have limited ability to monetize?
Is there a list of companies out there you can share, or are you going about it on your own?
I can understand feeling like both taxes and insurance premiums are too high, but the ability to make choices other than the specifically least risky one is one that fundamentally allows us to exercise our free will.

Those in Auburn are, by the same idea, subsidizing windows that get smashed when parking downtown, or even if you walk, the extra risk that you are hurt by someone while walking in a place with more crime per square mile.

You can live far away from a downtown and have to get your car smogged, because we wanted cars in the cities to provide for clean air.

I don’t mean we need to accept all risk in society, but for me there’s a very worrying trend against ANY risk/cost that doesn’t directly benefit the person advocating against it.

Ultimately I know it comes back to the current economic situation, because if everyone feels like they’re struggling there’s less thought to care for others.
OpenSwiftUI
Maybe you could use column_name, dtype, min, max columns and sidestep the nulls, but you’d have to convert “min” and “max” to text so they’re all the same type?

Could also split the table by dtype outside of sql to ditch null values without needing to convert non-null ranges to text, but then you split your data into multiple tables, maybe that’s inconvenient to break table schemas into chunks?
> We demonstrate our approach in the practical setting of Erlang, with a tool implementing protocol composition that both generates Erlang code from a protocol and generates a protocol from Erlang code.

That's great. Erlang has gen_statem as a built-in behavior so it seems appropriate to use it. Also Joe Armstrong had been talking about protocols for the longest time. He would say something like "Tell me what's on the wire! Don't give me some C++ API".

[1] https://www.erlang.org/doc/design_principles/statem
Restoration is possible: the hunt for Scotland's ancient wild pinewoods
In practice what actually happens is that these people will drive anyways and cause damage before being pulled over, except now they have no insurance and it’s a whole mess.

It is also the theory behind universal healthcare coverage, because people will have medical issues that eventually end them in the ER regardless of coverage status and someone has to get paid for services rendered. And also insurers will literally take any excuse to deny coverage if they can.
Cool! And so very overdue
Ive used my phone (Redmi Note 10S) to record decent video. Post work with KDenlive.

Mind your settings.
Exactly. There are a hundred questions that come to mind like how does it handle concurrent writes, sharding, views.

https://en.wikipedia.org/wiki/Database#Database_management_s...

I'm sure they learned a lot, but probably a waste in the long run