skysight-inc/HackerNews huggingface dataset:
It would be nice if everyone had a high quality of life or even basic food security/water to start, but how exactly does that solve the issue above where psychopaths and MBAs extract profit above all else? There are externalities like say not killing people with your medications/pollution/planes that fall out of the sky because you cut corners that aren't addressed by what you say and unless there is personal responsibility won't be addressed by corporations. I admit my bias is farther left than that: I firmly think intentionally privatizing the profit and socializing the losses should be a serious crime with lasting personal consequences. Regular people have consequences when they fuck up or run a scam.
I can’t back up the data in a PWA.
Do not miss P.S. section at the end. It is very inspiring! Quote:

"We’re not researchers at all. We’re just two people who became obsessed with a problem and put their meager knowledge to use, beating rocks against rocks in different configurations until something resembling a spearhead came out.
...
You, too, can do something like this. Find a problem. Become obsessed with it. Learn everything you can about it. Fall down dead ends. Give up, and then keep thinking about the problem at night. Have Eureka moments that lead you down other dead ends. ...
"
Ah. But, remember, you are not your thoughts.
I'd like to know what about HRT causes a Lowe's floor worker to turn into a "midlevel executive" within "months"!
You need stronger materials, but in general the more pressure the better.
Serialization is largely a Solved Problem in modern C++ thanks to template metaprogramming. Wrangling a kludge DSL instead of Serialize<T> betrays poor lang knowledge...
could it be that AAA games in general are more AAA because of budget and less because of the fun? Take crab champions, silly little indie game you can pick up for 14 dollars, which will bring you more hours of fun than a lot of AAA titles of the same genre.
Navy Seals aren't firing artillery. The article says the Seals brains were damaged by their own weapons which I assume to be rifles but maybe I'm wrong.
Location: Pacific/Los Angeles

Remote: Yes

Willing to relocate: No

Technologies: SQL, Glide, Hubspot, Asana, Monday, Miro, Git, JIRA, B2B, B2B2C, Scrum, Postgres, Canva, Trello, Slack

Résumé/CV: https://umagp.com

Email: leslie@alle.llc

Certifications: Professional Scrum Master I, Professional Scrum Product Owner I

---

I'm an experienced generalist with a background in early-stage startup development across a range of product verticals. Most recently, I was the cofounder of a SaaS/e-commerce startup and I'm currently an associate at an early stage fund. I spent four years working as a marketing consultant helping companies to understand product-market fit, and helping to set up and model data in their CRM, marketing software, and CMS systems. I'm looking for mid-level product/marketing positions, particularly in SaaS/B2B/B2B2C, and ideally with a socially-impactful company.
Yes, even within a company my threshold for accepting a change can vary pretty widely depending on my experience and relationship with the author. For an external contributor or someone I've never collaborated with (by reviewing code or having my code reviewed), I don't accept the code until almost everything is worked out to my satisfaction. With someone I work with regularly, it's not uncommon to accept a change with a comment like "this is all good, but you need to take X into account which will change almost everything in this patch" (I exaggerate, but only slightly). I know whether an update could be problematic and whether it is necessary to see it again. Sometimes there are a couple of obvious ways that something could be done, they picked one but weren't tied to it if I had a reason for picking a different one, I picked a different one for $REASON.

Most are somewhere in between.

Though in some ways it works the other way around. For an unfamiliar open source contributor, I need to be confident that the change is worthwhile. I will be lenient on stylistic things, and I'll just land their patch and then fix it up afterwards. For someone I've worked with a bunch (whether a familiar contributor or a coworker), I will trust their opinion on the underlying quality of a change, but be less tolerant of unnecessary stylistic differences since they should have already come into alignment on those and it's more likely to be an oversight if they missed something. (Plus, I don't want to be fixing up their changes after the fact, given that >90% of patches will come from regular contributors.)
What the US has today is inarguably better than what we had before regulation. That is worth retaining and reinforcing, and it makes no sense to undo the regulation and go back to what was verifiably worse.

This debate doesn't have to happen in the realm of hypothesis and ideology, it’s all in the historical record, simply look at the abuses of industry during the 19th and 20th century before the institution of various forms of regulation of those industries.

Pure Food and Drug Act, preventing countless deaths from adulterated products.

Clean Air Act, from 1970 led to a 78% drop in air pollutants to date. Think LA 1970s vs now. Think Beijing vs NYC or any major American or European metropolitan/industrial center.

The Clean Water Act meant we stopped having Ohio's rivers catch fire. Lead paint regulations reduced the percentage of young children with elevated blood lead levels from 88% in the 1970s to 0.5% in 2016.

Look right now around the world at the behavior of companies operating in parts of the developing world where there is a dramatically reduced or nonexistent regulatory standard in terms of things like labor law, environmental protection, and consumer safety.

Corporations would love if the only recourse was lawsuits that they could spend literal decades repeatedly appealing in court, allowing them to reap massive profits in the short term while delaying any concrete penalties, if any, into the indefinite future, and frequently having those final penalties, again if any, represent a small fraction of their profits from the behaviors in question.

Look at restitution after the BP oil spill, how’s that working out? Hint: predictably horribly - https://apnews.com/article/gulf-spill-lawsuits-bp-health-che...

"Let companies murder people, poison people, abuse people, and irreversibly devastate the world, then let people try to sue them after the fact" is such a transparently terrible strategy for organizing a society.

We've already run this experiment of regulation vs no regulation countless times over two centuries. The default state of the world is one without regulation, and that's what we had at the dawn of industrialization and that's what still we have now in many parts of the developing world.

The horrors that constantly and predictably result are the entire reason for the emergence of regulation to protect people from the inevitable tendency of industries to produce negative externalities.
Not to mention that if you're the kind of person who would buy this level of game on a handheld device, you've been burned by previous poor ports so are hesitant to drop any kind of cash on ports until they're well and truly tested and verified as working as expected.
This is a link to a paper with the title Compressing Search with Language Models did you, perhaps, get the URL wrong?
Earl Warren was a political hack. William Douglas was a political hack.

Every SCOTUS Justice, except for for Thomas, was an absolute top-tier jurist at the time they were appointed.

Every SCOTUS Justice, except Thomas, could have received a tenured professorship at any law school in the country, a partnership at any law firm in the country, editorship of almost any law journal in the country, etc.

Any one, including Thomas, would have been welcome as a professor at the Unversities of Oxford, Cambridge, Edinburgh, Sydney, etc; a magic circle UK law firm; or as arbiter in international trade.

Any one, including Thomas, would have been a shoe in for attorney general or solicited general of US. Any one, including Thomas, could have gotten a position as US Attorney in either a Democratic or Republican administration.

We have an insanely well qualified SCOTUS, mostly because of how arduous the confirmation process is.
I always thought it’s good practice in C/C++ to have only one translation unit in release builds e.g. SQLite amalgamations, instead of relying on LTO. It also speeds up compilation because it isn’t recompiling the same header files over and over again.
Location: LA area

Remote: Hybrid in the LA area (especially south bay or OC), remote is fine too.

Willing to relocate: Generally no, might consider Denver or Portland for the right position.

Technologies: Lately Ruby/Rails. Python/Flask before that. Some React sprinkled in there. Standard suite of supporting tech: postgres, some dynamo, redis, memcached, observability tooling, etc. I’m not too picky about tech stack – I've switched a few times and I'll probably be able to pick yours up.

Resume: on request

Email: audible.cleats-07@icloud.com

I'm a value-minded backend engineer, currently in a staff+ role at a successful ecomm company. 16ish YoE, most of that in backend roles at startups. I’m value/business oriented, pragmatic when it comes to tech choices (I can work well in codebases I didn’t write, err on the side of incremental improvements rather than ground-up rewrites, and know where/how to compromise technical perfection for other concerns), collaborate well, and enjoy learning about business/customers/etc. I’ve been with my current employer for several years, currently lead engineering on a critical business system (supporting 10-15 ICs) and support the broader org on some infrastructure/system QoL projects.

I’m targeting senior/staff backend IC roles with a hands-on focus. I like engineering teams that are value/business driven, pragmatic, collaborate well both internally and with folks outside of engineering, supportive and have a good variety of backgrounds/experience levels (I’d love to not be the most senior person in the room for a change). Prefer companies that are mature/established enough to not have a crazy work/life balance. Plus points for being related to health, fitness, the environment, logistics/shipping. US citizen, if it matters.
Running a database on zfs can work well but introduces a whole new world of whitepapers to read and tuning options to consider :/
I review a lot of code with the mindset of yes and…

Basically when I start the PR is approved in my head until I find something blocking. I.e. major problem that causes dataloss, big performance issue or breaks other code. Anything else is a minor comment at most. The PR is approved by default. This gives the dev responsibility and ownership. Plus it increases release cadence

Doing a follow up PR to improve or fix something is just as fast as blocking the MR, but blocking the MR can be bad for morale.

This strategy might work better in young startups where having the feature _exist_ is better than not shipping.
in my experience this builds up responsibility and ownership and removes the whole policing of other peoples work vibe around code review.

Also decisions and discussion around formatting, when to test, design, features, functionality, architecture should not happen during code review, they should have happened way before coding, or collaboratively while working. Code review is the worst time for that stuff, imho it should be to sanity check implementation.
You mean they don't censor the bug reports and try to gaslight you into believing their software is flawless anymore?

That's a tremendous improvement when compared to the time I interacted with them.
That's the one. Obviously not popular since I made it for an app I work on.

What's wrong with decorators? Technically not needed but I like things being explicit.
I think they meant that the stress was caused by the TBIs from the mortar shockwaves, not by what they experienced otherwise
I interpreted it as “there’s such a big difference between artillery and a handgun you clearly have never been around an actual gun being fired before”

Still snarky, but there is a point.
I'm an extremely light user (just on a few small projects), but

> Have you run into extra complexity and messes because of having two VCSes interacting in one working copy ?

Well, making git commits in a colocated jujutsu repository was a very confusing experience, because at some point I realized I wasn't on a git branch like I thought I was (after a few commits!). jj somehow magically did the right thing though and after switching back to it I had the commits I tried to make in jj and they worked just fine.
I’m an FBI agent and I kill my wife. Am I immune from prosecution unless Congress appoints a special counsel, simply because I work in the executive branch?
Sleep is nature's punishment to those who strive to build great works.

Don't ask me how I know :(
I can't understand how it'd need less maintenance.

A conveyer belt spreads the moving parts over hundreds of miles; with trains you can push all them cars to a yard for maintenance at a single point.
Sorry if that was confusing. The most of the experiments in the paper are around U.S. flu rate predictions using a compressed version of Google Search.
U.S. DoD Open-Source FAQ (2021), https://dodcio.defense.gov/Open-Source-Software-FAQ/

Both entirely new programs and improvements of existing OSS have been developed using U.S. government funds. There are far too many examples to list; a few examples are..

Security-Enhanced Linux (SELinux)
bind’s implementation of DNS security (DNSSEC)
BSD TCP/IP suite - Provided the basis of the Internet

A recent (2019) example is Ghidra, https://ghidra-sre.org.
SSDs could use 1K layer chips by 2027, maybe allowing 20 TB drives for <$300
Steve Ballmer Is Richer Than Bill Gates, a First for Microsoft Billionaires
Is that because it's behind cloudflare? I'm pretty sure it still runs primarily on a single server in a Colo (i.e. except in times of hardware failure or other physical realities).
It feels like a common trope among businesses of a certain size, when someone asks "Why does nobody read the emails?" without looking at the inbox from an engineer's perspective.

My job is not to read emails. I don't open a Gmail window with 200 unread CC'd responses and think that it's my duty to untangle that. I work on what I'm paid to do and wait until I'm told otherwise by my manager. The reason every single email client doesn't default to reply-all is because engineers are conspiring together underground to stop the unjust suffering and PIPs caused by missing the needle in the email haystack. Company-wide emails are the single point-of-failure that necessitate alternative communication platforms like Slack.
My first sentence. Are you serious?
I don't think they were demanding it work with Firefox.

I think they genuinely were interested to learn more about the deficiencies of Firefox.
although I agree that there are worlds of difference between small arms and artillery, I would like to point out that ear protection.. protects your ears.

there is no good way to protect from concussive blasts aside from avoidance and shelter.

fwiw most DoD studies have found that concussive blasts that seem to be damaging to personnel start at around the AT4/Carl Gustaf range of large shoulder-fired almost-artillery -- understandably since they're large and mostly open-air combustion driven.[0]

[0]: https://www.militarytimes.com/news/your-military/2018/05/01/...
So the government can violate my rights as long as it kills me too? That doesn’t pass a sniff test.
This is all great thinking.

Except for those of us who live in a world where most of their OS and utilities and libraries were originally written decades before Rust existed, and often even before Java existed. And where "legacy" C code pretty much underpins everything running on the public internet and which you need to connect to.

There's a very real risk that reimplementing every piece of code on a modern internet connected server in exciting new "safe" languages and libc-type things - by a bunch of "modern" programmers who do not have the learning experience of decades worth of mistakes - will end up with not just new implementation of old and fixed bugs and security problems, but also with new implementations that are incompatible in strange and hard to debug ways with every existing piece of software that uses SSH protocols as they are deployed in the field.

I, for one, and not going to install and put into production version 1.0 of some new OpenSSH replacement written in Rust out Go or Java, which has a non zero chance of strange edge case bugs that are different when connecting to SSH on different Linux/BSD/Windows distros or versions, across different cpu architectures, and probably have subtly different bugs when connecting to different cloud hyperscalers.
padenot already has
Yeah, that guy was a mistake
What's the engine? I'm guessing WebKit or custom?

Screenshots would be nice.
I think this is a very unproductive and pedantic take of functional programming. Inside the function, all things being equal, the implementation isn’t important. The important thing is that it’s isolated, self contained and does not perform I/O
Should == ‘I wish’.

If it comes down to it, something has to break the tie somehow right? Because while in most years, there is plenty of water, in the years there isn’t it can literally be life and death. And timelines for figuring out who does and does not get access need to be as short as days sometimes.

Different courts have decided different rules, but senior rights holder having priority is basically ‘first person to be using it (historically) gets to keep using it if there is a conflict’.

Which stops someone from moving in and screwing over the existing people (as hard!). Think of the alternative - you build a house in a remote area, dependent on a spring. You have plenty of water.

Housing development gets built 20 years later, also dependent on the spring. In good years, everyone has plenty. In bad years…. You die of thirst? Or what? At least the subdivision knew what they were getting into, when you built your place there was no subdivision!

Same with your farm example. First guy to setup the farm did so with expectations of a certain situation. New guy moves in, and should he now get the rights to half of the ‘the first guys water’ in lean years? Maybe meaning neither have enough water to farm? Or should the first guy have the right to the water he was guaranteed when he first moved in, and the second guy might not get enough in a lean year - but at least knew that was what he deal before he moved in?

Others are king of Solomon like ‘split it down the middle’ (everyone hates this idea, since no one might end up with enough water), or ‘fixed allocations first, then proportional later’, or ‘life critical uses first, then lower priority later’ (easy to game/screw with existing rights holders - add enough new mouths, and none of the ‘less critical’ rights holders get any).

Courts move too slow to resolve these kinds of issues when they become critical - which could be on as short a term as a week or a few days, with no notice.

And not having a general rule resolve these
kinds of things leaves a massive amount of uncertainly that due to the severe consequences of these kinds of situations can easily lead to people getting killed or even wide scale wars starting.

Or as they say in the US West - whiskey is for drinking, water is for fighting over.
Sometimes feature requests are actually bugs and can be illustrative of one not properly understanding design.

But I think it is important how user feature requests are interpreted. They have a frustration that you might not be aware of but they aren't aware of all the code and constraints. It can even be in design, which is still important. Very often there is a way to resolve a feature request that is not what the user explicitly asks for. But to do that you have to read between the lines, and carefully. Of course, some people go completely the wrong way with this and cough Apple cough decide that they know what is best for the user. It's totally a hard balance to strike, but I think it is very common for it to be framed much simpler.

There's the joke that the user is dumb, and maybe they are, but that doesn't mean the issue they face is. It's not always dumb when a person pulls on a door that says push, because it may actually be that the sign and design are saying different things[0]. And personally, I like when users suggest methods of resolving the problem. I might throw that in the garbage, but it can often give me better context clues as to what they're trying to ask for and really does tell me if they're thinking hard about the problem that they care about the product. They just don't have the same vantage point that I do, and that's okay.

[0] https://www.youtube.com/watch?v=yY96hTb8WgI
It’s more like a mid level capable person was working at lowes until they got their hormones in balance to function optimally which resolved their depression or other symptoms
Abstractions Are the Best Abstractions are the Worst
i thought xerox parc had lost its glamour and was being mismanaged by the parent company… maybe that was just a rumour
Yeah I eventually saw it.
It’s not just the orders of magnitude difference in number of rounds fired; it’s the size and power of the rounds. SEALs don’t shoot soda cans with .22 rifles.
Perhaps you could update to the paper title then? This doesn't seem like it should have the prefix 'Show HN' - Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread. https://news.ycombinator.com/showhn.html

And guidelines request the original title, unless it is misleading or linkbait https://news.ycombinator.com/newsguidelines.html
Most public sector code is not made public for the shame it would bring the country.
It may be useful in times like these to contemplate the impermanence and randomless of the world we live in.

The original job I had was "welder", for which the lower end of the pay range was about $20-$30k, and after some additional decades of experience you could dream of rising to $40-$50k.

I have had some pretty dumb programming jobs, but on the whole it seems pretty fortunate for there to be a job where you can be a college dropout and outearn dentists (or, for that matter, fleet admirals in the US Navy).
Sure, but code has a level of complexity that boxes and lines abstract away. If you want to describe a certain level of complexity, you'll need code or something that achieves a similar level of capability. If you don't need that high level of complexity, often because you're abstracting complexity away, it's hard to find an alternative that isn't better than boxes and lines. If there's a better alternative, nobody's found it yet. Boxes and lines appear to be a final state to which all roads lead.
they're talking about blasts from open-air combustion shoulder mounted anti-tank weapons.. very nearly artillery, and very loud.[0] . The article linked is the one mentioned in the parent article.

one of the major problems with such weapons is that although the support crew can shield themselves, often the firing soldier cannot due to operation of the weapon.

[0]: https://www.nytimes.com/2023/11/26/us/military-brain-injury-...
It's Chromium, it's just the standard web view provided by Qt.
How Grafana Security is using Dapr to improve vulnerability scanning
Yeah sorry, already updated it!