skysight-inc/HackerNews huggingface dataset:
>software testing, ISO 9000, GMP

Major difference is that ISO and GMP are intended to be mandated in a way that can only result in excess mindless behavior to some extent, but software testing can actually be made to avoid that.

>may be an essential part of achieving quality, but they don't cause it.

In the case of ISO 9000 with 20/20 hindsight it's more like it can be bureaucratically essential to gain acceptance among those orgs who don't know quality enough to recognize it on their own.

This was primarily an anti-competitive standard to keep less-bureaucratic products (from less-developed counties as well as the US) from outside Europe away from the continent, issued during an unfavorable currency situation before the Euro or even the EU existed.

If Deming were here today we'd be talking about the way ISO 9000 brought the continuous improvement process to its knees by requiring additional bureaucracy which diverts more resources than were once being more effectively deployed in true quality improvement efforts. The result has been a freezing in place of the quality that was reached when ISO 9000 accreditation is achieved. It's a huge milestone and the effort just to maintain that level of recognition is entirely focused on no further changes being made if at all possible, due to the extreme added difficulty of pushing a change up or down through the entire organization.

Not every one is frozen back to 1987, but the pervasiveness for so long has had an exorbitantly unmeasurable cost. Especially in terms of reduced innovation.

Plus many US companies that were in production before ISO were making higher quality products then than they do now, it really helps to see this if you were there at the time.
It's darkly hilarious how Amazon's motto of "Disagree but Commit" was originally about leadership bowing to the data and opinions of their direct reports, and now it's a cudgel used by leadership to shut down discussion from their workforce.

A shame, really.
SHORTAGE LOL

https://youtu.be/uPfFFmCqWow?si=9KoKNgylnKsQk-UY

Youth obesity
Sounds like each thing should know how to search for active instances of itself, given a date range, which is a common OO abstraction.
Given the development time and effort required to get SC to its current state, it’s hard to see another game getting close to it.
For truly high performers who are indispensable and a flight risk, the company will always make exceptions. But those are truly rare (<5%) and even among those, some want RTO, some want WFH and some want a hybrid.
> is to create a functional mini-DSL

Exactly. Is there a formal term for this?

Instead of one gigantic function with 50 parameters, you have 100 "template" functions, that all make use 60 different "helper" functions (what you're calling the DSL).

Instead of castles-of-logic abstraction, it's nuts-and-bolts or grass-roots abstractions. I've never come across a name for this development style.

But it generally works extremely well when building processes for tens/hundreds of data formats or customers or what have you.
You really think that you can do anything "better than anyone else"? Also, what is your basis of comparison for "you won't achieve anything interesting"? You have to have a very small world view to believe either of these; in the large scale we don't know what's important or what others are capable of.

Twiddling your thumbs may be the most important task in the universe, we simply do not know.
I’ve been using C# since 2001, before C# 2.0 and its generics rewrite and when J# was a promising star in Microsoft’s eye. There is no “Microsoft bullshit” surrounding the language any more. Microsoft runs it in production on Linux and the language (and runtime) has been transformed.

(If only we could first-class FreeBSD support…)
I often hear this kind of praise for Ruby but have never really dug into it myself. Does anyone have any links to pages that do a good job of covering some of the main selling points of Ruby in terms of syntax, features, ecosystem, etc.?
> Live debt free. Don’t become entangled in needing to work to survive

I don't know about you but with no debt and no income I wouldn't survive very long, as I need annoying things like food.
This is excellent reasoning. "Retirement" as it is thought of today, is a fairly recent phenomenon and was originally thought to be quite brief.

From my experience long periods scattered through your life is better. I was able to retire in my early 30s and have just engaged in intense multi-year periods of work since, always with gaps of a year or more afterwards. It allowed me to spend more time as a parent, more time with my spouse, and to spend time doing fun activities I will not be able to do in my 70s.

I think some professionals will have trouble adapting to this because there will be a strong impetus to "advance their career" rather than take a gap. But encouraging this mode may encourage people to take these gaps, and in fact improve the balance vs today's system in which it's mostly women who have trouble advancing because of time off with the kids.
Any handbook about the strength of materials has a chapter about creep a.k.a. cold flow.

The handbooks from immediately after WW2 already included such a chapter, but I believe that the first studies of this problem must be much older.

When any metallic structure is designed, it must be verified that it will not fail in any of the possible modes, including due to flow over the intended lifetime.

See in:

https://en.wikipedia.org/wiki/Creep_(deformation)

at "Temperature dependence".

By the approximate rule mentioned there, zinc begins to have non-negligible creep already above minus thirty Celsius degrees, so at normal ambient temperatures you must always compute the creep of zinc for any structural design.

On the other hand, metals like iron or copper have negligible creep at room temperature, even when pure.

Aluminum and magnesium begin to have non-negligible creep at temperatures only a little above normal ambient temperatures.

Hard alloys can have much lower flowing speeds than the metals included in their composition.

In integrated circuits, the metal connections are affected by electromigration, which is the flowing of the metal due to electrical current instead of mechanical stress.

The electromigration properties and creep properties of a metal are closely related. In the beginning, the ICs used pure aluminum for interconnections, but when their size was reduced, the connections began to fail after a too short lifetime.

The first solution for this problem was the replacement of pure aluminum with harder aluminum alloys, including small quantities of copper and/or silicon.

When the ICs became even smaller, the aluminum alloys had to be replaced with a metal having a higher melting temperature, i.e. copper, which fortunately also has a lower resistivity.
make a question post on Julia discourse, many people including me are more than happy to do free work for you!
They spoiled most of the movie in the trailer, back in 1995.

My friend still to this day says he would have preferred to go in blind, not knowing who the bad guy was. It would have been an epic reveal.
>Elite Dangerous is one of the worst. It's simply not fun. So pointlessly grindy for what is predominantly a single player game. I was so excited for the first 5-10 hours, and then so disappointed as it was obvious that every mechanic was just another massive progress bar that barely moved after hours of play.

Speak for yourself, I had a lot of fun for hundreds of hours and revisited the game multiple times over the years. I did space trucking and mining and combat at various times, and enjoyed never paying a monthly fee for an MMO.

Elite Dangerous was announced at the same time as Star Citizen, for comparison, and it's so old now that the main reason I don't play it anymore is because I did everything I could do in single player and the concept has finally lost its allure.

I have a friend who played thousands of hours because he was more social than I and wound up in a large player guild.

I love(d) Elite so much that I bought a VR headset and a joystick solely for it, and I don't regret these purchases.
> The software and hardware stack does itself need to be secure of course, but Apple has got pretty good at that.

lol
I suppose what the parent is saying is that's not the default. Fresh install of anything is still password and GitHub key import isn't a panacea.
Congratulations on beginning your spiritual journey. 99% of that stuff I handle in a Repl hooked into Clojure using Cider.
Languages that won, win, and will win are all of those that are moving towards being smart, in the sense that the compilers/transpilers infer what the programmer is trying to do and generate the appropriate code under the hood.

The future of programming is describing the majority of programs in something thats even closer to English, and then fine tuning it with something like python, all of which will result in natively compiled optimal binary.
I would love to see sabbaticals become more the norm, but I see a few problems with this particular plan and other problems with how they are generally implemented.

For this specific plan, it asks a 35-year-old to agree to work an additional year in their 60s for 3 months' sabbatical in their 30s. That's a pretty bad deal, not only because of the imbalance between what you gain and what you sacrifice, but also because there are so many unknowns about your ability to work in your 60s. And how do you really enforce something like that?

But in general, one major problem with sabbaticals is that they are almost always tied to your employer and require you to rack up multiple years of experience to qualify for them. But the trend over the past several generations is toward greater job mobility. It is relatively rare for Gen X and Gen Y workers to have stayed with one employer for decades, as many of their parents may have done. Job hopping is often the best way to increase one's compensation, and the loyalty that used to be shown between employers/employees has largely dissipated.

Thus, many people's only realistic chance at a sabbatical is to do an unofficial one by taking some time off between jobs -- but this has its own problems. Since health insurance and many other benefits in the US are tied to employment, it can be extremely costly to not be constantly employed.
Show HN: Knowstory – API to turn unstructured text into structured data
Hey Hacker News! We’re excited to share Knowstory, an API to turn unstructured text and documents into structured data. As we’ve built various projects in the past, we learned that our users were actually trying to use our previous services to extract data from their text - so we thought let’s just build an API for this. Knowstory was developed out of a desire to provide a simple way for anyone to extract data from documents.

We're looking for thoughts from the community to guide our development so we’d love for you to try it on desktop or laptop (we’re still ironing out our mobile views). Your feedback is especially valuable to us so thank you for being an important piece of our journey!

If you would like to integrate this into your app feel free to reach out to me at pradhit@knowstory.io. I’m happy to give you a pricing discount and help you onboard.
Cutting into an artillery shell with a grinder gives me the hebegebees.
In this context, is the national "retirement age" just the age at which national social-security-type programs start paying out? And the connection to actually retiring (not working) is that (1) people are less likely to want to work if they have access to retirement income and (2) payouts are decreased if you're earning a lot of money?
@ModernMech, you can just address people here individually, and not refer to them as V developers or V community - that currently is already too broad and paints people that you do not know at all, with the same paint, be it bright or dark.

It is the same, as asking you to not talk about all Australians, all Chinese or all Bulgarians, when you mean the actions of specific people/individuals.

That is all I am asking for, and I think that is not difficult to understand.
I think part of the issue here is that a fair number of programmers work in shops where they have very limited agency. They are tasked with making the minimum defensible change to add a feature or fix a bug. They are not allowed to change the tests or suggest refactoring. So those things just don't occur.
Using the word "construct" isn't adding anything to the conversation. If we bioengineer a sentient human, would you feel OK torturing it because it's "just a construct"? If that's unethical to you, how about half meat and half silicon? How much silicon is too much silicon and makes torture OK?

> Most people will [privilege meat]

"A person is smart. People are dumb, panicky dangerous animals, and you know it". I agree that humans are likely to pass bad laws, because we are mostly just dumb, panicky dangerous animals in the end. That's different than asking an internet commentor why they're being so confident in their opinions though.
There are a lot of ways for good code to express bad abstractions. The abstraction could be inconsistent with other parts of the system, inconsistent with the concepts it is meant to represent, inconsistent with its own observable behavior, inherently complex or hard to reason about, inconvenient to actually use, poorly suited to whatever people actually use it for...

I've seen a lot of code that is perfectly clean and "well-organized" as code but organized into absolutely awful abstractions.

None of that goes against your core point, I just think that seeing the code and its abstractions separately is an important perspective for understanding code design.

On the flip side, it's also totally possible to have bad code but a good abstraction. Some of the best abstractions I've worked with have painful implementations, and it didn't impinge on the quality of the abstraction itself! Of course, the bad code made life a lot more painful for the people responsible for implementing and maintaining the abstraction, and I'm sure it required some real skill and experience to keep that from manifesting to users of the abstraction, but they managed it.
I always thought of Ruby as Perl++ more than anything. It's relatively easy to write, not always so easy to look at and refactor later. As to why Python has won, I think you nailed it, the library integrations and academic space has made it popular and useful there.

Ruby's popularity for what it was, was heavily tied to Rails. As that space progressed, a lot of people came to dislike it as much as anything, and maybe more. There are a lot of ways it didn't work so great and those warts made more and more avoid it in future projects.

That's my $.02. I started with JS as well, but in '96 and through classic ASP (JScript and VBScript) through VB6, .Net (and C#) then into/through Node.js etc. I also dabbled in PHP, Ruby and a handful of other tech along the way. Python feels like a massive gap in my knowledge base at times, I have a few books to read, but not much in terms of opportunity/need. And the time I've spent on Python, I feel like I'd rather spend that time leveling up in Rust.
Somebody is preparing their promo packet and needed to hit an OKR. Launching product on time is harder than just changing the meaning of “General Availability”.

Google is a wholly political organization now, everything can be explained by internal power plays. Don’t look for another source of logic.
> it still seems that more sweeping claims like "Microplastics are responsible for the Flynn Effect and the male infertility crisis" are awfully bold

You are making my original statements into a straw man argument. I didn't say they are fully responsible, but rather I think they are contributors.

I even asked in my original post what else could be contributing:

> I think microplastics along with forever chemicals/PFAS are two of the likely culprits and are probably fairly easy to deal with.
>
> I wonder what else could be contributing?

Lead does reduce IQ and increase crime. Here is a meta-analysis that tries to tease out how much lead was responsible for crime and homicide:

https://www.sciencedirect.com/science/article/pii/S016604622...

Banning lead gasoline was the right thing regardless. It was causing harm. It is hard at the time to know exactly how much.

You then wrote:

> You throw obesity in there too, and doesn't it seem like folks are trying to pin all of society's ills on a single issue?

I do think we are poisoning ourselves in probably a few different ways -- we have made so many novel chemicals without significant safety testing that a good chunk of them are probably harmful and can also likely build up over time. If we can continue to deal with these harmful chemicals that have clear links to negative health outcomes, we will be better off as a society.

The trick is to keep studying them and then act on those studies to mitigate the harms of those chemicals.

The world is complex and there is usually not a singular cause of everything. But that doesn't mean we should just throw our arms up and say, oh no, I can not do anything it is all just too complex or overwhelming. No, instead you just have to do, as Anna says in Frozen II, "the next right thing:"

https://youtu.be/kFkClV2gM-s?t=118
... the infrastructure is high voltage 3-phase, same as EU.

Also, stone tools are easier to replace :P
Why should RTO need data? That was the setup until 2020 and it worked. Especially for the leadership who have grown up in that requirement. Onus is on the pro-remote side to provide data that that works.

Sample size of 1 - at my company, remote sucks even if we tried to go all-in on fully remote. I simply cannot have trusted relationships with my colleagues since everything has to be writing or is possible being recorded when on video. In person, both parties can share candid thoughts in person without any fear of being recorded for ever.
Yep, we're all well aware of the origins of employer healthcare in the United States.

However, I don't want to confuse the etiology of employer healthcare and the social reproduction of employer healthcare as it exists today. In other words, just because a thing has an origin, doesn't mean that the original cause continues to exist nor can we avoid examining proximal causes.

I'm a bit confused what you meant by "it's not enshrined in law." I think we both agree that there doesn't exist a statement of law like "Employer healthcare is a benefit of virtuous employment." Rather, the motivating factors for the ACA compliance[1] are congruent in the minds of a contingent with the idea that a work ethic justifies rewards.

There are many such programs that are congruent with work ethic such as Earned Income Tax Credit(EITC)[2], unemployment benefit requirements(looking for work[3]), and FMLA requirements(work >12 months)[4].

I want to be transparent and stress that this is much more in line with a critical analysis of the US legal code and policy than a logical argument, and carries with it all of the nuance and assumptions that any critical legal analysis does.

1. "ACA, employers with 50 or more full-time employees (or the equivalent in part-time employees) must provide health insurance to 95% of their full-time employees or pay a penalty to the IRS." https://www.nolo.com/legal-encyclopedia/is-my-employer-requi...

2. "Encouraging work" https://obamawhitehouse.archives.gov/blog/2016/01/29/earned-...

3. https://www.usa.gov/unemployment-benefits

4. https://www.dol.gov/general/topic/benefits-leave/fmla
I never said don’t work
Have you considered eating the rich?
Yes. Black text on white background in an underlit room is like reading a lightbulb.
“No mention of openbsd on the internet is complete without a long thread about source control migration.” — tedu@
What Brewers Can Learn from Nike
> You should almost never try to expand abstractions in this manner

But somebody on your team /will/.

> you should feel eager to simply split apart the abstraction

Sure, but it's going to be a lot more work at this point than if we had avoided the mess in the first place.
This system is then inherently favouring breaking the law because you will never pay more than the damage you caused, and since there's a nonzero chance you will win there's always an edge for the rule-breaking side
Drugs that will be up first for Medicare price negotiation
I would use this as the way for company's command line tools to be provisioned to me as a team member. This means my tools can be separated from work tools
Largely this is resolved by US houses having a lot more circuits. My bathroom has a dedicated 20 amp (2.4 kW) circuit for the outlets and a separate 15 amp (1.8 kW) circuit for the lights. Every bedroom in my house has its own 15 amp breaker. The kitchen has 3 20 amp breakers for different wall outlets, a 15 amp breaker for the lights, then a 30 amp 240v (7.2 kW) breaker for the cooktop, and a 20 amp 240v (4.8 kW) breaker for the oven.

For the a typical US house the standard feed into the house is 200 amps at 240v. So 48kW of power coming in we just segment it down a lot more.
> virtually all conspiracy theories are still bunk as hell

Except all the ones that have and will continue to turn out to be true.
I was going to say that Microsoft appears to have chosen to address this at the library level with brilliantly optimized frozen and immutable variants of the collections, but you beat me to it.

It probably would have been easier and cleaner to implement some form of `restrict` and `const` semantics (or maybe move, like you mentioned) than to work as hard as they did to come up with a still sub-optimal solution, but the performance they’ve managed to eek out of the frozen and immutable variants is to be commended.
You too can probably get away with a $377 million settlement for most torts.
Solid: Crafting Software to Conquer Complexity
The idea of the post is based on the fact that this period would be covered by the same social security fund that covers retirements right now in most of social-democratic european systems, so you don't need to save for sabbatical the same way you don't need to save for retirement under these conditions.
Could I run a standard computer PSU of 220V split-phase?
Totally get your point about AWS having free-tier services and compute never being free, regardless of the stack. My point wasn't that BEAM offers free compute, but rather that its inherent features can sometimes make certain AWS services redundant. For instance, Elixir has built-in fault tolerance with its actor model and supervision trees. This means that even when a process fails, it gets rebooted automatically without messing up other processes—kind of like what you'd use Auto Scaling and backup services for on AWS.

Similarly, distributed Erlang allows Elixir to run across multiple nodes. This could cut down the need for extra AWS instances or orchestration layers like Elastic Beanstalk. And when it comes to deployments, Elixir's hot code swapping can simplify what might otherwise require rolling updates or blue-green deployments with Elastic Load Balancers in the AWS ecosystem.

On the concurrency front, Elixir is designed for handling a high number of users and tasks simultaneously, which might reduce your reliance on EC2 or Lambda. Phoenix, Elixir's web framework, even has real-time capabilities baked in, so you don't need extra services like AWS WebSockets for that.

Finally, Elixir's actor model can serve as an in-memory message queue, which could potentially negate the need for something like AWS's SQS. So, while you're still incurring compute costs, the need for additional AWS services could be lessened, thereby simplifying your architecture and perhaps lowering overall costs.
The book is Calculus by Janusz for those wondering.
You should work on building up savings then.
Chainalysis Investigations Lead Is ‘Unaware’ of Scientific Evidence It Works
Wouldn't cost savings also translate to simpler models? I anticipate the process of distilling knowledge to simpler models will also become much cheaper and non-technical