skysight-inc/HackerNews huggingface dataset:
Technically there are more options, I agree. Practically very often these options are divided into whites (includes Asians) and people of color (includes Latinos but blacks have priority).
MrBeast on the Lex Fridman Podcast
Common Lisp is pretty cool, and to my knowledge this is the first major game title using it that is actually released.
The video is mostly about private freight rail.
A couple of years ago I was offered a team lead position after having been in development for 12 years (I regularly took on various other tasks/roles as well, that's how I got on their radar). It seemed like the natural step to take responsibility, grow, stretch, yadayada, you know what they say about personal/career goals. I completely underestimated just how much my intrinsic motivation would revolt against tasks that just don't fit, even though I could perform well enough and was commended for how I did as a manager both from my team and others. I went back to development a year later and didn't regret it. *)

One of the lightbulb moments for me was when I talked to a product owner and said that I just don't enjoy coordinating people/opinions/requirements (+ everything you listed) she replied that that's exactly what she finds enjoyable/fascinating. I understood then that there are simply limits to what you can "become" (in your essence) and I had to accept it. So I'm still just a "simple" backend engineer, I leave my mark in ways that don't involve a job title, often beyond the scope of my team. There are still moments when I observe managers and think "I can do that, too, and maybe even better, maybe I should...", but I quickly go back to remembering that I tried it once and don't need to prove anything to anybody anymore.

It sounds like you've endured this misalignment between your passions and your job for some time (how long exactly?) - don't do this to yourself unless you have some unavoidable pressures. The vested shares you mention, really worth it?

*) It was not at all this straight-forward, of course, I went through tremendous self-doubt, i.e. "why isn't this working?", just giving you the summary.
One of the founder's listed is Manu Kumar who has one of the longest Linkedin profile I've come across:

https://www.linkedin.com/in/sneaker
Don't create apps just for the sake of project structure even when models from multiple apps are closely related.

Moving models from one app to another is doable but it is a pain. It's even worse if you are relying on GFKs.
Most things are grandfathered in. In my experience, sometimes even if it's not something your inspector should technically let pass, they will if it's existing construction and things were made no worse than before.
On the 4473 form for background check in the US, the valid races are "White, African American, Asian, Hispanic". No other options, and no option to not specify. The fun part is, you can select ALL of them, not just one, and MANY people do just that.
It should not be called reverse racism either, but just racism
I find it strange that the incentives for self-departure are weaker than for non-voluntary departure. Usually it's the other way around, or maybe just where I come from. What's the logic behind incentivising people to not quit?
In Spanish it's fine to say "Bienvenido" even to women. It's a generic greeting (used in the plural as well, as far as I know... unless you want to be fancy and say "Bienvenidas y bienvenidos", which is rather an idiotic trend).
The US seems to be obsessed with race.
Would you mind expounding upon this comment? Against what goal did it fail to deliver?

I think I was more hopeful a decade ago than I am now that we'd see more decentralized manufacturing and more home-grown innovation, but I'm not sure that these were ever realistic expectations.
better than nothing, in my opinion. At least they were considered.
Except if you know that for some hypothetical demographic A and demographic B where all applicants are equally qualified you would expect the hiring to equally reflect both demographics.

If it doesn't, you have an issue. The only way to know for sure is to measure.

E: To be clear, assuming equally qualified candidates, you would want expect hiring proportions to match the same A:B ratio as you get from applications.
Because HN is basically filled with Boomers at this point, maybe most commentators don't realize that there are different segments of young people.

Those who were in the Class of 2020 and above got FUCKED big time hiring wise.

Those who were in the Class of 2008-2011 got FUCKED big time hiring wise.

Everyone who started their career between 2012-2019 (like me) have had an amazing ride. We could jump companies at the drop of a hat and 1.5x-2x our TC, stocks were constantly rallying, and it is this group that started to enter middle management and/or build startups with YC. And it is this group that has never experienced a real recession.

PS. What is happenning in tech right now is nowhere near a recession. I've seen the stress my parents had during the Dot Com Bust and 2008. What's happening right now is nowhere near that bad.
In court it's better to not know since it's harder to prove intent.
I largely agree. But I thing the goals should expand.

We have removed the barriers to design and we now have a huge collective competence in design work. But now we have a bottleneck in turning that education into progress.
Pedantry time!

A million people building GPT models means that one in 8000 humans on earth has built one. That seems wildly off.

Linkedin has about 100.000 profiles of data scientists. Assume generously that the actual number is 10x higher. Not correcting for the fact that a data scientist isn't always a machine learning expert, etc etc, there's just no way every single one of them even KNOWS what a GPT-like model is.
I think "asking for pronouns" as that user mentions seems like a reasonable place to land. It has a clear potential use, and isn't confusing about what it is asking.
Diamond-dependencies are hard to work with, and so we forbade them. Specifically, you can't revert an individual migration, you just specify your desired "target" to roll back to, and therefore you can't unapply a single branch of a diamond dependency. This means if your second branch of a diamond dependency breaks the DB, but your app depends on the first branch, you're SOL and are now manually running SQL to fix your production DB. (Can you tell I'm speaking from experience here? :) )

Your migration code uses the model classes, but the migrations are using a rehydrated version of the model that doesn't include any methods; another footgun. Basically you need to copy in any logic that you're using into your migration file, or else that migration's logic will change as your code is refactored. You might naively think that because `model.do_the_thing()` works now, the migration is somehow pickling a snapshot of your model class. It's not.

Because of the above, you should really squash migrations frequently, but it's a big pain to do so -- particularly if you have dependency cycles between apps. ("Just Say No to Apps" is my default advice for new Django developers. If you have a real need for making a bit of library code sharable between multiple different Django projects then you know enough to break this rule. Within a single monolithic project, apps just cause pain.) Squashing migrations quickly gets to some extremely gnarly and hard-to-work-with logic in the docs.

Moving models between apps isn't supported by the migration machinery; it's an involved and dangerous process. One idea here that might save Apps is if you manually remove the App Prefix from your "owned" / internal apps; if I have Customer and Ledger apps, I don't really need to namespace the tables; `user`, `information`, `ledger_entries` are fine table names instead of `customer_user`, `customer_information`, `ledger_ledger_entries`, a normal DB admin would not namespace the table names. You neeed the app namespacing to make it safe to use someone else's apps, but I think namespacing for your own apps inside a single repo is harmful.

I find the migration framework to be worth using, but it's definitely got some sharp edges.
> Most employees at Kraken don't know what the CTO looks like. He never turns the camera on during meetings and as far as I'm aware hasn't showed up to the in person events. He wrote most of the legacy backend.

> This was mostly a curiosity though. None of the other points apply to him. He was professional.

Call me "old school" but the CTO of a company valued at > $10B that manages who-knows-how-much in terms of customer assets shouldn't be able to do this. Frankly, it's ridiculous - can you imagine the CTO of Bank of America being an avatar/unknown? Seriously. Where is an adult to say "turn your camera on, show up to stuff, use your real name, or you're out"?!?!

Regarding the "sugar babies" and what-not - yes. Just another data point that demonstrates how ridiculously shady and so far beyond acceptable behavior, practice, and standards the space is.
I'll bet that Uber has a lot of waste and bloat that the new guys could avoid

I've heard some horror stories about a rideshare rider paying inflated surge prices while the driver just gets the normal rate, for example. (not sure which service this was)

Theoretically it should be dirt cheap for Uber to leverage its customer service and app for any new market to compete on razor-thin margins, but in practice they could be wasting most of that money and leaving the door wide open to a really lean competitor
> tech valuations have come down because the Fed has raised rates which long duration stocks like growths tech cos are extremely sensitive to.

That's actually not accurate. NTM revenue multiples for software companies peaked at ~12.0x on average in October 2021. The first rate hike in this cycle happened in March 2022.
Generally, no, this isn't the case.
I was going to comment controls looked like the mega hit "Celeste" and then I found this comment on HN, from 6 months ago, by the dev of Kandria:

"I wanted to create something bigger, and had just finished playing through Celeste"

Ah that explains it! Congrats on shipping on Steam!
I've used networkx as an intermediate graph layer in web apps before talking to a db, which seemed redundant, except being able to reason about my data as a graph was everything I needed.
The first we did with UAC was disabling it. Because nobody did care.

So you can throw the best security at users for free. Some dud will disable it because his powershell script is not working anymore.
Eons ago I've driven one such forklift through a high rack warehouse for a year. It had 2 batteries, weighing about 4 metric tons each (Lead-Sulfuric acid). They made it about 4 hours (half shift), then had to be exchanged with another forklift at the loading station. Always had to check for levels of sulfuric acid, watch out for oxyhydrogen/electrolytic gas, and whatnot else. But was fun to ride, because up to 35kph on the ground for the whole 12 metric tons, wobbly cabin/platform at 12meters up, and deadly fast fork. So...very niche, I guess?

Another thing similar to milk floats comes to mind from the time the railways used to deliver post and packets. Those things always trundled along the platforms, to where the post/baggage car would be. Sometimes with several small trailers.
Higher interest rate was the catalyst to recognizing reality, not so much a fundamental shift of financials.

Many of these companies were losing money and their future imaginary positive cash flows were wishful thinking given their business models. Higher interest rates accelerated loss in value as the speculative sentiment shifted to a more risk-averse posture once the market accepted the reality that was always there: these companies never exhibited the ability to make any money, plus they were cannibalizing themselves due to the extreme competition from other startups fueled by the huge amounts of money vc’s were able to gather during the zero interest rate mania.

Discounting future negative cashflows was always a foolish game.
Many of the examples on that website are not from English-speaking countries. "diverse" and "female doctor" are typically German, and "male" = "bad" was likely mistranslated from Italian (or another Latin language)
Been at the company 3 years, this guy Manu was there in the early days, but he is pretty much a ghost since the past 7 years. He's moved on, I think he is a VC now.
Which means gender should just be 3 choices, he, she, they. That's it. if a singular pronoun is used, its just changed to, "The person".
Not just pronouns, but nouns and adjectives too, and in some languages verbs.
Unless things have changed recently, Netflix neither has interns nor does it hire entry-level engineers.

Maybe that indeed has changed recently, but I am yet to find any indication of that.
Some countries have labour laws with gender-specific rules.
I'll believe this when I see successful startup utilities cropping up all over for the low capital investment of buying a field and filling it with solar panels. Hell, I'd settle for seeing the existing utility companies doing this en masse.
You microservice can be easily tested.

But then you may end up with - is your whole system testable and how do you do good integration tests?

Right now I work in a pure microservice architecture, where there are no proper system or integration tests. And we had minor bug fixes break things spectacularly.
No, I actually went off the first sentence:

"So which report makes an organization less racist"

So that implies that org B is more racist(because it hired zero brown people) - is that not the conclusion the author of the comment wants us to reach?
Kinda, but also no. It depends on a language. For example in Polish you'll say "has done" as "zrobił" (he), "zrobiła" (she), "zrobiło" (baby, or it). You don't get to play fancy with pronouns there, because the verb itself is modified. (Also to make things fun, objects are gendered too, so when speaking you need to know that the fridge is female and a table is male)
A lot of it has to do with population statistics, for better or for worse the USA is fixated on having available data on all racial discrimination (make sense given the history of the country). I do agree that the categories them selves need some revision, however, unlike the forms here at genders.wtf, you can usually opt out of answering the racial category, which makes it infinitely better.
I was about to ask the same thing. Why would someone leave voluntarily for worse benefits?
In Taiwan, electricians and plumbers are the same occupation.

When you're getting your certifications, you have to get both.

You can specialize in one, but you have to know plumbing and electrical work to pass.
To give a concrete example, VAAPI Haswell integrated graphics, peak CPU usage:

mpv hardware H.264 1080p60: 3% CPU usage
mpv software H.264 1080p60: 20% CPU usage

mpv hardware H.264 4K60: 96% CPU usage
mpv software H.264 4K60: 80% CPU usage

There comes a point of diminishing (or in this case, negative) returns. A bit more subjectively, the H.264 software rendering at 4K60 also felt smoother.

I'm using H.264 as it is hardware accelerated on this platform.
Are you talking about why Apple has so much cash in Ireland?

Why can't Apple buy its stock from Ireland without paying more taxes?
I wonder who the squid face guys are and whether they invented the quote. It is awesome.
I'm not sure where in EU you live, but every instant water heater, stove, and many semi-professional workshop devices require 380V. At least in Germany, 380V is standard for such devices and available in every household.
Your theory is that, for example, turning people into property based on race was not racist? If so, I don't think there's much point in a discussion here.

For those more reasonable who want to know about what anti-racism is opposed to, I'd suggest reading Loewen's Sundown Towns, Kendi's Stamped from the Beginning, and Mills's The Racial Contract as beginner-friendly looks at the system of racism, its historical and intellectual roots, and how it all played out historically.
Yeah, it started out with just Celeste mechanics before everything else happened.

Thanks!
Well, Fortran is a domain specific language. It does floating point arithmetic for engineers from the physical sciences. It does that _really_ well. It does other things less convincingly.
I was surprised to find that an assertion I read on here some time back—that this sharp distinction is quite recent outside of a small slice of academia—was basically true, when I looked into it. When I was taught this in college in the mid '00s I assumed I'd just been ill-informed earlier and that those definitions went back decades, if not indefinitely, but in fact it had only just spread to the rest of the humanities, a few years before it was taught to me.

I do think it's turned out to be useful and think it'd be fine if that caught on, but do remain uncertain exactly how "mainstream" one may regard this usage—so, how useful it is for communicating with a general audience—especially internationally. Pretty much everyone on e.g. Twitter understands (if not accepts) the distinction, sure, but I hesitate to guess what a broader poll might reveal.
Diversity numbers show up on reports that affect ESG investment. ESG funds will buy more of your company’s stock if you have a higher percentage of women on boards, for example, and other metrics.

And some positions are only offered to diverse candidates or candidates from a particular subgroup, like LGBT etc. Last year, one of the roles I had to fill was diverse-only. Only applicants of color were allowed to apply for the role.
As a Christian, the term is absolutely ridiculous.

I'd prefer to be called German Irish (or some other identifiable family history origin) or American. White or Caucasian isn't a nationality or race.
How I can plow a field using a website.
Flexport (YC W14) Lays Off 20% of Its Employees
FWIW, Google says 540 electrical deaths per year in Europe vs. 200 per year in the USA. Whether that's from lower voltage or more GFCI is anyone's guess.
I think you'd also want to check the NaN route is actually faster in practice on the CPUs you are targeting but beyond that as long as you're willing to maintain the dedicated codepath for it (or are fine with saying it only runs on specific targets) then you should be good.
If you collect demographics of employees, it tells one story.

If you also collect demographics of applicants, it may tell a different story.

If your employee demographics look skewed, but they're consistent with applicant demographics, you have an easy out when accused of ism.

Of course, if you collect the information, you might also use it for ism purposes. Or you might just lose or discourage applications from non-favored people. It's hard to show.

(It also doesn't help that the federal categories feel poorly chosen and ill-defined)
Might you be using tax software that gives you choices? The 1040 has a free-text entry for this, and the instructions don't state that you must enter anything in particular.
If this is distressing for you, you may need help.

What is enough to know about this, that it is blended paste, which means it gradually becomes composed of the cheapest available ingredients as the cost is continually lowered, while the experience kept up using extenders, like bologna for example. This is about this kind of a food you have to know. Happy distressing!
I have a lot of power surges in my area. Recently, the old power shut off, then power back on in 3 seconds thing happened - and the surge was enough to pop my fridge motors and cause a $900 repair.

I upgraded them to not only a surge protector, but this little neat shut off device. It's a device that goes between the fridge and the wall outlet, and basically if for any reason this device loses power - it shuts off the power to the powered device for a minimum of 3 minutes. This way the power can blink 100 times in 3 minutes, and my fridge won't have to eat 100 surges. It will just happily sit off for 3 minutes, and then come back on.
The CD-Rs were around fifteen years old, stored in plastic boxes in my house (in rooms with HVAC). A couple of them failed in a set of twenty or thirty I think. I do have 20+ year old CD-Rs that still work fine though.

For hard drives I have had ones that were mysteriously corrupted after being unused for six years or so, but others that were readable after fifteen. It partially is the luck of the draw.
PillCam Capsule Endoscopy System
It's like you only read the first sentence of the parent comment. The only reasonable response is to point you right back to it.
This is what they did with their cellular modems
So how would you run an instant water heater or electric induction stove then? Every apartment and house I've ever lived in had 380V three-phase right to the kitchen, to the bathroom, and to basement rooms (e.g. for prosumer workshop tools).
I don't see that distinction being made. The counter argument is things like libraries vs microservices. Those articles ignore the common case that probably is true for 99% of the apps - we live in a service based architecture. The Internet is service based. Everything an app talks to is service based. So quit arguing about it.

Microservices don't address any of the issues I ever faced or people on Hacker News talks about like mixing languages, building code around organizational structure, isolating faults, etc. Microservices are way to granular to address those issues well. The only time I ever wrote a microservice is when I had to wrap some stupid SiteMinder binary apache mod blob.

Also, almost nobody writes a monolith, if they say they have a monolith they are probably lying. Do they have a database? S3? ERP, CRM, blah blah blah. Nobody in their right mind would build microservices, that is nuts unless they have some really special architecture. So can we quit the endless debates about stuff and instead focus on the real issue: how to build robust and maintainable service architectures? How to partition systems properly so you can manage avoiding having conflicting data? Eventually consistent systems, etc.

This is as dumb as the CISC vs RISC debate I lived through in the 90s.
But you're not the one asking. Understanding diversity is a datapoint groups/services/people would like to know.
It's a word we should all stop using to mean "white". It's inaccurate, non-descriptive, and historically evil.
Additionally, in terms of the streamlining nanoGPT porports, HuggingFace's implementations play nice with optimization techniques such as ONNX/TensorRT, which will give you better performance than anything PyTorch-based even if minimal.

That doesn't mean an ONNX-ed nanoGPT won't be better, but the field of optimized text generation isn't as new as people claim.