skysight-inc/HackerNews huggingface dataset:
> I think Ben’s point is that Michelle went to prison for a crime she didn’t know she was committing and had checked [citation needed] with PwC.

The article is written that way, but that view contradicts all the facts. As summarized in the other comments:

- Really large numbers of executives were guilty of the same conduct described in the article. They didn't go to jail.

- Michelle was not charged with anything related to the conduct described in the article. She was charged with evading her personal taxes.

It seems unlikely that she had PwC audit her personal taxes. So the main point of the article seems to be that Ben Horowitz wrote it without bothering to learn what had happened.
> a better alternative would instead be something akin to Dockerfiles where you assert what packages you want to be installed on top of a base system, and if you want anything changed you update the dockerfile and rebuild the whole shebang.

Something like Packer?

You are right that there are hidden pitfalls. But they shouldn't be a great deal if servers are cattle. A lot of corner cases are related to trying to manage servers that live forever. This shouldn't really be done in 2021 except in rare cases.

> i'm imagining a system where the local filesystem is more or less immutable and work is saved to separate filesystem

CoreOS worked like that. Immutable filesystem for the system itself. It also had a secondary "mirror" of this filesystem that was used for upgrades (and as a fallback in case boot failed). New stuff would either come when the instance first booted up (cloud-init), or via system upgrades.

They were acquired and so my experience with them ended there.

There's also https://nixos.org/
Yes, it is generally a good thing to be able to communicate while you're working on a problem within a group.

But rarely does someone get posed a difficult technical design question on the job and on the spot where they've had little or no opportunity to think about it ahead of time. Usually there is a ton of contextual knowledge leading up to those group discussions vs. being asked a question in an interview and then be expected to perform at that same level.
How would rain be different on an alien world?
wow, plastic everywhere
'Typographic attack': pen and paper fool AI into thinking Apple is an iPod
> If we consider the expected utility of taking the bet at any point in time given some wealth W we obtain a positive utility (0.5 * 1.5W + 0.5 * 0.6W = 1.05W)

No. That is not the expected utility in the usual EUT solution.

In the usual EUT solution (with the usual logarithmic utility that would be used in a textbook problem like this one) the expected utility is 0.5 log(1.5) + 0.5 log(0.6) + log(W) which is lower than the expected utility of not playing log(W).
Just because it isn't a state secret doesn't mean you have to put the name on blast.
Unless it's completely dead, every pizza shop runs multiple orders at once and their drivers are in and out swiftly. The food stays fairly hot thanks to commercial heat bags.

For the delivery apps, the driver has to possibly wait in a line, check it out, then deliver the order a single order at a time.
Right, this was a famous SVG demo example from 2004 stored on http://www.croczilla.com/svg/samples/svgtetris/svgtetris.svg for many years
I'm in a similar boat, story time!

$current_company runs internal events and makes noise about leadership bonuses being tied to diversity targets. I'm part of $targeted_minority so I usually show to the relevant zoom meetings. There's recurring meetings but no actionable items emerge from these meetings.

In a way I'm alright with this because some people need the meetings as a coping mechanism but it doesn't fix the underlying problem; bringing in more $targeted_minority does that. What's missing: data about internal hiring/promotions/referrals showing whether $targeted_minority has a funnel problem. Maybe those reports are above my pay grade at this company. For some anecdata I've made over 30 referrals and not one has been hired. At $previous_company I made 6 referrals that turned into 4 offers and 3 hires (and one of those referrals walked away before being made an offer). Sure, $current_company has higher standards but I'm a bit incredulous at the success rate gap.

Maybe one day they will give up and pad the numbers with marketing/HR folk, etc. and pat themselves on the back. Maybe they already do that and I just don't know about it.
On the other hand, every time I've ordered papajohns [directly from PJ] I get a doordash driver, interestingly.
Same problem with the building standards in Australia.

Same problem in Australia with the AS/NZS standards. I've been having problems with my whiteset plaster, which is like a liquid applied white plaster surface used on almost every home here in Western Australia.
Mine was done incorrectly, I had to purchase two different $250 standards to understand how it was done wrong, how it should behave, how it was tested, in order to file a complaint. It may not surprise you part of the reason it was applied incorrectly is because not every trade has a copy of said standard.

And then even once you purchase it, it's a "one user" watermarked PDF you're supposed to only have 1 copy of and there's lots of harsh warnings about that, so even those that have it and scared to run around with it.

It's a crazy situation. Because this is legislated stuff for building. As a consumer it's very expensive to inform yourself on these things. If you wanted to inform yourself on all aspects of a build it would get expensive fast.

It's also difficult for me to publish and discuss this information in the public domain to help other consumers having the same problem, as the limits of how much text I can "copy" appears technically set at 0 even though it's standard to "reference" it. But it's very easy to mis-interpret the standard if you don't read things in context.

If the standards are effectively government legislated they either need to be government funded (this makes total sense to me) or the price needs to be much more token, 10 dollars, with much less draconian access. But at that price the government may as well fund it anyway.
What kind of backend development do you currently practice? Language? Stack?
I was certain that the Ada language spec - an ISO standard - was made freely available. I was mistaken. They only make an old version freely available. [0]

I get the impression the standardisation of Ada has been broadly successful in providing assurance of conformity, [1] but that still doesn't excuse paywalling the document.

[0] https://en.wikipedia.org/wiki/ISO/IEC_8652

[1] https://www.adaic.org/ada-resources/standards/ada-95-documen...
Not everyone here has actively followed HN since the last time it was posted (2018). I found this post to be interesting.
This is the kind of thing I think of when people talk a out meritocracy. Somehow social studies have warped the perception of meritocracy to mean "anti my group" by selecting examples that aren't meritocratic.

Just look up "meritocracy dead" on a search engine of your choice. It's pretty minds boggling what people want to replace the goal of meritocracy with these days.
I bet it was popular due to the ease and methods of removal considering nobody had heard of HIV yet :p
Chigorin and Salwe were both born in the mid-1800s. With the prevalence of chess computers for training and studying, the amount of strength you need to play at a top level is much higher these days.
You can as long as the size of your box is significantly smaller than the size of your warehouse. This is in fact the general case.

It's even truer if you're considering larger expansions; increasing the length of your warehouse by 200% will mean you can store 200% more stuff regardless of how awkward the original fit was.
The top comments to this post are all men saying how they were discriminated against, or how she did something wrong.

Fucking hackernews man, I rarely visit here now, its toxic.
As a hiring manager who was once a developer who was absolutely terrified of the typical whiteboard/algorithm interview, take home assignments are my preferred method to judge tech ability. However, I often feel it's not fair to ask the candidate to invest their personal time in the interview process. So I'm glad to see some affirmation that it's the preferred method for at least some.

When I have done take homes, I've tried to keep the time requirements minimal and the project itself simple and hopefully even a bit fun. It might even be as simple as "here's a REST endpoint, pick the JS SPA framework of your choice and do something interesting with that endpoint." Even just a simple form with clean code that builds will be enough to get you hired if you're otherwise a good candidate. Because in the real world, most of of us are just building CRUD apps.

All that said, I only bother with this if the candidate is incredibly green. For anyone with decent experience I generally assume they're not lying on their resume, and an hour long chat about their projects and technology interests will tell you more than any technical assessment.
It absolutely does. One of my first programming interviews, post MSc graduation, was essentially a 3hr whiteboard interrogation. I should have walked out after an hour as, in retrospect I was stuck like a rabbit in the headlights, unable to think straight as this unpleasant interviewer essentially tried to dismantle every angle of my understanding of a subject. I was gripped with anxiety and lost confidence. He claimed he was just trying to find out the edges of what I knew but boy did he do it in an unpleasant way. Interrupting, making slightly snide comments, being plain rude at times. I think he was either an actual jerk or maybe just not very good with people.

Anyway, other than that interview where I was super stressed and tanked it, all my others have been nothing like it. Just goes to show how stress and a loss of confidence can wreck your chances.
I've seen this plenty of times. I even heard one manager at a happy hour say, "Thank god I finally hired an ABC and an XYZ, I can finally start recruiting based on talent again". This may be an extreme example, but still.

Unfortunately when you have affirmative action or hiring quotas, you inadvertently to create a culture where the diverse individuals are seen as less skilled and less qualified even when many of them would have gotten to the same place without the quotas.
Stuff nightmares are made of: "Woke up in a sweat, I got GC'd!" ... ouch.-

Were it to be Rust, at least, I'd guess you'd know - death sentence style - what is to happen to you :)
Hmm, he certainly is working on automobile deaths by releasing this nonsense, and giving unsuspecting masses confidence that they should not have.
If they were performing as their CEO represented, the cars would be have driving themselves cross-country to delivery themselves to customers years ago. The time to have them up about lying what would be delivered and when was a looooong time ago.
Have had a former female coworker report a similar experience with IBM more recently than yours, pretty much search and replace "native american" with "female engineer". It was her first career out of college, and she just was not assigned very much duties in her actual team, and her management were far more interested in her DEI work than her engineering work. After a year of going "well maybe they just think I'm too junior for interesting work", she left for the company where we worked together.
We use a 3 step process, sans whiteboard:

1. First interview, the candidate interviews us. What market we serve, what our development processes are, what our technology stack is. If they express interest by being prepared and asking good questions, we send them

2. a programming task. Choose 1 of 5 tasks. The tasks are not abstract problems or puzzles, but come out of the designs we've implemented. We ask for 100 lines of code and not more than 2 hours. They take as much calendar time in days as they need, most have full time jobs, and let us know when you're done. The candidate then comes back, typically in 2 to 7 days and hosts a code review in front of our team. I give strict instructions before hand: The purpose of the review is to learn how they thought through the problem and how they solved it, not to criticize their style and approach.

3. If we decide we like them to this point, the third interview is with managers from other functions. How well does the candidate communicate, come across to non-developers, express interest in the company and role, etc. It's a check point to look for concerning weaknesses, as well as get buy in from the broader organization.

We like this approach because it allows the candidate to code in a much more natural environment. They can take the time they need and comfortably solve. No one spends their professional career coding on a white board. This approach so far has yielded excellent results. We ask developers how much time they took in the programming task and why they chose the one they solved. The programming task is telling, not in the quality of their code and how long they took, but how much did they get into it? We have had the range from candidates who did not complete it at all and opted out, to candidates who stumped 40 year veterans with elegant code. In every case, we learn how well they can express their thoughts, and importantly, their level of love for the discipline. This is as important to me as any other attribute.
The absolute worst is when interviewers keep interrupting the candidate. It shows a complete lack of empathy and it shows that the interviewer wants the interviewee to answer the way the interviewer thinks it should be answered.

I am very mindful of this when I interview and I think it’s my job as the interviewer to strain myself to try to understand the interviewee, not the other way around. I quietly try to understand my interviewee and don’t interrupt unless there’s a real reason since I want her to think freely and not feel stressed.
Hm, thanks for correction. I'm definitely not an expert. I just vaguely remembered that it was something that was at one point being legally challenged, so looked it up and found those articles, with headlines including:

"Supreme Court rules that building codes cannot be copyrighted"

"Construction code purveyor calls Supreme Court's ruling that annotated code can't be copyrighted 'monumental'"

Are you saying those headlines were overstating?
Adding a HN bio also helped, thanks.
Also https://eprint.iacr.org/, https://www.biorxiv.org/, and https://www.ssrn.com/. Probably others too.
If anyone is interested, below is a relevant portion of the court's analysis from the Up.Codes case in the original document linked to at the end of the Techcrunch article above. They lay out criteria by which a copyrighted work is considered "the law", giving the public free access to it:

"the principles that guide the Court’s analysis seem relatively clear. The law is in the public domain, and the public must be afforded free access to it. SeePRO, 140 S.Ct. at1507. That a law references a privately-authored, copyrighted work does not necessarily make that work “the law,” such that the public needs free access to the work. CCC, 44 F.3d at 74. However, a privately-authored work may “become the law” upon substantial government adoption in limited circumstances, based on considerations including (1) whether the private author intended or encouraged the work’s adoption into law; (2) whether the work comprehensively governs public conduct, such that it resembles a “law of general applicability”; (3) whether the work expressly regulates a broad area of private endeavor;(4) whether the work provides penalties or sanctions for violation of its contents; and (5) whether the alleged infringer has published and identified the work as part of the law, rather than the copyrighted material underlying the law."
The whole field seems engineered to prevent competition.

It is. After all it is not in the interests of anyone who is established in the field to make competition easy.
Honestly, there is too much representation in Silicon Valley companies from young people with pretty radical progressive politics and SJW philosophies, and too much lip service from those companies toward those causes.

More older male devs in Silicon Valley would be a breath of fresh air. Please make the switch, we need more people like you here!
https://news.ycombinator.com/item?id=10178989

This site best viewed in Lynx or otherwise without JavaScript.
The linked article says the exact opposite of what you are claiming:

> The issue doesn’t appear to be girls’ aptitude for STEM professions. In looking at test scores across 67 countries and regions, Stoet and Geary found that girls performed about as well or better than boys did on science in most countries, and in almost all countries, girls would have been capable of college-level science and math classes if they had enrolled in them.
How does that overcome systemic bias, eg prevalent poverty in many minority groups. The poor don’t have resources, wealth or contacts, to become a super coder/manager/whatever so they don’t make it into your applicant pool based on skill alone in the first place.

The cycle continues.

Breaking the cycle is hard. You could target low income children but that leaves everyone looking for jobs today in the cold, etc etc.

It’s a tough nut to crack but trying to fix historical bias isn’t necessarily a bad thing.
I don't want an always connected car; I want it to be completely able to work off the grid.
To save anyone a click, these are from a Joe Rogan interview.
Not to advocate for either approach, but surely MLK was describing an end goal, not a means for getting there, no?
> Very cool! Independent of the cool use of `aesenc` and `aesdec`, the features for skipping ahead in the random stream and forking a separate stream are awesome.

Ah yeah, those features... I forgot about them until you mentioned them, lol.

I was thinking about 4x (512-bits per iteration) with enc(enc), enc(dec), dec(enc), and dec(dec) as the four 128-bit results (going from 256-bits per iteration to 512-bits per iteration, with only 3-more instructions). I don't think I ever tested that...

But honestly, the thing that really made me stop playing with AESRAND was discovering multiply-bitreverse-multiply random number generators (still unpublished... just sitting in a directory in my home computer).

Bit-reverse is single-cycle on GPUs (NVidia and AMD), and perfectly fixes the "multiplication only randomizes the top bits" problem.

Bit-reverse is unimplemented on x86 for some reason, but bswap64() is good enough. Since bswap64() and multiply64-bit are both implemented really fast on x86-64-bit, a multiply-bswap64-multiply generator probably is fastest for typical x86 code (since there are penalties for going between x86 64-bit registers and AVX 256-bit registers).

---------

The key is that multiplying by an odd number (bottom-bit == 1) results in a fully invertible (aka: no information loss) operation.

So multiply-bitreverse-multiply is a 1-to-1 bijection in the 64-bit integer space: all 64-bit integers have a singular, UNIQUE multiply-bitreverse-multiply analog. (with multiply-bitreverse-multiply(0) == 0 being the one edge case where things don't really workout. An XOR or ADD instruction might fix that problem...).

---------

> This is a great idea. I wonder if we could speed up LuaJIT even more by SIMD accelerating the GC's mark and/or sweep phases...

Mark and Sweep looks hard to SIMD-accelerate in my opinion. At least, harder than a bump-allocator. I'm not entirely sure how a SIMD-accelerated traversal of the heap is even supposed to look like (aka: simd-malloc() looks pretty hard).

If all allocs are prefix-sum'd across the SIMD-units (ex: malloc ({1, 4, 5, 1, 2, 3, 20, 10}) == return (memory + {0, 1, 5, 10, 11, 13, 14, 34, 44})... for a bump-allocator like strategy... its clear to me that such a mark/sweep allocator would have fragmentation issues. But I guess it would work...

Semispace collectors innately fix the fragmentation problem. So prefix-sum(size+header) allocators are just simple and obvious.

--------

On the "free" side of Mark/sweep... I think the Mark-and-sweep itself can be implemented in GPU-SIMD thanks to easy gather/scatter on GPUs.

However, because gather/scatter is missing (scatter is missing from AVX2), or slow (AVX512 doesn't seem to implement a very efficient vgather or vscatter), I'm not sure if SIMD on CPU-based Mark/Sweep would be a big advantage.

------------

Yup yup. Semispace GC or bust, IMO anyway for the SIMD-world. Maybe mark-compact (since mark-compact would also fix the fragmentation issue).

The mark-phase is just breadth-first-search, which seems like a doable SIMD-pattern with the right data-structure (breadth-first is easier to parallelize than depth-first)
> But it was always clear to me.

So when the CEO went on stage and said cars would be self-delivering via fully autonomous driving it was obvious to you that his statement was a lie?
As a white, non-god developer who just went through a job hunt, I had offers from big companies. I don't think this is an issue in any manner.
I agree, though sometimes it's not actually bribery. If a company, for example, offers inmate telecom services to a prison, and offers to do it at "no cost at all to the state" or "revenue share", it sounds attractive. Of course, that means "exorbitant costs to the prisoner's families".
There's something quite like this in US law. If you are citing a case in a legal brief, you need to make sure it hasn't been overturned along the way, so you 'Shepardize' it. From Wikipedia [0]:

Shepard's Citations is a citator used in United States legal research that provides a list of all the authorities citing a particular case, statute, or other legal authority. The verb Shepardizing refers to the process of consulting Shepard's to see if a case has been overturned, reaffirmed, questioned, or cited by later cases.

[0]: https://en.wikipedia.org/wiki/Shepard%27s_Citations
If pickles are called gherkins, what are gherkins called? Or is there no separate word for them?

(In the US, a gherkin is a small pickled cucumber. A cornichon is a type of gherkin, but there are other types.)
Part of me thinks planes with a stable and fast connection would be amazing.

The other part of me will mourn the days when a plane flight was one of the few places you could be expected to be totally unavailable.
I feel like delivery has the promise of better packaging alternatives than in-person shopping ever will. It'd be easier to have more bulk/unpackaged items, less packaging, less attention-grabbing packaging/displays, and less wasted "impulse buy purchase" space, if no non-professionals were allowed in the store. Professional shoppers aren't going to mishandle bulk items (or lick them and put them back, which I have seen happen with kids in grocery store bulk-goods sections).
Yes, in air freight weight and volume are independently significant.

But I'm not saying that all multidimensional data can be losslessly reduced to a one-dimensional value. That would be crazy! the point of my comment is that it isn't true that -- as the parent comment asserted -- it is impossible to usefully report multidimensional data with a one-dimensional value. To the contrary, it is quite possible that the multidimensional data adds zero value over the one-dimensional summary.

Some multidimensional data can easily be losslessly reduced to a one-dimensional value. We can easily make a much stronger claim -- all one-dimensional values are "reductions" of other, multi-dimensional characterizations of the same data. But they're not all useless! The number of dimensions you use to describe data is an editorial choice, mostly unrelated to the raw facts.
I learned Z80 assembly in 1987, x86 assembly somewhere '91-92 can't exactly remember but it was in '94 when I met IBM Assembler (yes they called Assembler language which is also confusing) and I was like "what is this sorcery where assembly has an instruction to insert into a tree".