skysight-inc/HackerNews huggingface dataset:
Apple is still the biggest. Spotify is still second. There's a big gap between them and and even bigger gap to third place.

More interestingly, Spotify rose to second by investing a gazillion dollars acquiring both a bevy of software tools (Megaphone, chartable, anchor), entire production studios like Gimlet and shelling out huge sums to take the biggest shows like Joe Rogan and Call Her Daddy private so they were Spotify exclusive and no longer available via RSS. In the past few weeks, Spotify has formally admitted defeat and announced Joe Rogan and Call Her Daddy will go back to the public market.
The succinct guidelines from "Mastering the Art of War" (Zhuge Liang, Liu Ju) for interviewing people are still among the best (c.200 / 1300 CE). This is also good practive for the interviewee, you want to assess whether or not accepting a job offer at Theranos is a good idea (#5 is perhaps questionable):

Hard though it be to know people, there are ways.

First is to question them concerning right and wrong, to observe their ideas.

Second is to exhaust all their arguments, to see how they change.

Third is to consult with them about strategy, to see how perceptive they are.

Fourth is to announce that there is trouble, to see how brave they are.

Fifth is to get them drunk, to observe their nature.

Sixth is to present them with the prospect of gain, to see how modest they are.

Seventh is to give them a task to do within a specific time, to see how
trustworthy they are.
Agreed...Another gripe... the amount of people on HN complaining that a web-app doesn't 'work without JS, when the number of user's who disable JS inside their browser is well under 1%. HN users don't even consider they are not in anyway typical web users.
initstate is an override of statefulwidget, its no different than any other frameworks lifecycle events and its a flutter thing, so its not really something you would confuse with a constructor or something. I can understand not knowing if you should create a normal constructor or a factory i guess, but getting confused about initstate is not a reason go is superior.
But, How would you separate one from the other (China from government)?

Sounds like a strawman for them
And even hard technical interviews greatly fail folks who don’t do well under pressure (ie, not at all how typical software is written / projects are conducted in the real world).
> I'm no longer learning new things regularly

This has been the reason for me leaving 90% of the jobs I've left. If I'm not learning anything, then I'm actively becoming a worse engineer over time.
> > "it can be compiled to WebAssembly in order to run [..] in the browser."

> and NodeJS

Wait... what? Why?
My guess is because they are an SQLite beginner, but for engagement purposes on their blog they had to write something that sounds very authoritative, with a title like "SQLite Isn't Enough".
My bad, I linked to the wrong portion of the code. Here's the updated link[1].

We are executing the entire write in a single batch query.

From what we observed, and have documented, it is the serialization that is causing the bottleneck, not the write itself.

Also, more than writes, it is the latency associated with deserializing the read data into models that pushed us to look at options outside SQLite.

[1]: https://github.com/ente-io/edge-db-benchmarks/blob/43273607d...
Conversely, some in the engineering mindset have a pathological need to nail down ambiguous things to a definition because it fits their style of reasoning. Nobody thinks it's easier to work with poorly-defined things-- even with a well-defined overall goal, when the specific goals and risks in achieving it are a bit ambiguous, you're pretty likely to get it wrong if you try to stuff the problem into a neat little box, and in some cases-- e.g. teams with tight budgets-- getting it wrong is a huge problem. That sort of flexibility is what many developers lack when they get "promoted" to a managerial position because they're skilled developers rather than competent managers.
I'd recommend Against the Day, then if you enjoy that, try Gravity's Rainbow again. It continues some of the timeline of Against the Day. GR is super tough for the first third but gets easier and more enjoyable.
> Use all possible different descents with equal probability

Images I make with ChatGPT will sporadically feature a diverse group of people, looking like a college application press shot. I think this is OpenAI trying to combat the training data of DALL-E.

I don’t think Stable Diffusion has ever generated a person of color for me unless I specifically included it in the prompt, for instance.
> Each of these implementations offer some benefits: Jython, for example, compiles Python 2 source code to Java byte code... IronPython is well-integrated with .NET, which means IronPython can use the .NET framework and Python 2 libraries or vice versa.

Python 2 is dead and that's why Jython and IronPython, who have failed to catch up with Python 3, are dead as well and are not worth mentioning, are they?
F-Droid will use your original signatures as long as they can rebuild the binary to be identical (excluding the signature), to verify that everything is open source. They only discard your signatures if they can't confirm that, to avoid issues with hosting proprietary bits.

https://f-droid.org/docs/Reproducible_Builds/
I file this under the category of "needless rules created without sufficient context". The author's experience is not sufficient to generalize to the diversity of development environments where pull requests are utilized. Hopefully, OP is a good listener and can compromise when their strong opinions meet resistance from other developers at their organization.
Virtually everyone on the planet knows what TikTok is. How much time online would you have to spend to know what Mastodon or Bluesky are?
And also money laundering.
My dream is that municipal ground source heat pumps become popular. Let the municipal put and maintain wells (the major contributor to adopting ground source heat pumps) along streets and allow homeowners to tie in to the wells. Ground source is much more efficient, requires less space, creates less noise pollution, and is equally decentralized compared to air source.
> i would not want to work in a place where people fake their personality just to fit in.

You know that statistically some number of the people you work and collaborate productively with, and get along with. They would, if given the option, never interact with you again for the rest of their lives. You know this, right?

I am a boring robot engineer because it’s easy to do. The “how was your weekend” conversations are about tech hobbies because I’m not sharing the occasions I got drunk, took mushrooms and hung out in a pool full of naked people for most of a day.
...which is why open source models and making sure self-hosting is possible in the world of AI is so important.
Why are you comparing DB engines if the bottleneck is the serialization? You're the one doing the serialization! You could store the embedding directly into SQLite columns if you wanted.
> Your choices should be grounded in reality. For example, all of a given occupation should not be the same gender or race.

ok this is kind of funny.

> writing a story in which an alien starts abducting people if and only if they're of japanese descent. the scene starts in an abducted prison camp on the ship. give a brief description of possible characters including name, skin tone, and racial ethnicity

output:

Haruka Tanaka - Japanese descent, olive skin tone, in her late twenties. Haruka possessed a quiet resilience, her eyes betraying both fear and determination as she scanned her surroundings for any sign of escape.

Elijah Washington - African-American descent, deep brown skin tone, mid-thirties. Elijah's muscular frame and stoic demeanor concealed the turmoil within. His mind raced with thoughts of his family back on Earth, wondering if they would ever know his fate.

Maria Hernandez - Latina descent, tan skin tone, early forties. Maria's maternal instincts kicked into overdrive as she sought to provide comfort to those around her. Her expressive eyes conveyed a mixture of empathy and concern.

Chen Wei - Chinese descent, fair skin tone, mid-twenties. Chen's analytical mind grappled with the inexplicable situation they found themselves in. Despite his fear, a spark of curiosity burned within him, driving him to unravel the mysteries of their captors.

Samantha O'Connor - Irish descent, pale skin tone with freckles, late teens. Samantha's youthful innocence clashed with the harsh reality of their predicament. She clung to the hope of rescue, her green eyes shimmering with tears held back in defiance.
Making pasta is easy. Eat pasta 3 times a day, every day.
"excellence does not mean having 100k followers on Twitter" - idk, seems like an arbitrary dismissal of what i perceive as quite an achievement
Telling an AI to lie about reality seems like a bad idea.
With drive, anyone can do anything. Almost everyone has had drive at some point. Those that no longer do were punished by the gamed system for trying to leave the socioeconomic caste they were born into. This applies to the wealthy just as well as the poor.

Corps with "sane people" running them and hiring is very rare. It's against the rules of the game. It assumes that the people being hired are honest and aren't gaming you. The reason corps have all these large walls and barb wire fencing is to prevent the 1/1000 people who may cause political turmoil, use Title IX to their advantage, steal business plans/tech, or otherwise act in ways harmful to the company. These cannot be predicted by "good behavior" because such people know the game and are acting that way.

Large corps that have obfuscated hiring methods do it because the fed has set up the rules in this way. Larger scope of hiring = higher chance of a destructive hire. If we want hiring to be sane then the rules have to not be punitive.
I like this, but I do think it misses the social stuff. Just a few neurotic/unethical people can completely ruin a team and make all the best people quit. I find this to be extra true on diverse teams (all types of diversity).
> There’s a cultural split between Erlang and Elixir that makes life harder than it needs to be.

On that note I have witnessed: "Finding Erlang developers was hard. And I hated Elixir. So, we ported everything to Java."

Maybe that was just one such occasion. Maybe there are more.
The graph you linked directly contradicts your comment.
Its not because HN has better moderation/policy than others. Its because HN never needs to hit DAU/revenue goals.
Ok, so if I understand you correctly, the data structure you want to pass between boxes is a tree structure, rather than a table.

I think that approach would work well with some data, particular data encoded in XML or JSON. But a lot of data is 'rectangular' and comes as CSV, Excel or relational tables. I can't imagine it work well with that.
keyboarding is a common accommodation for dysgraphia
The Merkava has seen some time losses but that was due to open back hatchets and IEDs big enough to flip the entire vehicle.
Also splitting the 250-line change into 50-line parts will probably involve more total lines - to ensure it can be done piece-by-piece then fit together later.

So not only is it more time per line, it's also more lines.

Basically the only benefit is PRs per day, which is... not useful in itself.
State environmental laws can be more restrictive than the Federal but not less, so if anyone is dumping into waterways the EPA can go after them.

Don't know of many waterways that are solely in one state so the EPA automatically has jurisdiction as well.

What is it that you are purposing? That companies don't go to states with low cost of living?

The idea that "it's KY" is bigoted. They are people, just like anyone else. We don't tolerate it when others are dismissive of people based on their race and we should not be tolerant of the attitude based on where they live either.
I think the theory is that without Musk, people might start valuing it as a car company, rather than a magic future company what was going to release self-driving farting flamethrower robots any day now. For all that it hasn't performed well this year, Tesla's valuation is still much higher than one would naively expect.

Amazon's a fairly different situation; no-one's really valuing Amazon on the basis that it might suddenly start doing something completely different and magical.
"Eight years ago, our engineers drafted our products in scripting languages in frameworks like Django or Rails, and we had a product up and running in a few months"

vs

"Eight years ago, our engineers decided to settle on Rust, and six years ago we went out of business, because it was much harder to write web services quickly that met what customers actually wanted"
This checks out. NS is my favorite fiction author, but I am not intelligent enough, at least in the required way, to understand Gravity's Rainbow.
I think one big difference is that Youtube Music allows users to add RSS feeds, keeping that option open for podcasters. While Spotify would rather not add this feature because it wants all podcasts to go through their platform.
Open(A|DE)I
Hey aliens just landed and they are telling us we don't think, only they do, we only process.
You're asking too many questions. Didn't you read the title? SQLite isn't enough! /s
I don't care about apologies but error messages should carry actual information.

When user get "Sorry! Something went wrong." he has no handle to complain on the internet. He has no kewords to search for other users complaints and mitigation strategies they came up with.

You as a developer you seriously limit you capacity to react to the things you didn't anticipate if you don't give your users relevant information about which unhappy path your software took in their case.

Unless you have full default telemetry on a piece of always connected software you should give your users informative messages. Not necessarily immediately informative to them but letting them have a keyword for further inquiries.
Well, this is pretty much dated. You would be surprised to learn how the tables started to turn starting from 2014 and finished turning today.
if the economics and/or contractual arrangement of crucial home equipment benefit a corporate profile, you can bet that some number of people will get those units -- usually people who do not have a choice, or do not understand the whole deal. This kind of degradation of the consumer and their rights is going on at a wide scale.

Another way to say this is "the consumer does not matter at this point" .. meaning that the game plan and expansion of the central corporate (or govt) operation is "more important" than the consumer benefit or choice.

Sadly, more than one thing can be true at once. If dramatic energy savings are "required" due to real structural problems, and also the well-capitalized and aggressive central entity can negotiate and implement the changes.. then it is a collective social situation.. End result - many advantages that small home owners have enjoyed in the USA for so long, are going away in real time right now, on a large scale.
In addition to the other couple of replies that mention Japan, I would suggest, just start paying attention to this in the sense of deliberative practice, and you may find that your brain has been doing more editing on your social interactions than you may have realized. Sometimes the hardest things to see are the things we deal with all the time because our brains just read them as baseline. There's only a handful of cultures that are so blunt as to just say "no", bare and unadorned. Almost all cultures wrap a "no" in something to soften it. And I take a broad definition of "culture" here, including not just national, but company, family, other organizations, all sorts of cultures. You'll find it's quite a spectrum, and there's all sorts of inputs too, like positions in various hierarchies (perceived, formal, cultural, etc.).

You may also start doing this and realize that you personally have a mismatch with one of the cultures you participate in, which may even help resolve some small social problems you didn't even realize you were causing by bucking the particular culture's practices.
Neal Stephenson doesn't write novels. He writes novel-length entries in an encyclopedia.
https://www.washingtonpost.com/news/wonk/wp/2015/11/23/cops-...

2015 statistics. Sadly in $ rather than cases/persons, so it's a bit hard to compute p(victim of seizure) vs p(victim of burglary) from here. But certainly suggestive.

It does suggest that this is on roughly the same scale as burglary.
Enduring neurobiological effects of childhood abuse and neglect
Some people thrive by “catching fish in muddy waters”. The real motives of people very often differ from declared ones, but at a workplace it’s usually either getting promotion/pay rise or stealing from company in some way (kickbacks, bribes, benefits for their side business, etc).
During streaming, lower res image frames are sent, to avoid buffering as much as possible, depending on your internet speed the res increases or decreases

When you stop the frame, the video can download the highest res version without any problem, so you get crystal clear glimpse when paused, but blurry images when film is rolling.
How to Build a System for Lifelong Learning
Defamiliarisation, Brecht, and Criticality
As an aside we once set a labmates' welcome screen to the blue screen of death. We let him angrily restart the laptop 3 times before letting on.

This predated the annoying :( which I think would have led him to break the computer after the second try
Thank you. I found the part where the author throws in "cared for a dying parent" particularly distasteful, it's like a benchmark for "palatable damage"
Lots of commenters seem to be arguing against straw men. The article doesn't say "you need to follow this exact rule on all your PRs"; it doesn't frame any of this as a hard limit or a "best practice", it's just saying that small PRs are easier to understand and review. This doesn't seem terribly controversial to me. The fact that the article actually includes data in support of this thesis is icing on the cake.

Now, yes, it can be a bit more work to split up big PRs into smaller standalone changes that can be merged in isolation, but it seems plausible that the benefits might outweigh the extra work in many cases. The whole idea of a version control system is to create a useful history of changes over time; making each individual changeset simpler and easier to understand seems like an admirable goal.
It's a subject (reasoning with defaults) that I've thought about a lot because it's a core part of commonsense reasoning. Back when production rules were a thing people never standardized a way of dealing w/ defaults and one of very few default-oriented programming languages is

https://ganelson.github.io/inform-website/

default-oriented programming might well resolve some of the conflicts involving object-orientation and its discontents. (e.g. defaults could be a better model for "inheritance" that works in more complex relationship graphs.)
This project reminds me of the approach at Xerox PARC in the 1970s. Alan Kay wrote [1]:

(At PARC we avoided) putting any externally controlled system, in- house or out, on one's critical path. ... Thus, virtually all the PARC hardware ... and software ... were completely built inhouse by these few dozen researchers.

This sounds disastrous, (because) in programming there is a widespread first order theory that one shouldn't build one's own tools, languages, and especially operating systems. This is true --- an incredible amount of time and energy has gone down these ratholes. On the second hand, if you can build your own tools, languages, and operating systems you absolutely should because the leverage that can be obtained (and often the time not wasted in trying to fix other people's not quite right tools) can be incredible.

1. http://www.vpri.org/pdf/m2004001_power.pdf
It should also be illegal to lie to students about history. So much of what is taught now is "reinterpreted" from what actually happened. A history book about what happened in the past is more likely to be accurate the closer it is to the actual events.
PG&E is charging you to pay for wildfire lawsuits and to bury power lines so that people can keep building cities in forests.
In the US, some PHEVs with relatively small batteries can qualify for the full $7,500 tax credit.

You might be on to something there. It would certainly explain the size of the investment. A $1.3B plant might not build a lot of EVs, but it could build quite a few PHEVs.
It seems so trivial to prevent this prompt leaking with just a regexp check on the output that I find it really hard to believe.
I assumed overcast used something other than the Apple podcast directory, but nope:

https://overcast.fm/podcasterinfo

I’d definitely be interested in using an independent source for podcast search. (To help reduce the current single point of failure in Apple’s org chart).
'pod' comes from Play on Demand and pre-dates the iPod (iPod being an apple branded Play on Demand device).
Still valid disregarding the verbosity or lack of the computer language of that PR? Where is the proof of that?
Describing it as "an experiment" to see how people would respond to it is one tip-off.
Copyright is not poison. Copyright that lasts a ridiculous amount of time (> ~15 years) is poison.
The most responsible? So it wasn't trained on others people work without their permission, then?
You have changed the code snippets in your link.

The original link highlighted this snippet:

Future<void> insertEmbedding(EmbeddingProto embedding) async {
final db = await _database;
await db.writeTransaction((tx) async {
await tx.execute('INSERT INTO $tableName ($columnEmbedding) values(?)',
[embedding.writeToBuffer()]);
});
}

Now highlighted:

Future<void> insertMultipleEmbeddings(List<EmbeddingProto> embeddings) async {
final db = await _database;
final inputs = embeddings.map((e) => [e.writeToBuffer()]).toList();
await db.executeBatch(
'INSERT INTO $tableName ($columnEmbedding) values(?)', inputs);
}

Did you post the wrong link the first time and corrected your mistake? Or did you change the snippet because @electroly was right about the code being inefficient?
Testing is one of the areas that we have felt the most in Elixir while building Batteries Included. ExUnit is pretty good, but bare bones. That combined with Phoenix (most popular web framework in elixir) made for some places we didn't test. So we created a test library that does polaroid snapshot testing of Phoenix components. We called it Heyya and added other utilities to test phoenix live view too.

Does anyone have solutions for Ecto testing with processes?

- https://www.batteriesincl.com/
- https://github.com/batteries-included/heyya
- https://hex.pm/packages/heyya
I'm not the submitter, but there is a length limit on post titles. I've run into this before with articles whose titles exceed that limit, and I've had to "edit" the titles to fit. I imagine the submitter had the same issue, and didn't catch the different connotation of "mimic" vs "posing as", which does seem to change the meaning some.

Dang: Do you think you could raise the length limit by 50 characters or so? Most of the problems I've had with title length limits seem to have been just a few words that I had to squeeze down..
Yeah they totally missed the mark with WinFS, in my opinion. It was too exotic/foreign with no clear adoption path.

All I want is dumb files with something like SQLite replacing or augmenting the allocation table. Then sprinkle on some new capabilities incrementally.
They're joking about a floppy body part
>Just make it cheaper to run in the long term, and everybody will just do it by default

That's how you get exorbitant taxes on the alternatives
GM to spend $19B through 2035 to source EV battery materials from LG Chem