skysight-inc/HackerNews huggingface dataset:
The thing is we want to be surrounded by people who see development as a calling, and not just a safe career.

That cycle has been going on for years. Now, there are so many companies that are essentially writing variants on the same software over and over again that demand is dictating the shape of the field. The shape of the industry. “We” are all industrial designers in a world that just isn’t that enthused.

If we wanted this other world that we keep interviewing for, then it’s not a matter of not enough programmers, but way too many. They’re cheap enough that people everywhere are reinventing wheels instead of assembling off the shelf components designed for that purpose.
22/02/2020 Update:
- I have fixed some typos.
- I have fixed some compatibility issues in RHEL distributions using SELinux.
- Improved the exclusion of addresses that should not be routed via TOR.
- DNS port 53 to 5353
- Started a parallel project to support other Unix like distributions like BSD.
The only thing more boring than government work are tired lazy stereotypes accusing government employees of incompetence/lazyness/wastefulness.
It seems that the OP linked to the /sites page, rather than the landing/home page. Can this be corrected? The linked page is pretty bare and has almost zero information.
The problem with Scroll is we trade one evil for another: instead of ads and trackers, we get legally dubious "AS IS" clauses in Terms of Service, and censorship-laden arbitration clauses that cannot be subject to oversight.
:/ I've got strong opinions here, even if they might be a bit radical to all jam in one post. It is likely that the reforms of the 1970s broke the US [0] and if it wasn't them then something changed (maybe access to cheap oil, maybe other nations recovering from WWII) that really broke the environment where the US understood how to be successful. The US has to ask itself how effective its 'capitalist economic system' really is.

* It has a higher tax:GDP than China [1]. That is to say, the nominal ratio of money siphoned into government vs money retained by private citizens is less free than China's. There isn't really a point of comparison here because the two countries are so different (eg, China has state ownership) but there is some shock value in just how large the US government is in the economic sphere.

* It has socialised access to capital. Large banks have the power to create new money and the US government steps in during crisises to pick winners and losers when the lenders are proven to be incompetent at taking risks (eg, 2008 era). China does this too, but the battle becomes which government is more astute at supporting bad risks rather than which system is more effective. China is probably more long-term strategic, using the money to build useless infrastructure instead of the US using money to uselessly boost asset prices. This point is a huge deal to me and really undermines my faith in the effectiveness of free markets used elsewhere in the system.

* A complicated IP law system where people are prevented from doing things they know are good ideas. China largely ignores this system.

This article teases at one point; which is socialised access to capital favours companies that are too large to compete but can negotiate for loans and are known to government/large investors.

[0] https://www.epi.org/publication/charting-wage-stagnation/ & EDITED from 1980s, a decade too late.

[1] https://en.wikipedia.org/wiki/List_of_countries_by_tax_reven...
PR at first sounds like a great idea. I used to support it.

Watching how it plays out in Europe is instructive. What you see in PR systems is many parties, all of whom enter Parliament and none of whom have a majority. This leads to:

- Long delays whilst they try to form alliances with each other, often unsuccessfully. Belgium went without a government for 541 days. Having no government for three-six months is quite common.

- Alliances that make no sense at all and make a mockery of the parties political manifestos, e.g. right wing and left wing parties forming an alliance then not being able to actually do anything because they fundamentally don't agree on much. Germany used to have one of these. Then they attempted to form an alliance between the Greens (hard left socialists) and their libertarian party! As you can imagine, that didn't last long.

- A very similar issue is that parties can win a lot of votes and still get no influence, because the other parties hate them so much they refuse to ever form an alliance with them. This happens to conservative parties a lot. For instance in the Netherlands the PVV is the second biggest party by vote share, but every other party refused to enter an alliance with them so their voters have no influence on the government. The alliance required to achieve this took 208 days to put together and 225 to formally start work in the cabinet, so the Dutch people were without representation for more than half a year because their politicians refused to contemplate compromising with the second largest party.

[Modified] first past the post as used by the USA and the UK isn't perfect, but it results in elections having a clear winner who can then (mostly) implement what they said they would implement. In PR countries end up being ruled by what are effectively new political parties which didn't actually exist when voters went to the ballot boxes, may have policies that were never discussed during the election and which may still exclude the preferences of large chunks of the voters, including even the largest chunk.
You don't want them to track you but are happy with them reading emails?

Anyways, I guess the login cookie and/or session storage is being cleared. Then they obviously can't keep you logged in.
Used, yes, butbnot implemented. std::collections::LinkedList is a doubly-linked list suitable for games. It's basically just the no-std crowd that might need to implement their own.
When would you have a keylogger and not a screen logger?
22/02/2020 Update: - I have fixed some typos. - I have fixed some compatibility issues in RHEL distributions using SELinux. - Improved the exclusion of addresses that should not be routed via TOR. - DNS port 53 to 5353 - Started a parallel project to support other Unix like distributions like BSD.
Excerpt:

"While this computerized future, often called the Internet of Things, carries enormous potential, best-selling author Bruce Schneier argues that catastrophe awaits in its new vulnerabilities and dangers. Forget data theft: cutting-edge digital attackers can now literally crash your car, pacemaker, and home security system, as well as everyone else's. In Click Here to Kill Everybody, Schneier explores the risks and security implications of our new, hyper-connected era, and lays out common-sense policies that will allow us to enjoy the benefits of this omnipotent age without falling prey to the consequences of its insecurity."
Rust has a concept of ownership and borrowing. (I think) everything is fine when you just have immutable references everywhere. But as soon as you start taking mutable references (of which only one can exist at a time) or ownership (stronger than mutable references), then cycles break things.

You can get around it with Interior Mutability, it's just slightly more verbose.

Also, it isn't really that they made an easy thing hard. Properly maintaining the invariants with cyclical references is hard and unsafe. Rust exposes that difficulty in a very literal way
I'm reading The Silmarillion now (coincidentally, just yesterday finished Beren and Lúthien, indeed moving) but found Starmaker much more "fun" than The S, at least so far.
Yes.

Did you mean to say “can it be over-appreciated”?

It can be that, too. It ain’t slavery.
My partner used to watch Grey's Anatomy and this procedure was the main plot in one chapter. I could not believe this could be real so I googled it and confirmed to my surprise it was a real thing.

Recently I watched a local show about a bank robbery. The secure chamber was constructed beneath a river. If alarms triggered the chamber would flood. Again, I could not believe somebody could engineer that. I was wrong.

This pattern repeats. Certainly fiction is bounded by reality.
Dude stop lying. Also, other UX students with similar shitty experiences as that cohort have been trying to get their ISAs cancelled, and are getting the runaround. Come on.

Did you not read the scathing letter? If you want to address these issues - why don't you publicly post the letter and address every single damning issue highlighted if you are so confident? There were things outlined outside of just "bad instruction" and "misaligned expectations". Do better.
Thanks, if that's what was referenced above, it certainly isn't a study to see if women were underpaid - but to see if anyone was underpaid.

And reading the brief content:

> There are a couple of reasons that the pay equity analysis required more adjustments in 2018, compared to 2017. First, the 2018 analysis flagged one particularly large job code (Level 4 Software Engineer) for adjustments. Within this job code, men were flagged for adjustments because they received less discretionary funds than women. Secondly, this year we undertook a new hire analysis to look for any discrepancies in offers to new employees—this accounted for 49 percent of the total dollars spent on adjustments.

I suppose a natural question would be if an overpaid se4 is an underpromoted se5, or if an underpaid se4 is an overpromoted sr3.

I understand the try to correct for "similar roles" - but that doesn't mean the promtion/roles are accurate.

Either way; interesting link.
It could be like this:

https://en.wikipedia.org/wiki/Bar_examination

https://en.wikipedia.org/wiki/Architect_Registration_Examina...

https://en.wikipedia.org/wiki/Principles_and_Practice_of_Eng...

We do interviews in this field like casting calls. Come on over and audition for this role. So basically we're saying 'software engineering' is a talent and not a skill.
I have learned from an Amazon recruiter that it was a data-driven decision to focus on algorithms during interviews. Apparently, on average, it has worked the best for them than other ways of interviewing.

I think the state of despair is caused by companies copying practices from FAANGs without understanding the intricacies of why those practices are in place. To the point of asking a UX/UI dev to solve a DP problem.
That would be a step forward. But a government-backed ISA is very much like a special-purpose income tax. If we're going to that, I say we just go all the way.

I think of education as like roads, policing, and courts. It's fundamental societal infrastructure. Because the benefits are widespread and diffuse, charging directly for it is difficult. As with primary and secondary education, I think it's ultimately easier to just pay for it as a society and get it back in taxes later.
We would have always seniors who are there already for some time to refactor the code. No reason to have it refactored by someone who does not know how to properly code yet and does not know what problems existing structures have or solve. Otherwise you are just switching one mess to another mess.

We had juniors for easy new features, tests, anything that is small and isolated.
Docker-Sync
> This whole 'whiteboarding' thing has degenerated into 100% pointless trivia, with many elements of a popularity contest - I just don't see any reason why we should trust this to yield 'safe' candidates.

People blindly and dumbly implementing any practice is going to yield bad results. I've interviewed for Google, for a small company with a crappy pipeline and a low need for talent, and for my current job, which needs Google-level talent across multiple specialties[1]. Whiteboarding has played a critical role in all of these. The goal isn't to have them answer trivia questions in marker, it's a basic test of their ability to think critically and program. Naturally, the exact questions differ based on the role: for the second job, it was basic processing of data structures, while for the third, I got a question that involves some degree of spatial reasoning. But in general, this is a pretty fundamental way to test a pretty fundamental set of skills.

I even was lucky enough to get a negative example: I ran the tech org for the second company, which had two non-technical founders. We hired a candidate with no engineering experience on my recommendation because he did very well in his coding interview: this guy ended up being the most reliable, clutch engineer in the company. I also rejected a candidate on the basis of failing the simple whiteboard problems, and the founders decided to hire him anyway based on his years of experience. The founder ended up having to bounce him around from task to task, leaving a trail of destruction wherever he went. His code would bring production down, he'd create weeks of work for others in a couple of days, he utterly destroyed devops during his brief tenure there, etc. He was very sweet, hardworking, had a great temperament... But the inescapable fact was that he was just kinda dumb. The whiteboard interview handily caught this, _which is what it's supposed to do_, and all the HN sniveling about whiteboard interviews only being useless trivia contests doesn't erase that fact.

[1] You can imagine how hard hiring is for us right now...
And rusts default hashing implementation is hardened against these attacks
How is hundreds of political campaign volunteers considered far-reaching? Surely it's less than the number of normal non-shill people involved in the campaign legitimately. I feel like the scale of these numbers is off in a way that suggests the campaign messed up in more than one way.
Maybe you need to completely reevaluate what you think a paradigm shift really is? Could be you've been thinking about it wrong the whole time.
This isn't a linked list issue at all, but a problem with constructing the nodes. If you construct list nodes in a contiguous location cache misses are a non issue.
We evaluated the use of Mercury before settling on prolog for terminusDB. Mercury is a great language, but the community and library support is just a bit too small.
I don't have any connection to either side, but I have to say that it seems reasonably fair to me to tie the release of the ISA to a covenant not to sue. (It's like if a car maker buys back my lemon car, I don't expect that I also get to sue them because my car was a lemon.)
> It seems implausible. It's counter-intuitive. But the idea seems pretty persistent.

Some of us have direct experience with exactly this situation (see my previous comment). Hell, Jeff Atwood wrote a whole piece on it a long time ago.
You can't make anything near the precision tolerance of a LEGO brick with a 3D printer.
Unicode support of Raku is grapheme based (NFG or Normalization Form Grapheme). The unicode theory: https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundarie... , about the implementation: https://6guts.wordpress.com/2015/04/12/this-week-unicode-nor...
The quality (tolerance / fit) decreases very quickly with price.
Sorry, this won't work.
1. Too arduous for the FAANG company
2. If the end result is $250k/year salary, then absolutely insane amount of people will stick it until the end. I know I do. Heck, I will live at FAANG office 24/7/365 if I need to, and I know a lot of people will do it. See the current state of Leetcode forum and reddit CS career questions to get the feel of the type A people who flock there. It is go big or go home. Bleed and get up again.

Hypothetical scenario, tell the startups/VCs to pay more for software engineers, just a little bit lower than FAANG, then two things will happen:
1. Either FAANG will even increase their salary even more to attract type A types
2. A huge number of applicants of varying quality will flock to CS as an industry lowering the overall quality, forcing companies to do hard DS&A questions to filter applicants.
If you want a "toy" example of this type of code, look at flight control software for drones such as Betaflight. You can modify this code and test it in real life. I did this, as I contributed the GPS Rescue feature. I have a blooper reel of failures during testing.

https://github.com/betaflight/betaflight/
Find your way making hundreds of thousands of dollar online in a year
I think you missed the entire point of these articles. The algorithms you're forced to memorize are, 99% of the time, useless. Instead of hiring someone by their track record, managers are choosing to hire those capable of memorizing trivia.

Part 2, paying someone on trivia instead of capabilities is not sustainable. The company ends up suffering in the long term. Other engineers that are actually capable have to pick up the slack. Longer hours, less family time, higher burn out risk. Then comes the firing period because the company is losing revenue due to rampant incompetence. Putting even more pressure on the capable engineers. There's plenty of articles where trendy startups have some brutal layoffs, even though 12-18 months earlier had massive funding rounds and went into "extreme" hiring phases. The chickens come home to roost, no matter the sparkling bling of big paychecks.
Yes I've seen that also work, it's a lot of stitching together things yourself and we had to put a lot of caching in front of the inverted index we were using, however definitely plausible. ClickHouse doesn't do any streaming of data between nodes as you scale up and down which was a big thing for us since we had large datasets and needed to rebalance when cluster expanded/shrunk.

With regards to trie vs inverted index for Graphite data, I'd actually still be inclined to say inverted index is better based on the amount of queries I saw at Uber with Graphite where people did `servers.*.disk.bytes-used` type queries which is way faster to do using an inverted index since you have a postings list for each part of the dot-separated metric name, rather than traversing a trie with thousands to tens of thousands of entries in index 1 host part of the Graphite name. This is what M3DB does[0].

[0]: https://github.com/m3db/m3/blob/b2f5b55e8313eb48f023e08f6d53...
I witnessed "cyber bullying" on BBS forums already in the mid-to-late 1980s. It's both understandable and curious that very few contemporary journalists have any idea at all about that pre-Internet multiverse.
Not every business needs to be aiming for hyper-growth. Perhaps some tech startups can take a breather and reconsider whether they need to be engaged in the same zero-sum game as everyone else. Because grow at all costs doesn’t just harm untrained juniors- it also leads to corner cutting and short-term thinking that could bite the business in the back later on.
It’s a tough world where “ear rape” strictly falls into the “being an asshole” category.
> Ask Me Anything :)

Appreciate it. For some background it would be nice if you clarify the perspective of your role as one of HR/coordination or a more technical view on participants of these interviews.

Do you feel like current FAANG hiring practices for lower level roles incubate a generation of programmers that trains specifically for the interview process moreso than they do for the actual role you want to fill (and if so, do you feel like that is benefitial to your employer / simply a necessity at their scale / worth changing)?

edit: That makes sense, thanks!
I think it's a compelling and feasible solution to the news site monetization problem. It just seems difficult to imagine users flocking to something like this away from ad blockers—which improve daily (and are mostly free).
So this is like Spotify for websites?
I'm a student - "reviews are fine" because students are also scared of being truthful to staff. The staff do not have a good history of listening to negative feedback and criticism. They are either ignorant or delusional.

Look at Dustin Myers and how he responds to criticism: https://twitter.com/dustint314/status/1156423191645917184

Look at Trevor McKendrick (Chief of Staff) and how he responds to criticism: https://twitter.com/TrevMcKendrick/status/108285421890879488...

Look at all of Austen's interactions on Twitter to students and how he gaslights them: https://twitter.com/Austen/status/1213711252175740928

Look at Ben Nelson (cofounder) and see how he only interacts with positive testimonials and discount negative ones: https://twitter.com/sunjieming/likes

Look at Ryan Holdaway and see how he only interacts with positive testimonials and discounts negative ones: https://twitter.com/Ryan_Holdaway/likes

Look at Ryan Hamblin - same thing: https://twitter.com/RyanleeHamblin/likes

There's a clear pattern here. These are key people in staff who should be listening and responding with empathy to the horrifying student stories throughout Lambda. All negative dissent is squashed by dividing and siloing students. They are made to think their issues with the "school" are due to some personal deficiency.

It is no wonder that negative student accounts rarely get amplified or even created. I was personally scared to write negative reviews for fear of being admonished by their "Student Success" team. There's been rumors circling of students removed from Slack after they complained about the quality of education. Leadership and key members of staff are all complicit.
Every time people say that if they had how to pay for the site they would use it. Now is the time to show the truth
That's not the intended goal...

...The intended goal is to figure out who is intrinsically motivated (i.e., curiousity, innate interest, desire to learn, etc.), from those that are extrinsically motivated (i.e., salary, money, title, career, corporate position, etc.)
I don't know much about Rust (and nearly nothing about Pin) but if this was true, don't you think someone would already have written a library providing doubly linked list without using unsafe?
Google made logic riddles disallowed on interviews by over a decade ago (I think 2005? plus-minus few years), yet they are still thought to ask them.

Despite it being a turn of the decade 1980/1990 Microsoft thing.
Fred is talking about adding folk to a late project
No, wouldn't use it, sounds at least 10x slower than typing.
Attributing the perceived lacking performance of people to having kids is just another way for ageism.

> I've had to teach senior architects not to send private ssh keys to each other and instead use public keys.

This has nothing to do with seniority, just ignorance. And ignorance knows no age.

> How to do basic naming schemes for servers.

Now this is something that I would understand why someone older would not care. You know why? Because these things are just fashions. You think they are stagnating? Truth is, they are probably just waiting until next week when some bright up-and-coming 30-something will show then another article they found online and will try to change ever-so-slightly something just so that they can feel they are making a difference. "Naming schemes for servers, really?"
It's also a hell of annoying. Since in 99% of the cases noone is looking over your shoulder it's OK to not give me a puzzle every time.

Also, with consistent numpad I'm able to enter all digits super-quick which is very hard to track. While with randomized numpad I need 5 seconds to find my numbers.
Not an astrophysicist so it might be a stupid question. If the combined mass of the pair is calculated to be well outside the range of what we find in our galaxy, could it be that it is not the mass but some other inputs to the calculation? From what I understand there is still a challenge to determine distances to the very far objects (that is one of the reasons for recent news about “Hubble not so constant”)