skysight-inc/HackerNews huggingface dataset:
Things - Reliable, maclike and generally well thought out/polished piece of productivity software. Stand out feature is its hotkeys and os integration make capturing useful reminders of what needs doing as it comes in from various sources quick (== far less likely to be forgotten).
Possibly during the big bang era?
Try 8x10 transparencies. You will be hooked.
Is there a theoretical reason that a sufficiently-gigantic ultrafast pulse laser with a sufficiently-massive lens couldn't put enough photons at the focal point?
If such a tool became commonplace, bad actors would just run it on their own malware and keep tweaking it until the LLM failed to detect it.
> And that's fine for most weird nerds. Being cordial and respecting of knowledge is all that's needed in the workplace.

Well, no it isn't. That was the point of the top comment in the chain: the commenter worked for Weird Nerd, found them insufferable, told everyone they were insufferable and that working for them sucked, and as a result the Weird Nerd's career has tanked because no one new will work with them. There really aren't many cases where you can Go It Alone without any support from anybody, even if you're brilliant.
That seems like an almost exact duplicate of the NodeJS/NPM issues?

Those same points (but the NodeJS/NPM version of them) is a lot of why that ecosystem is having security and reputation issues as well.
Thanks a lot! Good luck with your engine as well :)
That’s hilarious …
Yeah you're right, people miss use the term keylogger frequently. These kind of malware are broadly called "stealers" and usually do not involve keylogging.

Actual keyloggers tend to be rare nowadays due to them being easier to detect and the fact that in general the browser data is a more valuable target.
Not sure if you know this, but not uncommonly, non-English-speaking countries, like Japan, don't offer international shipping.

After learning some very simple Japanese, I developed a good relationship with a Japanese record store in the '00s via letters to get each of the very small runs of CDs that Office Augusta used to do (they didn't make it available digitally in the West until well into the '10s). Would get some great additional records gifted from smaller and far more obscure indie artists. Was amazing. Couldn't use cards with their payment system, so paying was a complicated affair, but absolutely worth the fuss.
What better box is there than a black hole event horizon?
I would say the masses won in this case, instead of academics and CEOs in high towers… now they have to share some power with the rabble.
HR is not your friend. "Human resources" -- guffaw! Of course, the Human behind the desk is more than their role.

Conversely, I've met brilliant people living on the street because [trauma]--who can't get a leg up because they're stuck in a proverbial catch-22 where bureacratic desk-jockeys can't help (even if they want to) because those of us working in state/corporate jobs love kicking the can.

I hope future generations figure out how to get shit done.
Docker itself doesn't seem to have the best quality control for their official releases, so blindly upgrading Docker will likely bite you in the ass if you do it for a few years. :(
Yes, I understand your point. I based my approach on similar "check order status" apps, many of which operate in the same way. However, I chose not to share any personal data, so it only provides general information about the order.
TBH, while I definitely could see this being an easy bug to write, something is definitely wrong if it took 5 days to identify the root cause of this bug.

That is, I'm struggling to understand how a dive into the logs wouldn't show that all of these inserts were failing with duplicate key constraint violations. At that point at least I'd think you'd be able to narrow down the bug to a problem with key generation, at which point you're 90% of the way there.

I also don't agree that "usual tests wouldn't catch it (db wiped for good isolation)". I'd think that you'd have at least one test case that inserted multiple users within that single test.
> almost all their other products are marketed as "Replace" for ICs from big brands

Made in China 2025 plan https://en.wikipedia.org/wiki/Made_in_China_2025 Subsidies for manufacturing/using locally sourced domestic components.

Good example is this teardown of Deye SUN-5K-SG04LP1 5kW hybrid solar inverter https://www.youtube.com/watch?v=n0_cTg36A2Q. Brochure advertises top name brands, all Chinese clones
(presumably high quality) substitutes inside.
I Code in the Cloud
In a world where this entire codebase wasn't generated by ChatGPT, you'd have engineers familiar with the various parts of the system to quickly identify and fix the problem.

Testing and debugging isn't just a matter of stepping through code, it's an exercise of seeing where your mental model of the codebase is faulty versus the current reality of it.

I've encountered similar problems and they'd be fixed in a matter of hours, not days.
A compiler by itself is surprisingly easy, especially if you read Abdulaziz Ghuloum's or Jeremy Siek's tutorials. Making it competitive with state-of-the-art compilers like Clang or HotSpot is difficult, but this is true for every kind of software.
Love this. This really appeals to my way of thinking, it's oldskool, but extremely practical.
I was going to dismiss your comment thinking that it wouldn't be possible to capture the amount of carbon we are emitting with trees alone .. but after running the numbers, trees seem like a pretty decent solution.
A cleaner API you mean which exposes what is necessary only.
No, I want the computational feasibility explanation with some nice O(function) on biological processes. To the best of my knowledge, we still have no idea.

Something like "the computational complexity of a beached fish to invent and grow a leg is O(n^2 log n) hours where n is the number of neural spikes in frontal cortex" or similar.
Thanks for not telling us the track! I probably love that song, whichever it is, and wish to remain ignorant.
nobody ported python to wasm yet?
I honestly feel that way every time I walk into the hardware store.
They could also have done default=uuid.uuid4 to have a new id each time, or default=lambda : str(uuid.uuid4()). It's not really related to whether or not it's a database default.

It seems quite unfair to place the blame on SQLAlchemy here, or even Python.

Even a statically typed language wouldn't prevent this kind of issue - the author of the code is the only person who can decide when they mean "use this exact string each time" or "use this function to give me a new string each time".

I suppose a column description API could follow the dataclass style definition, with different argument names for default and default_func. That would (I think) prevent this from happening.
Answer, for anyone wondering not wanting to read the article -

> We find that men who are more dissatisfied with the size of their penises are less likely to personally own guns across outcomes, including any gun ownership, military-style rifle ownership, and total number of guns owned.
Yeah, in Paris, for the last few years, in my flat, I have turned the heating maybe 2-3 days per winter.
I believe there should be a clear indicator in UI of every OS when any new program listens to your keystrokes.. it should be the norm
It's easy enough to learn "base + index*scale +- displacement". And it can be written in exactly that way, in whatever order makes the meaning of the code clearest, as you would do it in a higher level language.

AT&T syntax forces you to learn this before writing or even reading a single line of code that references memory, instead of giving the illusion that maybe something like [eax+ebx+ecx] or [[eax]] was also allowed. I don't think that's very helpful. It also forces you to learn a very specific way of writing it that is completely unintuitive.

I'm somewhat sympathetic to the argument that assembly syntax should correspond to the underlying hardware, just not to such an extreme. For example, I prefer 8080 over Z80 for that reason (one mnemonic for each addressing mode).
From a quick scan of the code, on mobile, it doesn't look like it does.

This seems to actually manually parse the ELF file and recursively parse any dependencies.

Pretty cool.
There's a hammer museum in Haines Alaska with similar vibes. Countless different types of hammers.

https://www.hammermuseum.org
So it's an absolute moonshot that posits that all observed discrepencies of galactic rotation curves is actually due to a coincidental and highly unlikely distribution of topological defects (that are not consistent with the full field equations) that have not been observed, and also fail to explain every other feature of dark matter at various different scales. nice.

Its fine for a paper but doesn't really make sense as an article unless you are more interested in ad revenue from titles like "we don't need mass for gravity" than the ideas being presented. These science article websites live solely off of people who aren't equipped with the prerequisite background to actually critically parse the ideas that are being presented.

This is probably the reason why everyone ~online~ (and not in departments) loved string theory two decades ago, and virulently hates it today, and also think that dark matter "is just a bunch of BS from the physics establishment" and that things like MOND or this are even remote competitors to the general consensus (which is basically just - we have no idea but we probably just need an extension to the standard model / quantum gravity at somepoint in the far future).
> My main point: as a consumer of these files, I prefer it when people send me TSVs rather than CSVs, because I am more likely to be able to use a simple not-really-TSV/CSV parser to read them

My point is that you are not really talking about CSV/TSV since your parser does not handle CSV/TSV. You are using a custom dataformat. Which is fine and perfectly reasonable, and its probably specified to avoid all those issues.

But it is not CSV or TSV. When you say "a simple not-really-TSV/CSV parser to read them" you mean you are not using CSV or TSV. That's fine for non-CSV and non-TSV. usage. Just be clear about what format you are actually using and specify it. It clearly isn't TSV or CSV.
Stop chasing consensus, start building momentum and farming for dissent (2023)
Blum–Byrnes Agreement
Line 56 is executed as the file is loaded. Simplified, the line is essentially:

id = Column(default=str(uuid.uuid4()))

As written, a UUID is generated once and used to set a class-level attribute. Each Python process would generate a unique value, so it wouldn't be immediately obvious. Most of the time Python's ability to run code as a file is loaded is helpful, but this is one the well known gotchas.

Although I'm not a SQL Alchemy user, I assume the fix is essentially the same as it would be for Django. So the correct code would have been essentially:

id = Column(default=uuid.uuid4)

Instead of executing `uuid4()` and caching a single UUID value, it would have executed `uuid4()` each time a new object was created.
Oh definitely. Their ops experience seems very low. But I've found it extremely uncommon to see anything better in smaller projects.
I think you've got "discussion" and "marketing" confused, but that's not a surprise given how many spam submissions you send.
Oh, that one I have added in code manually (500ms). Some random delay to make it sound pleasing.
Thank you.
I meant sandbox the less trusted bit.
During the work day, this was fine. We probably committed 10-20 times a day

That's... scary, to put it mildly. I wonder how many of those are fixes to things broken by previous commits. Then again, I work on software where the average is far less than one commit per day, although it's a mature product. Nonetheless, "slow down and think" is probably good advice in this case.
The refresh rates are disqualifying.
The Functional Programming Hiring Problem
Tadalafil works well for getting more out of your workouts too (I take that). Gives you an overall feeling of well-being too (better than any cup of joe), I no-bullshit begin my day with it.
The fact that they couldn't find it by looking at error logs is weird to me.

This is an entirely forgivable error but should have been found the first time they got an email about it:

"Oh, look, the error logs have a duplicate key exception for the primary key, how do we generate primary keys.... (facepalm)"

Funnily enough, I saw the error in their snippet as soon as I read it but dismissed it thinking there was some new-fangled python feature which allowed that to work like the function def defines that default= accepts only functions so the function gets passed? -- I haven't kept up with modern python and that sounds cool and I figured the bug couldn't be THAT simple.
From a certain perspective, there are two kinds of fields in the academia: "laboratory science" and everything else. If you want to make a career in laboratory science, you need to be a manager and a professional beggar. You need to bring in money to hire people to do your research, and you need to support the administration with grant overheads. If you are good at the job, you pay the administration more than they pay you. Long-term non-manager positions are rare, because they are more expensive for the university than successful managers.

Outside laboratory science, the expectation to bring in funding is not as strong. You don't need much money to do research, and grants are not as readily available. As far as the administration is concerned, if you do your teaching duty without too many issues, you can use the rest of your time as you see fit. Academic politics revolve more around personal relationships with the tenured people at your department.
Breaking up soil into large, mostly intact chunks, without turning it over, aeration. See the links above from the peer poster.
> This is a great example of why SQLAlchemy is a terrible ORM

I feel like "terrible ORM" is a tautology.

This issue highlighted in one respect a fundamental problem with all ORMs and why I despise them so much - they're the absolute worst of a leaky abstraction, and as I like to say "they make the easiest stuff a bit easier, and they make the harder stuff way harder". E.g. in this specific case they don't prevent you from needing to know the details of default column value initialization, but apparently they must have also obscured a simple duplicate key constraint to some level that it took 5 days to find the root cause of this bug.

Just learn SQL. You'll need to know it anyway even if you do use an ORM, the basics aren't hard, the skill is much more transferable than the esoteric details of some ORM, and there are lots of good libraries that make dealing directly with SQL easy and safe (slonik for postgres is a favorite of mine, but there are other similar ones).
I’m happy with Amphetamine as my Caffeine replacement but will try Owly out of interest.
Much like people who don’t have aphantasia speaking to people who do. And so forth.

Aphantasia is one that I find extremely hard to wrap my head around. The notion that somebody who’s otherwise normal can’t visualize things is really interesting. I have a friend who has it. The only outward symptom is his dislike of fiction and most TV/movies (and you’d only notice that if you knew him fairly well).
No, a lack of monitoring cost you $10K. Your app was throwing a database exception and nobody was alerted that this was not only happening, but happening continuously and in large volumes. Such an alert would have made this a 5-minute investigation rather than 5 days.

If you haven't fixed that alerting deficiency, then you haven't really fixed anything.
Excellent!

It's still possible that it could change Bluesky culture for the worse, for example if native Bluesky content devolves into shallow but high engagement Threads type content as a result of being forced to compete with it. But no use worrying about every hypothetical.
>I love that you chose to make this up instead of finding it in the code, probably because you're aware that it's not a thing they do.

It's a comment about what they do in practice, not what they do in the codebase...
This. More, smaller companies mean more duplication and overhead which can manifest in higher prices. One of the biggest factors behind market consolidation and centralization is because it reduces duplication and overhead which can increase margins and might reduce prices.

Merely increasing competition doesn't necessarily drive prices down.
This seems like something that would fit well into a tablet-sized display with a voice interface -- sort of like a conversational adventure.
If you want to skip the prelude to the attack you can skip to 47:45.

It is messed up to think this level of destruction happened in Hiroshima and Nagasaki. But in their case it was even more horrifying because nobody knew what was going on or what to do.
Yeah, we have quite literally caught bugs like this in 5 minutes in prod not bc we made a mistake, but bc a customer’s internal API made a schema change without telling us and our database constraints and logging protected us.

But it took about 5 minutes, and 4 of those minutes were waiting for Kibana to load.
"AI Wave" being -> cheaper indian workers that cannot keep up with the support tickets and move them all over emea, asia and US. Azure AI that helps with tickets cannot replace a real agent.
> In gambling you pay someone to take risk for you.

No, you don't, you take the risk yourself. You're certainly not paying the casino to take risks for you; you're paying them for the privilege of you taking risks (and losing on average) by playing their games.
It's a convenience and risk assessment matter IMO. Looking at the repo I see stars in the 1000s, issues are well addressed, and of course the source is available. Lots of persons have likely gone through the code already and no flags were raised, so it's pretty low risk to use that one-liner. I'll definitely use it, as have others, as I just want to get setup and move on with minimal effort.
Another vote for Things 3. A simple and very polished to-do app. Really helps me be organised and I wish I could find a calendar app of similar quality/vibe.

Superhuman. Expensive and delightful email.

Velja. Opens URLs in preferred browser (Safari for everything except Meet, which opens in Chrome).

PS - I’m not a developer but really like Zed as a text editor.
Well, then it's time to reinvent academic publishing. (Personally, I've found off-the-cuff personal blogs can be far more insightful than oh so many stuffy academic articles I've read. If there's one thing about programming culture I've gleaned: those of us who connect the rubber to the road actually know something about knowledge-production.)

P.s. I think you can say "ass" on the internet. Hell, in 2024, you can practically kiss ass on the internet.
The bug was in multiple subscriptions not just users. And I can't think of one non-contrived reason to do it. Even when testing the visibility/access of subscriptions between users you need 2 users, but only one subscription.
> ... a thin outer layer of negative mass ...

Brilliant! My antigravity boots are nearly here.
https://cdrdv2-public.intel.com/819723/325462-sdm-vol-1-2abc..., Vol. 2A page 3-598 (physical page 1191): "LEA—Load Effective Address"

https://cdrdv2-public.intel.com/819723/325462-sdm-vol-1-2abc..., Vol. 2B page 4-42, (physical page 1263): "MOV—Move to/from Debug Registers ... At the opcode level, the reg field within the ModR/M byte specifies which of the debug registers is loaded or read. The two bits in the mod field are ignored. The r/m field specifies the general-purpose register loaded or read."
So I understand right, there are two solutions that would have handled this before it even got to prod or at least found it in prod fast.

1. Bunch of tests that simulate exactly the scenario of signups. Hundreds of them actually inserting db records with maybe some kind of dummy stripe code.

2. Logs of the actual uuid for each person.

The second would never have been used since the tests would have caught this bug. But are important anyway.

Seems a bit rich to blame the absence of these two things on chatgpt. That’s just immature engineering practices.
Yes. These were local people who could already function in the same kind of society and probably still had their wealth, business skills, social connections, etc. Even today, those types of refugees don't need to live in tents.
New York should show the same courage
Slightly confusing rounding to 2dp. E.g. 1/8 displays as 0.13. Maybe show another decimal or display target as fraction.
This is a pretty common mistake with sqlalchemy whether you’re using ChatGPT or not. I learned the same lesson years ago, although I caught it while testing. I write plenty of python and I just don’t often pass functions in as parameters. In this case you need to!

For something like this where you’re generating a unique id and probably need it in every model, it’s better to write a new Base model that includes things like your unique id, created/changed at timestamps, etc. and then subclass it for every model. Basically, write your model boilerplate once and inherit it. This way you can only fuck this up once and you’re bound to catch it early before you make this mistake in a later addition like subscription management.
Not everything is a dichotomy
I occasionally come back to this interview because it's so beautiful. Blender is such a success story of a project putting a focus on practically improving its UX with code quality being one way of achieving that, but not the ultimate goal.
25% of the Earth's population is younger than 15. Assuming 20% of them use the internet, the TAM (not including the <15 year olds) is 80% of the world's population.

3 out of 4, or 75%, seems like nearly ever human, I'd say (though it is a matter of opinion I guess.)
> With insurance it’s very difficult to get more than the market value out of the destroyed thing on payout.

Yes, of course. But that's not what I was talking about. I was talking about whether your payout is less than the value of the premiums you have paid; it can be even if the payout is not more than the market value of the destroyed asset.

To take an extreme example, suppose you buy a house for $100,000 and insure it for that value, and the next year the house is destroyed by a covered event. Your insurance payout will be $100,000 (which will be spent in rebuilding your house), which is the market value of the house, not more, but you are certainly not going to have paid anywhere close to $100,000 in premiums, so your payout will be much more than the premiums you have paid.

Of course this situation will be very rare, but that's the point: the insurance company certainly cares about not paying out more than the market value of the asset (for the reason you give--protecting against insurance fraud), but they don't care in an individual case about not paying out more than the premiums that were paid in by that individual customer. They only care about the latter on average, and of course their actuaries get well paid to make sure their premiums are high enough to ensure that they still make money on average.
If wishes were fishes...
Rising seas force Panama Indigenous families to leave island homes
The problem with lab developed tests (LDTs) is they aren't very regulated, and in a malpractice situation, a physician could be liable if they made diagnosis or treatment decisions based on unverifiable LDTs.

It may well be that many LDTs are quite reproducible, but there's now oversight on that at the moment. You could set up a lab in your garage and start billing people out-of-pocket for the results of a Ouija board.

If you want some policy opinions from the College of American Pathologists, feel free to lodge them here: https://www.cap.org/advocacy/laboratory-oversight-and-regula...