skysight-inc/HackerNews huggingface dataset:
You would probably find Hindenburg Research interesting:

Hindenburg Research LLC is a U.S. investment research firm with a focus on activist short-selling… Named after the 1937 Hindenburg disaster, which they characterize as a human-made avoidable disaster, the firm generates public reports via its website that allege corporate fraud and malfeasance.

https://en.wikipedia.org/wiki/Hindenburg_Research
Instead of migrating one column, now you have that and every table with a foreign key to the original. Requiring transactions and possibly locking etc.
It's sad to see that the educational system stayed generalized, and never customized to each person's mental capabilities, I always find neat articles discussing different topics from a totally different perspective. If only these existed back then when I was a studen.
Pay some amount of money in your country to set up a corporation and make an enterprise account (which does not have the 20 tester requirement, that's only for personal accounts), problem solved. In the US, this only costs 200 dollars as a one-time fee, at least for the initial setup.
> So they want to use your freelancing profiles (Upwork, fiverr, etc) your IP address (Using TeamViewer), and your US bank accounts to secure those contracts. They'll split the profits with you 50/50. All you have to do is let them apply to jobs using your account, show up for the online interviews and pretend that you're the one doing the work.

This is Nigerian Prince level of obvious red flags.
It would be so cool to also have access to GCP resources!

Great job nonetheless!
UUIDs are only good when you don't care about ergonomics or performance.

Snowflake IDs are much more reasonable. 41 bits timestamp (ms) + 10 bit machine id + 12 bit serial.

But if you care about ergonomics and privacy the most then short and random IDs are really the best.
Yes, you can go to great depths, but they each have trade-offs - in performance, increased complexity etc. and it's necessary to make a judgment for each particular app instead of applying the most overengineered solution everywhere.
Apple's Secure Enclave utilizes a separate processor isolated from the main processor(s): https://support.apple.com/guide/security/secure-enclave-sec5...

It runs it's own microkernel-based OS to isolate individual tasks/functions to mitigate the impact of one of those tasks having exploitable bugs.
Or more charitably, someone thought "I wonder if users would like this feature", so shipped it to see, and then saw they didn't use it, so removed it to reduce complexity and move on to more important things.

I'm not saying you're wrong, but in my experience few are thinking just about their CV or promotions, and most product changes are driven (at least publicly, within the company) by a desire to improve offerings for users.
I was going to short a few shares just for fun, but TIL that the tokyo stock exchange only lets you trade in multiples of 100 shares (~228 USD per share right now for TYO: 6920 Lasertec Corporation)... https://www.jpx.co.jp/english/equities/improvements/unit/
This is a tech-focused selection from my personal list, with a few more business-y sources thrown in:

- https://erikbern.com

- https://lethain.com

- https://commoncog.com

- https://scattered-thoughts.net

- https://danluu.com

- https://ideolalia.com

- https://staysaasy.com

- https://collabfund.com

- https://blog.nelhage.com

- https://jacobian.org

- https://equalventures.substack.com

- https://defmacro.org

- https://spakhm.com

- https://apenwarr.ca

- https://scarletink.com

- https://benkuhn.net

- https://cpojer.net

- https://brandur.org

- https://zeptonaut.com

Let me know if you want some reading recommendations for any of these!
It’s worth noting that Shreyas (the first author) was a student with Tenenbaum at MIT before he went to Berkeley
Wait? Moving the pagefile, which should cover large memory allocations (not necessarily large memory usage, just the allocation), to a Memory based disk. Well...that's interesting, to say the least!
maybe a voice assistant that represents the candidate, but does the reviewer have time to play around with them?
Unfortunately it only works for systemd units, as far as I am aware.

Consider this use case: I have a test program which executes some unit tests, it creates some temporary files. I want the temporary files it creates to all be removed when it exits, even if it core dumps. But while it runs, I want those files to easily be accessible to subprocesses it spawns. I don't think systemd addresses this, because my unit test runner isn't going to be a systemd unit.

So really I was talking about a generic facility an arbitrary program could use, not just something limited to systemd units only.
Connecting to GKE for k8s events/deployment info is WIP, we plan to pick up Stack Driver too soon.
Not really assigned at birth, but at the time you first request the card. It's a very very very crappy database ID number:

-There's a significant amount of duplicates, enough that if your database is big enough you will find one sooner or later.

-Format is variable: There are older 7 digit numbers, modern 8 digit ones, some people pad the 7-digit with a 0, some don't, some consider the CRC letter part of the key, some don't, some just append the letter, some hyphen it. If you deal with manual data entry anywhere, you will suffer.

-Foreign people exist: You start using their passport number, the format of your key is now completely arbitrary, can't validate it. If you were using 8 digit NIFs as keys now some countries use 8 digit passports, increasing your chances of duplicates.

-Foreign people stay: They get a resident card and they use that. Format is almost like NIF but not really so you need to account for that. Someone you registered initially with a passport now has the card and registers for something else with it. Have fun cleaning their duplicated identity from the whole system.

-Foreign people become Spanish: Now they get a NIF. If you have dealt with them for a long enough time, have fun again fixing their records for the second time.
Say Goodbye to Your Todos
> a service that provides you with a stable id

I think there's the important point. Is your key actually natural or is it someone else's surrogate key anyway? Going back to the vehicle identification number: that's already a surrogate key. You just did not assign it yourself.
The question here is whether it is better to silently guess at the author's intent or to loudly say "your intent isn't clear; try again".

I strongly believe that the second is the better approach for nearly all use cases. When I'm writing a grammar, I'm focused on the happy case and not on how the rules interact with each other. My intent was to write a grammar with only a single result, indeed, but if that's not what I've done, I'd want to know!
For actual best results you’d probably want to truncate at the word or syllable boundary, and it should likely be language specific.
eNclave
eXclave
> So if a company designs an interview process that involves all this hoop jumping and whiteboard hazing, they are deliberately adding bias against older, more experienced candidates.

I agree about the bias though I don't think its deliberate. I think its just the easiest way for them to filter through masses of candidates.
> surrogate keys can be fixed size integers

This launches into the other debate about PKs: using UUIDs rather than sequential keys.
> scaling the team is going to be slower

On the other hand, the ROI from hiring a couple of developers with Clojure/CL experience is almost always guaranteed to be higher than hiring a bunch of "regular" programmers. Niche languages like Clojure usually attract more experienced, tired, "seen some shit" developers who have likely worked with multiple languages before. Their broad experience typically leads to higher productivity and better-quality code.
In this case of doctors being paid to endorse drugs, the problem is that there is payment being exchanged at all. The issue persists whether or not the drug is effective.
Show HN: Summarise GitHub Actions failures in your PR with an LLM Bot
Hi HN!

I maintain a popular pytest plugin[1] and throughout its life have supported and observed many developers struggling with GitHub actions.

- It's hard to identify what caused a failure given the length of some ci logs
- Multiple ci jobs can fail with the same cause meaning it's noisy
- It's unclear how to prioritise fixes to these failures

This Github app gives you a prioritised, de-duplicated list of issues relating to your GitHub actions failure.

It uses LLMs (GPT3.5 at the moment) to identify the most likely root cause, highlight relevant source files, and order the issues by priority.

Feedback welcome!

[1] https://github.com/treebeardtech/nbmake
Their Diplomas Came with Envelopes of Cash, and a Catch
This also demonstrates how a legacy reputation, built over a period of decades, can be also thrown away in a period of weeks.

VW quality deteriorated incrementally over the years but it was the emissions cheating scandal that became the wake-up moment.
https://archive.is/5X9Cm
That's the one! myinitials@ntlworld.com

And NTL merged with Virgin in 2006, making it 18 years. Oh dear.
That would only be true if they eat a pure grass diet. They do not. They are fed soy, which is perfectly edible for humans.

https://ourworldindata.org/drivers-of-deforestation

>More than three-quarters (77%) of global soy is fed to livestock for meat and dairy production. Most of the rest is used for biofuels, industry or vegetable oils. Just 7% of soy is used directly for human food products such as tofu, soy milk, edamame beans, and tempeh. The idea that foods often promoted as substitutes for meat and dairy – such as tofu and soy milk – are driving deforestation is a common misconception.

If we stop that, we free up a lot of calories for human consumption. I'd say the total amount of pure grass fed animals would be way lower, which would be better for the environment of course, and meat would be much more expensive. Actually, I like that. Good idea!
My suggestion wasn't to improve the bottom line of dating apps, by the way.

Dating apps are already incredibly profitable with all the value being provided by users.

And pretty much every initiative to make them more profitable amounts to selling one segment of users to another.

See Tinder Deluxe.
> seemingly completely unrelated number words for different context

I don't know much Japanese but I don't see it as that weird. I see it as something like "murder of crows" or "pile of sand". Something cultural that was there for a reason (or a monk somewhere) and now we have to memorize it.
I wrote this because I had no way of tracking every time someone wrote "@todo" across a codebase. This stores them in a central location and then you can work on getting rid of them over time.
Let's hope they continue making progress. Expected failures are fine. Unexpected failures have the potential to derail such a program for years.
Thanks! That option did not exist when they released this feature.
Nice game! Finished a small one now - https://huewords.snellman.net/share/44s0 . Let me try something harder.
Is there an 'undergraduate' version of the course?
Here’s an article that speaks to this:
https://www.onclive.com/view/markman-column-optimism-plays-a...

In short, yes! Mental outlook has a big effect on outcomes. It won’t cure you, but it will improve your physical outcomes.

This is the meta analysis they refer to:
Rozanski A, Bavishi C, Kubzansky LD, Cohen R. Association of optimism with cardiovascular events and all-cause mortality: a systematic review and meta-analysis. JAMA Netw Open. 2019;2(9):e1912200. doi:10.1001/jamanetworkopen.2019.12200
Omakub – Linux setup script from DHH
From the Github repo, it writes -

Turn a fresh Ubuntu installation into a fully-configured, beautiful, and modern web development system by running a single command. That's the one-line pitch for Omakub. No need to write bespoke configs for every essential tool just to get started or to be up on all the latest command-line tools. Omakub is an opinionated take on what Linux can be at its best.
Valid point, but then I wouldn't consider classical mathematics to be a science
Wonder if this is linked with their introduction of IP protection, another VPN, within Google Chrome?
One of my first jobs involved an account management software which created an ID for each user based on first name and surname. So John Smith would get SMIJOH. It was the user natural key and it could not be changed once created.

One woman got married and changed her name; se became really upset when she found out that we couldn’t change her login.
Wow thanks! At least the person I spoke to asked permission to impersonate me first.
That's not what I said. They did offer it, then removed it after I had made the decision to use them partly based on the Open Source self-hosting nature of the project. They used Open Source to bait and switch me.

I don't even need helm support, I'm fine to do my own. But they stopped even providing versioned releases so there's no stable tag or branch to build and target. That's actively hostile to anybody not spending their full day managing Posthog stuff.

I had planned on switching to the cloud Posthog when we got big enough, but it seems like we will have to start out with other options and it'll be much harder to change that later.
Maybe in 200 years, the industrial revolution itself will be considered a crime against humanity.
What has worked best for us is to have a sequential integer as the primary key as well as UUIDv4 as a surrogate key for every row. The applications would expose the objects only using uuid and never the primary key. The primary key always remain internal at the database level and never gets referenced or used at the application layer. In this way the security and privacy of objects are maintained and having sequential integral primary key for the object ensures the database design remains robust. Essentially, separating out the key for the database and the application. Is there any potential issue with this approach?
Wait, are you talking about the systems with separate memory modules?

I'm talking about these new things with ram integrated into the SoC...
In my experience, this won't end well. Some examples:

Belgium has the RNR/INSZ identifying each person. But it can change for a lot of reasons: It gets reused if someone dies. It encodes birth date, sex, asylum state, so if something changes (which happens about every day), you need to adapt your unique key.

Belgium also has a number identifying medical organizations. Until they ran out of numbers. Then someone decided to change the checksum algorithm, so the same number with a different checksum meant a different organizations. And of course they encode things in the number and reuse them, so the number isn't stable.

An internal COBOL system had a number as unique key, and this being COBOL, they also ran out of numbers. This being COBOL, it was more easy to put characters in the fixed width record than expand it. And this being French COBOL, that character can have accents. So everyone using the 'number' as unique key now had to change their datatype to text and add unicode normalization. Not fun.

In my experience: don't use anything as an ID that you didn't generate yourself. Make it an integer or UUID. Do not put any meaning in the ID. Then add a table (internal ID, registering entity, start date, end date or null, their key as text). You 'll still sometimes have duplicates and external ID updates as the real world is messy, but at least you have a chance to fix them. The overhead of that 1 lookup is negligable on any scale.
Some explanation about Fourier transform can be found in the Feynman lectures here, https://www.feynmanlectures.caltech.edu/I_50.html
I use it all the time, simple example if you can't remember a word you can describe it to ChatGPT and it will respond with it.
This reads like something from the 90s. Buy whatever you think you need as swap as "more RAM" and call it a day. I'm running my desktop Linux without swap since maybe 20 years, and I never had any of this "pathological behaviour at near-OOM" afterwards.

And I have time to think about better problems than "You can achieve better swap behaviour under memory pressure and prevent thrashing by utilising memory.low and friends in cgroup v2."

The core problem with swap is that nowadays you need gigabytes of swap to actually make a difference (when you have 32GB of RAM, 1GB of swap is 1/32 of a difference). And you certainly don't want to system to swap in and out gigabytes of memory.
Sony Pictures CEO announces controversial change to films and TV shows
> I'm not saying it's a bad practice, the opposite actually

I'm sorry that I didn't make that more clear. I saw that you mentioned it as a best practice and are aware of the advantages. It's just that there are so many others that don't have the balanced view as you seem to have.

I have been involved in many discussions at my work place where "security by obscurity" is used as a way to shut down discussions. They changed their minds about sequential keys after the incident I mentioned, but it still has the power to "win" other discussions. Sure, we need to have rate limiting on ip-addresses, auth and other mechanisms, but they are not perfect and bugs happen all the time. An "unguessable" id is an additional security layer

> It's not an easy thing to add into an existing application, though

I agree, but there are ways to reduce the attack surface. You could add an extra "public id" field that can be used for lookup in addition to the existing id. In this way you can have a gradual migration where you go through each endpoint and migrate them individually without changing the foreign keys and other relations in the database (they would still use the sequential key). Maybe you end up not having time to migrate them all, but at least you can reduce the attack surface on the most sensitive endpoints.

If you have low volume endpoints you could perhaps even simply add a mapping layer where you do a simple db lookup to replace the public key with the internal without changing the existing queries. You could even cache this easily to reduce the db load. (both ids are permanently fixed and can be cached forever).
Is there a Facebook/Meta version of this?
Subaru was affected by the Daihatsu scandal because they sell a couple models that Daihatsu produces under the Subaru brand. The Daihatsu Tanto, for example, is also sold by Subaru as the Chiffon.

As far as I know Subaru didn’t do anything wrong.
Fair. I read the comment as, more or less, "the typical laptop has so much RAM these days that putting ~/.cache on tmpfs would be a reasonable default" or something like that. But I guess it could -- and should -- be read as, "if you spend a bunch extra on RAM, you can get laptops with so much RAM these days that you can consider putting ~/.cache on tmpfs", which is reasonable enough.
Holy hell. Wow that's harsh, I'm super glad you are employed now (even a terrible programming job is better than a home depot job) and that ordeal is behind you.
This lousy economic cycle will eventually reverse a bit and we will hopefully all have some more leeway to find better employment.
how about swapping it out with a small... camera?
Is this an issue if you get $100k? That should more than cover flight tickets and hotel stay.

If you're not even willing to do two travel days, why are you even participating in a 3-month accelerator? Doesn't sound like you want that kind of commitment.
I love that in this kind of product's advertisement, people are so highly capable of touch-typing. The reality is that most people need to glance multiple times at their keyboards while using it. If these glasses make that a pain, I doubt that people would keep using the product.
Google googling Google things.
I completely agree with bishbosh.

However, can I know what is that easy way to check if every single chip of a motherboard will be compatible with linux?

I am honestly asking, because I have not found anything to check hardware.

the same way, if I want to make a computer formed with parts from a store, (not a prebuilt) how can I check all pieces to make sure that it will be compatible?

Thank you.
It tests knowledge of how C++ itself is implemented. That's not really something most people study or prepare for unless they work on C++ compilers. I wouldn't call knowing how vtables are implemented intermediate-level C++ knowledge, and I never again encountered it despite spending another ... 5-6 years writing C++ code afterwards.

It's intellectually interesting for sure, I think depending on how it's introduced it could make an interesting discussion in an interview. But asking someone to implement them from scratch on a whiteboard? Come on. :)
Any downsides? In particular, will games work? Visual Studio?
Cannot tell much about the app itself as I just learned about it and has to see how it performs. However I wanted to comment on the buying process. You can pay any amount which you think is fair and get a download link. Later on you can donate more if you like. This is, for the Apple eco-system, really refreshring, and I very much miss this for iPhone Apps. I do not know how often I have installed and directly after de-installed apps because I cannot use them until I payed x bucks, which is completely rediculous because I do not know if the app will do or work in my setup / use-case.
Common fallacy in sysadmin:

- A user has a system with X RAM and Y swap. They buy Y RAM. If one compares (X RAM + Y swap) versus (X+Y RAM), it's obvious that they don't need swap anymore.

Thing is, the correct comparison is (X RAM + Y swap) versus (X+Y RAM + Z swap), where Z is a new amount of swap.
If anyone works in bioinformatics, please, please, for the love of god, generate your own unique IDs.
Database identifiers are not generally unique (the same id might get reused for e.g. protein variants). Even sequences are problematic: I've found the same seq with different ids (can't remember the db now), and they can change (sequencing or human error might've occured and they get updated).
Taales: Tool for the Automatic Analysis of Lexical Sophistication
Who doesn't understand YYYY-MM-DD? Never in all my (many) years have I encountered any divergence from that.
“improve offerings for users” without basing it on anything other than “let’s see if they like it” is CV development. It gives you an excuse to build something new rather than squeeze out a tiny performance gain in the money machine.
> From my experience, anytime you try to turn human interaction into a mass market app that can appeal to all users, it inevitably turns to shit over time as it keeps getting gamed by all parties involved till it implodes from the shittyness.

But what I described doesn't appeal to all users. It appeals to a subset of the exact same demographic using dating apps, it just also appeals to them beyond finding their first match.

You join the app and still have to find a match (or join with your partner; admittedly, a different demographic) to access any additional features. It's not some app you hop on to find a good grocery shop for Manuka honey or booking a flight.

If the matching aspect works fine, adding additional features shouldn't reduce use of or interest in the app, unless they're coupled with an annoying UX ("Hey, we took time to add this so you must use it").

It's not an "everything" app, it's about providing additional value to the existing audience that extends beyond just matches.

I don't think we can definitely say something like that does or doesn't work until we see enough of them crop up and fail. From what I have heard, niche dating apps (or "singles apps", more appropriately[1]) do okay in localized regions.

I would bet they probably would do okay on a larger scale, just that real life dating probably is a different game from city to city and so you can't just ship the exact same experience as you might for Vancouver to Springfield

[1] https://dvt.name/2020/02/24/rfc-lets-disrupt-dating-apps/