skysight-inc/HackerNews huggingface dataset:
I'm a devops engineer and so am plenty comfortable building APIs, but I use next.js for front-end stuff, effectively as a more powerful "create-react-app". However, I dislike having to caution-tape over the server-side of nextjs, and I dislike having to build my own https wrapper every time etc.

Is there a good / popular front-end focused nextjs alternative that doesn't make it a massive pain in the butt to crank out a react app? Am I doomed to make my own create-react-app wrapper?
Yes, its something similar. We made this as a coming soon page for our upcoming app, that helps to reduce stress and loneliness with 5 minute social activities provided by AI.
If I'm understanding it correctly, the assertion is that Apple feigned interest in collaboration as a pretext to put themselves in a position to hire away employees. If that's true, then it's certainly dishonest even if it isn't illegal. It could also be concerning if large companies can smother smaller competitors in the cradle.
Dang it! I hate re-reading after the time for editing is over and finding a stupid mistake.

The Python is correct, but the comment is not. The formula for the second derivative should be, of course:

# d²y / dx²
And colonoscopies miss 60% of the precancerous polyps. There's no such thing as a guarantee in healthcare.

> The skill of a doctor doing a colonoscopy is often measured by their adenoma detection rate — how often they find a precancerous polyp. American doctors find them 40% of the time.
Every so often I stumble across the Wikipedia page of an author from the 19th or 20th century who was _hugely_ successful in their time, writing many bestselling books, and yet is almost totally forgotten now. They must have justifiably believed they had attained some kind of artistic immortality, yet it turned out not to be so (at least, probably not to the degree they expected — they do at least merit a Wikipedia entry, which is more than most of us will ever get).
I don’t understand why they had to go with Tesla and Polestar. It’s not really the issue with EV ambition but because Teslas are expensive to fix. Plenty of other EVs out there.
I think there is a lot of fantasy thinking that ancient times didn’t use money. Trade is evident from the earliest times as proven through goods at burial sites that originated thousands of miles away. Trade necessitated commoditized assets as intermediary value stores, and common ones included salt and furs in addition to hard metal coins and commoditized metal objects like swords.

Social relationships are still important the higher you go in finance - it’s much easier to get a $100 million loan for a new building with a strong relationship with a banker than as a stranger, regardless of collateral.

I think a pre-commercial time where people didn’t care about money is a fiction.
Hey thanks for the awesome comment! I just made a new account using google oauth with a spare email I had, and seems like it is working perfectly fine. Five other people have managed to create an account using google as well since the post. I would love to know what went wrong but I'm unsure how to help there. Maybe try again ? In any case sorry for the inconvenience.
There is a rich literature in bioinformatics on sequence homology search, and there are many existing libraries that scale to billions on base pairs. I wonder why they reinvented the wheel
I'm probably overthinking this, but the article makes me think about the infamous 10x programmer. If, as seems reasonable, the ability to program successfully depends on a number of factors (raw brain power, spacial reasoning, education, ability to concentrate for long periods, etc) and these factors follow a similar gaussian distribution, then 10x doesn't really seem that out of line for the best vs average programmers.
I’ve had a couple friends this happened with. One of them however would laugh SO hard he couldn’t breathe!
Agreed about Cupertino but San Francisco is very walkable!
We all compare ourselves upwards. Related, you might wonder why a strong cyclist bothers buying a $10k bike. After all, they'd be faster than most people on even the cheapest bike! But they start riding with others, and their peers are faster than them. Their peers have nicer bikes which they come to appreciate / desire. They spend lots of time USING the bicycle, so the "investment" makes more sense. And so on.
Miniaturize it and make it into a small, waterproof, rugged device that I can take backpacking with me and I'd pay a handsome sum.

(I don't want a cell phone app, my cell phone remains off while hiking)
Best practice is the practice that works the best. That isn't groupthink. If it works, it works, regardless of whether a single person or a group is doing it. Groupthink would be whatever the group thinks is best, which isn't necessarily what actually works well at all.

The reason why running an app on a VPS is not best practice isn't that the VPS can't handle it; it's not a question of scale. The issue is that there are many different problems with running an app on a VPS, and it is much better to avoid those problems by not using a VPS at all, rather than to spend a lot of time trying to mitigate those problems on the VPS. If there is an alternative that is lower cost than the cost of mitigating the issues on the VPS, then that's the better solution.

It turns out that there are solutions like that, among them Heroku/DigitalOcean App Platform, DigitalOcean K8s/AWS EKS/GCloud GKE, Fly.io/AWS Fargate, Google Cloud Run/AWS App Runner, AWS Lambda/Google Cloud Functions, and many more. Almost all of these are better than running your own VPS, because they are designed to remove the problems you will inevitably run into with your own VPS.

Some people buy cheap things and replace them frequently. Some people invest in better quality that lasts longer. If you'd rather patch the holes in things rather than simply last longer, a VPS may be the solution you want. But it's certainly not the best solution.
Money-as-knots-in-a-rope sounds closer to the modern money-as-bits-on-a-plate than does money-as-metal-disks.
Steve Jobs was a product manager, the best in class.
I hadn't considered that not everyone would agree with what I said; thanks for telling me what you think.
>I have started looking at Goodreads ratings as a good proxy for well written books

Based on my experience looking at Goodreads reviews, I think you'd have just as much luck with a random number generator.
Could you elaborate on what Brazil is in this context?
I don’t like it much either. I have friends who don’t think about such things. They tend to be happier 95% of the time. Not as useful when everything catches on fire though.
The thing about PMs. They fulfill a very specific need, and that need is hard to quantify, but I can tell you that without a good PM everything falls apart.

Here's a list of what they tend to do:

- gather information from users on what is/isn't working for them

- gather information from executives about what needs to be done to keep the company working

- gather information from industry leaders who may or may not be part of the company about where the industry is going

- work with design

- take all 4 previous points and distill them into what actually needs to be built for a needed feature

- work with engineering to figure out what is practical, vs not, for building, and how long approximately it will take

- work with engineers / higher ups to remove features that take time but don't add as much value.

- work with engineers to ensure estimation and team velocity is more or less predictable

I've probably already described a 1 and 1/2 jobs. Now if you take product away, each of the above gets distributed among the engineering team, and not everyone in that team is good at it. And even if they get to a good homeostasis, one person leaves and now there's a non-obvious gap that we're not interviewing for.
True. From which country are you from? In our country, the government makes rule to not make construction workers do their job between certain times, when the sun's heat is so high.
Unions are like government. In both, the most corrupt and power hungry individuals will see a way to get a ton of money from the masses by grandstanding their way to the top, and once there will move on to the next easy cash: selling out their ability to place rules on the people that pay them to the highest bidders.

I once went to a bar in Portland that had a ~20% discount if you showed them your union card when asked. If you said you didn't have a union, they'd respond: "no, you don't have a union... yet!" with a big grin on their face. Well intentioned, I'm sure. But overhearing the sheer volume of bike shedding that went on in conversations there regarding matters entirely adjacent to the folks' actual work, I can't say I want any part of it.
https://www.pordata.pt/db/portugal/ambiente+de+consulta/tabe...

Actually, for 2021, earning 40k€ per year puts you in the top 10%. 4 in 5 families earn less than 27k€. Less than 5000 families earn more than 250k€. Top 1% is 100k€.

This is for a population of about 10 million.
Good paper from the progenitor of the blockchain, Nick Szabo, positing that the first moneys emerged up to 75,000 years ago and possibly enabled Homo sapiens sapiens to supersede Neanderthals:

https://www.fon.hum.uva.nl/rob/Courses/InformationInSpeech/C...
I loved Drupal back in the day, but at some point (D8+, part of it moving to Symfony), it became too difficult to manage and for me personally to keep up with.

But I believe that, in the early days, Drupal made excellent foundational design choices as a framework, and if you used it's APIs in your custom module development, then, generally speaking, you would have a secure website.

But now, D7 is approaching EOL, and I absolutely don't want to migrate to the latest flavor. D7 has been rock solid for a decade, and I have no desire to chase the latest fad.

I wish that there were a stable, monolithic solution that is simpler to setup (as in including everything, including database, webserver, SSL certs, etc.) that just worked and was extendable and overridable programmatically, in the same way that Drupal was.

Modern web stacks have become a bucket of Lego pieces that seems ok if you are an expert in everything and know how to put everything together exactly. The problem is, most people aren't experts in form handling, login and authentication, media handling, caching, etc.
Is there a colorblind mode? Red green is the most common form of colorblindness.
Sieve (YC W22), a video/audio AI cloud, is hiring AI engineers
Part of what makes this kind of thing difficult to really fathom is the time scales involved - e.coli can reproduce once every 20min or so, yeast can do so every 2 hours or so. 12 replications a day, 4380 replications per year, repeated over a billion years. It all seems phenomenally unlikely, but the combination of an unfathomable number of repetitions and even a small evolutionary thumb on the scale can take you an enormous distance.
Some early fridges ran on ammonia as the refrigerant. Didn’t survive scaling up to mass production. Neither has nuclear.
A plug for Steve Rinella's excellent book, "American Buffalo: In Search of a Lost Icon".[0]

He recounts his grueling trip in the Copper River Basin in Alaska on a hunt for a bison, and every other chapter continues a parallel telling of the history of the species in North America, particularly the archaeological evidence of prehistoric hunting of the animal, from large kill sites to fascinating sites like the Mesa site in northern Alaska[1] linking arctic cultures to Paleoindians in midcontinent.

It's a really enjoyable book, and he narrates the audio book.

[0] https://www.amazon.com/American-Buffalo-Search-Lost-Icon/dp/...

[1] https://www.blm.gov/programs/cultural-heritage-and-paleontol...
Moderna is in trials with an HIV vaccine based on mRNA tech.

https://pubmed.ncbi.nlm.nih.gov/36454825/

https://www.clinicaltrials.gov/study/NCT05854381
I really struggle with this sentiment because I often agree with it, specifically at large companies.

At Google product managers became the worst aspect of the entire company. They spent their time arbitraging credit, cutting off communications between builders and executives, and generally appearing for a while, not taking ownership, then leaving after they fucked up the roadmap so badly they couldn’t fix it.

They became the worst kind of leech on the company.

But then in starting my own company, PMs who need to own, execute, and deliver on a triads goals has become invaluable. It shortens communication pathways and distributes responsibility.

So I dunno I’m at a loss.
That’s funny, because as someone who just switched from Android to iPhone i feel the opposite. Android nails some basics that iOS really misses on, like notification handling and gestures.
Or they’re just less affected by the public’s perception of their promiscuity
Laravel + Hotwire if working alone or with a small team. Laravel + Inertia if working on a large team or with dedicated backend and frontend teams.
Yeah. It's definitely a simple procedure... To the doctors who do it all day every single day for decades. To the patient who's going to be examined, it's extremely invasive.
Such standards do exist: https://slsa.dev/spec/v1.0/provenance
Yeah, if memory serves they are contemporaries which is why it’s upsetting that Monica is dating him. He’s literally old enough to be her father.
This comment is so eye-poppingly fatuous that I don't even know where to begin. The parent commenter is speaking about how people (a group which includes women) have the right to choose who they want to marry, which includes the right to marry nobody at all. You appear to be using the declaration of human rights to imply that the desire of one person to marry another somehow overrides the prior right, which is utter nonsense. Please refrain from commenting if you can't provide a more cogent argument than ChatGPT.
Selecting for intelligence/education/creativity is objectifying? Boy that’s a new one.
I lolled at that too a little bit, but then saddened because I think it's the result now of 10+ years of tech industry "best practices":

1. Ruthless data-driven decision making for products (not allowed to use any subjective judgment, gotta go only on metrics). And assume that the data is always painting a clear picture, not one that is easily subject to all the pitfalls known in statistics, and goes through subjective interpretation (especially impacted by confirmation bias). Don't use your intuition or judgment to question the validity of the metrics and try to figure out a better way to measure!

2. Dumb down the product, aka remove features. "simplify" is the euphemism we all use now, even though it doesn't always simplify things (sometimes it does, sometimes it doesn't).

3. Make changes to get promoted. Removed a feature? Great, promotion! Added a new feature people wanted? Promotion! (never mind it was the same feature in both cases)
Shaun Lintern is an experienced health system journalist. This piece, written by him and Danny Fortson, is a comprehensive take down of Babylon.

Lots of people had serious concerns about Babylon Health - mostly around obviously false claims of accuracy - for years, and it was baffling to see them keep getting money.

And the real story is pretty grim - copious amounts of corruption and deception, and a system not holding them to account.

It's notable that a key feature of their model - quick access GP appointments to push patients to private secondary care (where the people providing the GP appointments and the people providing the hospital care are in the same company) did not work, and could not work because the finances didn't make any sense even with the corruption and deception.

There are often discussions around NHS models of care, and people will suggest moving to a mix of public and private, or private but non profit insurance models. The simple fact is the model doesn't matter: healthcare doesn't work unless you fund it.
I'm well aware! It's actually Microsoft that originally pushed for that change, CA/B Forum just implemented it IIRC.

Apple's PKI:

1. Has a much easier verification process.

2. Is a lot cheaper, dev program membership is ~$100/yr and they throw in a couple of DTS incidents as well.

3. A big one: Apple's PKI issues certificates with long term stable identifiers (team IDs). CA/B PKI specifies all kinds of random details that CAs have to follow but the subject name isn't one of those, so systems that use the subject name as a key (which Windows does in various places) will immediately forget who you are if you change to a competing CA, or change your company name, or it relocates its HQ, or if you change OV<->EV, or if they just change their policies again for no real reason. This problem makes CA/B certificates largely useless in practice because you can't associate anything with the verified identity. They know this problem exists because I have raised it with them specifically, and they don't care.

5. The root and intermediates are more stable (experience odd expiration/cross signing issues less or not at all).

6. Apple hardware can protect private keys using the secure element that comes with the device, so it can have equivalent security without needing the USB token. USB tokens have a bunch of issues. Also Apple's OS can limit those hardware protected keys to specific bits of software too, so you can ensure that only your code signing tool or build process can access the key. USB dongles can't do this, anything that can talk USB and get your credential can use it.

So those are some specific technical justifications for you.
People put in Trabant orders when their grand children were born. As an 18th birthday gift.

Theres a German entertainer that made TV skit where he tracked down some of these people (probably some time in the late 90s or early 2000s and "delivered" their new Trabant on (hidden) camera. Quite fun.
When I was at Apple (during the interregnum between Jobs’ reigns) we had people called product managers, but yeah they were mostly about getting the product to market and interacting with the market.

We had project managers who nominally controlled product design decisions. We had test managers in a separate testing directorate (I was one of those).

My experience was that the three managers worked together to define the product, with the product manager trying to represent the market, the project manager representing engineering, and test manager asking pointed questions.
> I just don't really fully comprehend why so many people care so much about the clock, beating other people, etc.

If the only reason for progression you can think of is to beat other people, and you have no desire to beat other people, how did you progress to running marathon distances while other people haven't? Presumably the was a time when you couldn't run a complete marathon, no?
Agree. But we have to keep this limitation in mind. There could be situations where you have to carry a drone or batteries from place to place for example.
Replying to scarface, who has no reply button... It would help to know that profiles are not likely to be a Chinese scammer, and it would help in that the app wouldn't be actively _hiding_ profiles of people that have expressed an interest you behind a "gold-level" function. Because that's what Tinder does: it finds the short list of people that might be interested in you, and then hides them behind a pay wall, occasionally trickling one out (and dare I speculate, the one that is least likely to lead to a relationship).

If anything, Tinder is the precise opposite of a dating app.
Counterexample, roll a dice. That gives you a randomly generated number. You can then test whether said random number is prime by enumeration.
I think the hiring away is a valuable tool for individual contributors. If you know how to do something that your current employer doesn't value as much as another employer, you should be free to go elsewhere. It's a check and balance on your compensation; if your current employer can't make money from your ideas and give you a reasonable cut, and someone else can, then they kind of deserve what they get.

In this case, Apple didn't want to buy an entire company just to get an algorithm. So, they found the person that came up with the algorithm and offered them more money to come up with a similar algorithm. Not illegal.

Apple has had this happen to them. They had Safari engineers hired away by Google to work on Chrome. They blocked this using back channels and got sued:

https://appleinsider.com/articles/14/03/24/steve-jobs-threat...

Basically, Apple wanted to under-compensate software engineers. This is bad for our field in general. It's important that ICs comply with any contracts and applicable law as they are poached, but backroom declarations of "war" or "you can't hire any of my employees unless you buy the entire company" is total horseshit that keeps software engineering compensation low.
Statement detected on web platform 'HackerNews': Autocorrelation in progress...
Identity found: Subject #ThrowAway1922A

Warning: Potential dissident behavior. Monitoring level upgraded to TIER-3.
Recommendation: Dispatch surveillance drones for real-time observation.
I agree, however, time is zero sum. In school, it's all a numbers game to A) pass and B) pass ahead of your peers. This is the similar to the work environment A) not get fired and B) appear better than your coworkers.

So while in an ideal situation, students would be learning the context of a historical event, dive deeper in a topic, to create a better, more informed knowledge, what's the point? Does knowing more about Plato help with Java 101 by a statistically significant margin?
Great rant. Now explain why it is different with taxes.
Yep, a common pitfall is to not understand how product managers are supposed to do, and thus they just do project management, which often has neutral or negative value.
There's a lot of anthropological and archaeological evidence to the contrary. People indeed had trade and exchanges in ancient times, but these did not aalways necessitate a formalized system of money as we understand it today. The early forms of trade were often based on complex systems of credit and debt that were deeply intertwined with social relationships and trust within communities. David Graeber's work, "Debt: the first 5000 years," highlights that for more than 5,000 years before the invention of coins, humans extensively used such credit systems to buy and sell goods, long before the existence of coins or cash.

While it is true that trade is evident from ancient times, with goods found at burial sites that originated thousands of miles away, this does not automatically imply that all trade was facilitated by a commoditized asset serving as a universal medium of exchange. In many cases, goods like salt, furs, and metal objects were indeed used in trade, but they were part of a broader system of barter and reciprocal exchange, which could function effectively without a standardized form of money.

Regarding the role of social relationships in finance, while it's accurate that relationships remain crucial, especially for large transactions in modern times, this does not discount the fact that in the past, community trust and social bonds were often the primary means of securing credit, not collateral or commoditized money. This is evident in how competitive markets and the scarcity of trust can affect transactions, as Graeber notes through an anecdote where mutual aid within a community was a given, not a transaction requiring formal repayment.

The idea of a pre-commercial time where 'people didn't care about money' may indeed be fictional, but it's more nuanced than simply saying they used money in the way we do now. They cared about value and exchange, but these were frequently managed through social mechanisms rather than through impersonal, commoditized money. It's essential to understand that the concept of money has evolved and that early forms of trade and credit were valid economic systems in their own right, even if they don't match the monetary systems we are familiar with today.