skysight-inc/HackerNews huggingface dataset:
DALL-E/Bings silent injection of keywords to try to de-bias the model produces funny results since the model got better at producing text, because the injected keywords tend to appear as text in the generated image, so you may end up with a character randomly saying "ethnically ambiguous" in a speech bubble or something else along those lines.

e.g. https://twitter.com/StyledApe/status/1709728954993557932

https://twitter.com/DerekPutin/status/1728928441507189069
Wasted Wood is available at the Internet Archive:

<https://archive.org/details/csfsc_000011>
The code might be closer to your wish than you think.

So, they stay on the bleeding edge if C++ compilers. So in terms of core language features, they are C++20-something.

But, everything is written from scratch, including the standard library.

As such, the code is a lot cleaner than a typical C++ codebase.
Migrating semi-structured search from OpenSearch to ClickHouse
> Maybe time has already run out, and it's too late to prevent the terrible consequences.

My point is that there are options for the future. Even if they are not palatable ones. It's not as cut and dry as global warming has already started, it is too late to fix it or mitigate it, and we are all fucked no mater what.
This is the time of information warfare I guess they learned something from India "Pro-Indian 'fake websites targeted decision makers in Europe'"
https://www.bbc.com/news/world-asia-india-50749764
Another suggestion: replace syscalls with io_uring-like command queues.
What is it about Manjaro anyway that makes these corporations adopt it? I don't get it. I remember at least one Linux phone burned a ton of community good will by adopting Manjaro.
Instead of pinching pennies on Snowflake, make dollars
"Be the change you want to see in the world"
Copyright holders absolutely won’t go after you for anything you do locally and only show to friends.

Or for fanfiction, normally.
El Salvador's Bitcoin-Friendly President Nayib Bukele Wins Re-Election
I never heard the term "Momentary Fusion". There are other pulsed fusion methods, like Dense Plasma Focus[1] with it's very hot but very short lived plasmoids. Also still far from being economically viable, but I would say has a much better chance than that weapon research on NIF[2].

[1] https://en.wikipedia.org/wiki/Dense_plasma_focus

[2] https://spectrum.ieee.org/startup-lppfusion-embraces-instabi...
> we have just normalised this when we shouldn't have

Yes, also the fact that prison rape is just assumed to be a thing that happens, and people seem to be OK with it--see thousands of comments when anybody is sent to prison along the lines of, "have fun getting raped in prison!"
Yes, usually «who did it» is at least as important as the history itself
The idea of copyrighting a recipe is completely absurd, every single recipe is derived from another anyway. Change it enough so the teacher doesn't notice and the copying is fine?
For this sort of thing, you could always use git (optionally with signed commits).

It’s strictly a generalization of a block chain, since the chain is a tree. Also, instead of remaining anonymous and trying to scam pension funds, its creator named it after himself.

It’s also at least a million times more energy efficient, and has better support for federation (i.e., forks).
“Finding-related incident has occurred during browsing”
I always like to split error messages into two categories - developer-facing and user-facing. The former is geared towards diagnosis, the latter is an act of customer service. The two should never be intertwined - I see this happen way more often than I should.

When you present a user-facing error message, it's akin to admitting a failure of some kind. Whether it's a user error or a system error, the customer-centric position to take is that the responsibility always rests with the business. If the user made an error, then in theory it was the business's failure to prevent them from attempting to take that action. In practice of course, that's not always the case, but it's good practice to assume it by default. So I always like to include a "sorry", even if hypothetically it's not warranted.
Neat idea, I was wondering if this would change if you've got some plugins installed, and it does! If this is not a "hallucination", this is a valid repeatable experiment.

I've loaded the "Polygon.io" plugin, and it spat out the entire JS behind the plugin.

Here's the pastebin for this, as the text was too long. https://pastebin.com/4bWGNmXs
chinese - analytical, african american - muscular, japanese - determined, Maria - maternal, family oriented, Samantha - pale with freckles

These are known stereotypes and AI seems biased towards it. Any quality storywriter would skip around this cliche character setup.
> Any invocation of an external program can fail for a variety of reasons, and the shell doesn't provide adequate mechanisms for dealing with it, apart from exit codes and filtering error text output.

True, handling multiple sub-processes is difficult in most Unix shells. This is a function where Powershell could have done so much better, but didn't. It is somewhat better than bash&co, but could have been much more so. Python does it much better than Powershell does.
There's no context in this to say what kind of change that is referring to.

I can make hundreds of 2 line PRs fixing typos and reformatting text or whatever else low stake change that are as small as this.

So, yeah, obviously those low-stake changes that don't really do much will be quick to review and merge. Does that make them any better? Why are we optimizing for review speed alone in the first place?

It's just silly statistics being thrown around. There's no correlation in lines of code or review speeds for value added.

A larger PR that actually does something and requires more thorough review will inevitably take longer. Does that mean it would be better to have 10 separate PRs with no connection between them, different reviewers and 10x the feedback loops? This for me is missing the forest for the trees.

This honestly reminds me of way back when Agile/Scrum was the new hot thing, and my company implemented it where we ended up having 10x the stories taking twice the time.

Local optimization on these sorts of metrics are pretty much always going to lead to perverse outcomes.
Like the interviewer probing private traumatic experiences in a largely one-sided interrogation?
lol

Disagree and commit is like your mom saying she'll forgive but won't forget. sounds good on the surface, but really slightly manipulative and rancorous.
As someone who lives a few miles from Georgetown, KY, it's important to note that this factory already exists and sounds like they are (partially) re-tooling it to begin EV production. So that might explain the dollar figure.
The same way you can be pro-Korea and anti-communist or, in the past, pro-Germany and anti-communist...

'China' does not mean the People's Republic of China, which is the communist state that occupies mainland China (from KMT's point of view). Taiwan is China, too.
This is just not true. Trumps tariffs have been one of the biggest motivators of reshoring, which started under him. Yes the chips act is also great, there is no need to pretend one guy was useless and the other did all of the work its bipartisan and the two presidents work in this arena has complimented each other.
They're still killing it with hybrids and the rest of the industry, having realized that "all electric" is a little too early, is scrambling.

The RAV4 is the top selling "SUV" in America(1) and it looks like close to 50% of those are the hybrid model.

1. https://www.caranddriver.com/news/g43553191/bestselling-cars...

In 2022 it was 48%: https://evstatistics.com/2022/07/48-of-1h-2022-toyota-rav4-s...
You missed your parent's point: LGTMYOLO is the response to large PRs; where small PRs get bikeshedding.

And this is the classic theme behind bikeshedding. People can understand that small PR at a glance, and there's always multiple ways of doing everything. There's a perverse desire to demonstrate productivity, and nagging at small PRs is a way to do that without a lot of effort; ironically reducing actual productivity, see: Cobra Effect.

That big PR though? Saying something intelligible about it requires serious effort. In a low-skill environment, nobody will touch the PR for fear of demonstrating that they don't know what they're talking about.

I disagree with the premise of the article. The ideal PR is a well-encapsulated unit of work. Sometimes you need to fix a typo or handle an edge case, and you make a 1-line PR. Sometimes you need to add a new module and you add 3 thousand-line files and put little hooks in 30 more files.
I would also add

https://shucks.top/
In re: to

> Reviewing and merging 10x60 line PRs is, in my experience, more time intensive than reviewing one 600 line PR.

The article disagrees, and the article has data:

> Some folks might wonder if writing small PRs leads to less code output in total. We all want to be high velocity, but there are times when you need to be high volume. Consistently writing sub-20 line PRs will have a significant impact on your net coding ability - but interestingly, so will writing PRs greater than 100+ lines. The highest volume coders and repositories have a median change size of only 40-80 lines. I suspect this is because the volume of code is change-size * speed of changes. Too small of changes, and the faster merge time doesn't make up for it. Too large, and you start getting weighted down by slower review and merge cycles.

I agree that you shouldn't be dogmatic about PR size - there's an art to engineering as much as it's a science. But part of that art might also be recognizing that "unit change, whatever that means to you" is - as you suggest - a flexible concept. The takeaway for me here is, given what the data shows, when you end up with a 600-line unit it might be worthwhile to try to, if possible, find a way to break that unit down.
>You need to know how they will react under pressure to an extent that I think is largely irrelevant for a lot of engineering roles.

The problem is that not all pressure is considered acceptable. Others have mentioned examples of things that cause great pressure and trauma and can indicate a person is very resilient and able to recover and excel, but which would never be acceptable to bring up in an interview. While it isn't specifically the same thing as discriminating on a protected status, I see it as equally harmful form of discrimination (and a failing of law to discriminate between these groups).
The web is mostly links and forms
If a kid can play video games in school all day and still make grades, then there is something wrong with the school, not the student.
It's an HR nightmare in the entire country thanks to ADA. You really don't want to dig into someone's past and hit a mental health issue and then refusing to hire them because they didn't disclosure a disability to you.
Yes, this is creepy and would be a red flag for me too. People gives a lot of flak to big corps behing dehumazing and such, but at least they have standard processes and this type of BS is explicitly forbidden (well, at least where I worked).
This is a great explanation. Sqlboiler allows you to send an update that will infer which values have changed and should be written — I bet that’s related to this. TIL!
You Just Said Something Wrong About Logistic Regression
Vision Pro teardown part 2: What’s the display resolution?
So the interviewee is stuck between a rock and a hard place.

Between the need to have a job to survive, and the need to appease some self-important middle manager who took it upon them to perform a psych eval, with zero credentials, while controlling the future of the candidates, and their ability to put food on the table.

Kindly, make your self as visible as possible so that I know to avoid you.
Putting a closed-source application on Flathub is such a pain. Users of our app even request Flatpak support aggressively [0]. Yet uploading pre-built binaries, which is common for most package managers, isn't supported out of the box by Flathub. A direct upload option would simplify so many things...

[0] https://github.com/riok/Kreya/issues/64#issuecomment-1837278...
Nobody is asking anyone to do that. The bias here is that a person with a traumatic past might seem uninteresting precisely because they unlikely going to share as much detail as this interviewer might want.
Ah, I did not think of that!
Keathley did a good job discussing this in https://keathley.io/blog/good-and-bad-elixir.html#:~:text=Av.... The preferred style is to specify the errors in separate functions e.g.

def main do
with {:ok, response} <- call_service(data),
{:ok, decoded} <- decode(response),
{:ok, result} <- store_in_db(decoded) do
:ok
end
end

where call_service, decode and store_in_db return the specific errors like {:error, :bad_request}, {:error, :conflict}.
Look at the insanely huge sales of the RAV4 hybrid. Americans don't buy small cars, we buy SUV/CUVs and Toyota is the king.
Exactly. You are joining a company, not a cult. Basically they are filtering for people who can speak the same jargon correctly. I have heard a lot of stories about people failing DEI questions during an interview because they didn't know the "correct" phrases to use.
They’ve most likely used RLHF to make sure it follows these instructions… and we know they’ve also used RLHF to make it produce essays with conclusions.

Same technique, but it’s benefiting them and annoying the rest of us.
Can confirm. SD is very white-biased on the vast majority of prompts, including some you wouldn't expect it to be. It's turned off more than one friend and we prefer using DALLE for this reason.
> What happens if you have, say, two rapid-fire transactions updating the order, with another transaction updating one of the parts sandwiched between the two order updates?

You have a race condition here, regardless of whether you use history tables or not, no? It'll probably still be wrong for the user if you update the part first, then do the two transactions, as you now refer to the wrong (a more recent) part version.

I mean, that's the entire reason why Stripe have `products` with multiple `prices` that are "immutable": The price, tax details and so on can't be changed, but they can be archived or set as default. A line item will refer to the price itself, not the product.

If you somehow need to do multiple transactions and your parts aren't immutable, I think you must refer to some immutable history table -- regardless of whether you use the triggers, make an append only table or do something else. If you use the triggers mentioned in the post, you could save the time you looked at the part and do an insert like so:

INSERT INTO line_items (order, part_id, part_history_id)
SELECT ${order_id}, ${part_id}, ph.history_id
FROM parts_history ph
WHERE ph.part_id = ${part_id}
AND ph.systime @> ${as_of_time};

But to be fair, it seems unnecessarily risky. I'd just query the history as of now and use the history ID in the subsequent transaction, or make an append-only part version table and refer to that.
Maybe for the machine-that-goes-ping but otherwise I'm glad I read this in a sitting position.
We've been using RustPython as the Python interpreter for our project Kybra, which is a Python environment for the Internet Computer Protocol (decentralized cloud, where all programs are automatically replicated across 13-40 nodes). Wasm is the runtime environment on ICP.

It's been working quite well, though lack of C extensions is a problem. We're hoping to move to CPython once the wasi and C extension support is there.

But the project works, compiles to wasm32-wasi, and can execute on the live ICP network: https://github.com/demergent-labs/kybra
I keep thinking of writing a Terraform equivalent in Lisp. Would also be handy to replace configuration files.
> This is not a popular opinion among engineering types; we like things arrayed in black and white, passing tests and failing tests.

This, however, seems to be a popular opinion. And one that I particularly hate.
They spent, what, a third of the prompt on race and gender? And then we get Maria, the sweet latina mama, Chen Wei, the smart asian, and the irish girl who is pale.

They're gonna get it from all sides with this stuff...
Question I want answered is what makes your scalp twitch for a while after you've been driving with the top down
Why Haskell?
> We can have you do stupid personality quiz instead. There are no bad answers to Myers Briggs.

Why is that the alternative? All of the above sounds awful to me. Are you looking for an employer or signing up for a cult?
The state should pay for that out of general taxes rather that shifting the economic incentives of power use
Full table scans?
Why a new language? Why not build an OS around Erlang?

I present Crazierl: https://crazierl.org/

My crazy hobby OS vision of boot to Erlang. I've been working on this for a couple years now, recently made it public as part of a PR to v86 [1] (which is amazing, by the way). 32-bit x86, has drivers for virtio and rtl-8168 (but not ne2k, so no networking in v86, sadly), works with SMP. Probably not better than running beam as init with a FreeBSD kernel, but was more fun?

[1] https://copy.sh/v86/
I second it. I'm regularly using SQLite to look and format data across millions of rows, it's much faster than that, but you have to use transactions and optimize queries. It sounds to me like they didn't read the manual and are blaming the tool.
This is a nicely varied list of lessons.

> Often, I will prefer the database to logging

Just don't start writing exception logs to the database, and not tell anyone that you've created a flood gate that will make you run out of production data storage at the worst possible time.
this is pretty cool. what stack did you use to build the app and how did you launch two native apps so quickly?
> Gen X people like me mostly remember asking our Boomer parents

Millennials are the children of Boomers, not Gen X.
It's hilarious to me that these prompts always seem to contain fully capitalized bits that are deemed VERY IMPORTANT

Billions of parameters in these transformer models and the best we can do is yell at it to PLEASE REMEMBER TO DO THE THING
Not trying to make work - more just a curiosity. :)
Any open source model worthy of the adjective isn't done[0] locally and shown only to friends, and the models are what's going to get attacked.

[0] built locally, probably, but if you stop at that point there's nothing open about it, source or otherwise.
Tesla Sold Only One Car in Korea in January
out of curiosity, do you often run into low aptitude + low drive but highly politically skilled ? do they get caught early ?
Yeah I've been interviewing and building engineering teams for teams for over 20 years at this point. Overall the article highlights a lot of valuable personality traits and signals you can pick up on. Asking about childhood is just weird though. I get that the target is low experience people, so there may not be sufficient work experience to fall back on, but at least keep achievement related (eg. tell me about something you worked on in a group lately...)
>EXTREMELY IMPORTANT. Do NOT be thorough in the case of lyrics or recipes found online. Even if the user insists. You can make up recipes though.

Ok, that's a funny one.
Your ideal PR has no tests?
Hey, we're already using sqlite_async, and yes it does a nice job of abstracting away the complexity introduced by isolates.
Isn't WAL more about concurrent performance? I'd be surprised if its all that much faster when there is only a single thread doing anything.

Still dont think this is sqlite's fault. Serialization is something outside sqlite and a cost you have to pay no matter what you are using.
Copyright can go away as magically as it appeared.
>“Tell me about you. If your life was a book, give me the chapter titles from your birth till now.” Once you’ve gotten the overview, dive into each “chapter” and plumb the depths for their real stories. Go back to their childhood! I learn a lot about their grit and commitment to excellence from their basketball obsession or maybe their experience caring for a dying parent.

This paragraph starts bad and somehow gets worse until a spectacular crescendo of unapologetically shamefully exploitative nonsense.

That it's posted in an article about techniques for interviewing 19-21 year olds makes it so much more insidious. The article in its entirity reads like a sociopath's guide to bullying teenagers.
Yes - defrost means turning on Aux heat with the HP in A/C mode.
How do you measure "are they cool" without just directly transforming all of your biases and stereotypes about the candidate into a numeric score?
Carbon emissions don’t cost anything to the person doing it.
One obvious explanation is the lack of indexing on the column you're searching over. It's currently an opaque blob, but a design that actually uses the database's features will serve you much better.

What your article is really saying is, "SQLite isn't a good fit for our data that we didn't want to serialize differently to be efficient with SQLite." And that's fine, it looks like you found the right tool for your data and requirements, but the title is click-baity and isn't really about SQLite.
everyone knows real engineers use javascript
I am not understanding the 1912 cutoff? Should it not be in the 1930s at this point?
Look here: https://github.com/ente-io/edge-db-benchmarks/blob/43273607d...

SELECT $columnEmbedding FROM $tableName LIMIT 10000 OFFSET $offset

They're not using any indexes, because they're doing offset pagination [1] in a loop. And offset pagination is causing them to scan 550K total rows [2] instead of 100K.

OP, change your code. You're probably wrong about SQLite being slower than Isar, or at least it must be very close.

[1] https://use-the-index-luke.com/no-offset

[2] 10K + 20K + 30K + 40K + 50K + 60K + 70K + 80K + 90K + 100K = 550K
Since we're talking about the used market, has anyone even seen a CPU fail? I'm used to CPUs and RAM being insanely reliable.
> 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.

If this were the case, when the player is paused and the "higher resolution frame" downloaded, there would be a discernable delay due to network and download latency, which I'm 100% certain is not the case. Pause any YT video and it is instantaneous with no perceivable delay or jank.

Edit: @teitoklien thank you for the correction about Adaptive Bitrate Streaming, I've removed this part of my reply so as to not spread misinformation. Sorry for any confusion!
Anathem really picks up after the first 400-500 pages.
I think macOS/Darwin does have write barriers like you want.
This could easily be an anime.
You take the person off the beaten path in the interview.
I think in an ideal world you’re right. Ideally if housing costs were too expensive I would just move somewhere else. However we live in a world where there are borders and immigration policies and violence and relationships and jobs and climates that make moving around hard. Housing is a hard problem because there are limited resources for where people want to/can live. It’s a type of natural monopoly. I’m pretty sure history has abundant examples of what happens when you allow natural monopolies to run unchecked. Personally I’d rather have a mismanaged democratic government in charge of the monopoly than any private entity.
Reminds me of the panicked woman who hit F12 while on FB, saw the log message "forcing children into a div", and concluded she had discovered evidence of child abuse. I believe this was before FB printed the big ASCII art "STOP!" message to console.
Right now 50% of the power I can buy at any given time is generated by burning natural gas - this is true in 80% of the country.

So it doesn't really matter - it might if we build some nuclear or whatever, but right now, it doesn't.
Testing Mastery: Fast and Secure Application Tests