skysight-inc/HackerNews huggingface dataset:
That doesn't end up being the case for a number of reasons. Firstly, no one is actually able to account of all of these known issues a priori. I don't like calling things impossible, but writing safe C that avoids any compiler bugs is probably best labeled as that.

Secondly, vendors make modifications during their release process, which introduces new (and fun!) bugs. You're not really avoiding hidden wasps, just labeling some of them. If you simply moved to a newer compiler, you wouldn't have to avoid them, they'd mostly be gone (or at worst, labeled).
I think the argument is that if the nodes are fixed size then you can preallocate a big block of them slab-style, and for the pointers you just use indexes into that array rather than "real" pointers.

Potentially there's a small memory savings as well if you can use 2 or 4 bytes for the index instead of a full 8 byte pointer. But you're taking on a lot of complexity and tuning by going this route so you'd really have to test and make sure the gains were worth it.
Lots of good open source projects fail. But not every company is willing to open source code like this, though, and I'm very happy that Uber did so in this case.

I get your frustration, but everyone should remember there are never any promises of support with open source software, regardless of how well supported it is at a particular time.
I've always wondered why Netflix and all don't have clip widgets that you can link/embed on other sites. It is essentially free mass embedded paywalls.
I think some part of this is that technical debt is invisible to the people that don't directly deal with it, so it's easy to underestimate how much of it there is.

We, collectively, need to get better at communicating the cost of the technical debt we face in each project. I stress that this is a two-part conversation: the engineers need to get better at explaining the amount of it in terms that matter to the end user, and management needs to learn to understand what the engineers are trying to say.

Let's also not forget that the engineers are the ones who produced the technical debt in the first place. The earlier it can be identified and weighed against other business desires, the better. Speak up about it not only once it sucks but also when it is created in little pieces.
Can you explain more? How did you find a trading company that hires non formally trained devs? They seem to be the type to only look at Harvard grads etc.
Because we want to find the best people at solving difficult problems with limited time, and maximum ambiguity.

At a high level that reflects the work that we do. The project scale may be 20 weeks instead of 20 minutes, but the level of complexity is scaled accordingly.

Of course, we miss out on some candidates that could be great at executing on a large timeline but can't demonstrate it in a short in person interview.

But, (see my edit), this is all we can do to scale our interview process, and we don't want to take risks.
iPhone settings that could save your life
Ah thanks, that's a rough blow for this idea.

I worry that this idea won't work until

- Someone can prove that the increase in number of paid subscribers will offset the decrease in $/sub, and...

- The subscription company is effectively owned by the big news orgs, so that they feel comfortable effectively handing over control of their subscriber base. Similar to how Hulu was started as a partnership between a few big media companies.
Jerry (YC S17) Is Hiring Product Managers (Toronto, SF, Remote)
Google Plots Course to Overtake Cloud Rivals
I rarely find a developer website without RSS. Most blogging platforms provide RSS either natively or via plugin. If a website does not offer an RSS feed and I _really_ want to follow it, I will ask the author.

Shameless plug: I've created a Tip of the Day platform [1] specifically with RSS in mind.

[1] https://tips.darekkay.com
I sincerely hope the codebase of your employers is littered with 30-minute solutions to puzzles such as the one you describe.
The test example looks alright: https://github.com/sile-typesetter/sile/blob/master/examples...

The kerning doesn't look great, but that's the fonts (DejaVu Sans + Libertine AFAICT).
And I can criticise it. :-)
>The only reason business people love patents is that in a world where patents exist, you have an incentive to collect them. But I think the second order negative effects of this dramatically slow innovation and harm society economically. If Prusa can exist without patents in a market where competitors still use them, we can obviously make functional an entire economy with less intellectual property restrictions.

You make some interesting points, however generalizing one example from 3d printers and concluding "patents are clearly bad" is really oversimplifying the issue by a lot.

There are plenty of examples of patents stifling innovation (oftentimes purposefully, where a company buys a patent just so nobody else can use it). There are much more complicated examples though, such as the pharmaceutical industry. At least in the US, which funds most of the world's drug research, the entire business incentive for developing new drugs would evaporate without patents. Now there are lots of problems with the pharmaceutical industry, however developing new innovative drugs (with the intent of profiting from them, often viciously) is not one of them.

Everybody agrees the patent system is broken. The problem is nobody can propose a better alternative.
You might like "The Wandering Earth" by Cixin Liu. Very little "story", but a fast paced, coherent sci-fi trip!
Maynard Smith has said "A man called Olaf Stapledon was a marvellous predictor who wrote science fiction books that I read when I was 16 and that completely blew my mind; and Arthur C. Clarke put his finger on quite a number of bright thoughts. He and I have something in common: we both took out of the public library the same science fiction book when we were boys of about 15 or 16, which was Stapledon's Last and First Men. We took it out of the same country library in Porlock in Somerset. Whoever put that book on the shelves had a lot to answer for!"

Libraries have their uses.
> Is it really that rare that companies have legitimate hiring processes and realistic interviews?

In my experience, the gap between the HN comments section and the real world is massive when it comes to hiring practices.

In the world of HN comments, most people tend to identify with the candidate rather the interviewers. The interview candidate is the hero, the underdog, and the person we're supposed to root for. The interviewers are bumbling fools, drunk on power and dead set on abusing their power to find flimsy excuses to reject candidates.

In the real world, most of the senior engineers I know have spent considerable time on both sides of the interviewing table. At different points in their career, they've been the ones asking questions as well as the ones being interviewed. This leads to a lot of cross-pollination of interview techniques as well as different perspectives on what works vs. what doesn't.

We can all agree that interviewing and hiring practices aren't perfect, but it's much harder to suggest better alternatives. At one point, I tried directly asking candidates how they'd prefer to be interviewed in a way that best highlighted their talents. A surprising number of people defaulted back to standard interview practices, but I also had a number of "just trust me when I say that you should give me this job" type answers.

These online discussions inevitably skew one way, because no one wants to be the bad guy defending the current imperfect status quo. Even the author of this article artfully dodges any request to suggest alternatives, instead falling back on the safe and secure "we have a lot of work to do" response.
Both my comment and the website linked literally say “most people can eat peanut oil”. That’s hardly dangerous misinformation.

I’m willing to bet the restaurant had peanut cross contamination in the kitchen.
If you consider a larger pool of available competent developers to hire as beneficial for companies (thus driving down wages), then it does make sense. But it requires long term planning and investment, which does not mesh with the short term profit over everything business model currently running the economy. Training is a cost that must be paid, and while both students and governments have been made to pay much of that cost for a while, that system may not function for much longer.
It's scalable all right, but the other points- especially the latter two- are being debated in this thread.
Color Quotes
If you search the article for the string "New college grads" the author indicates he received multiple emails from new grads claiming they couldn't find jobs. Personally I've seen lots of new grads with 4-5 offers and many who were unable to find jobs out of college despite tons of interviewing.
Or maybe they trust/value their peer's judgement despite the fact that they themselves don't have any strong views on the subject?
To prime the populous for when other types of media manipulation occur - folk aren't going to dig into media manipulation if it's done by someone they like and never realize the sheer mass of it. But if it's by someone they don't...

If nothing else, Bloomberg's ad budget is a solid experiment for the impact of ad budgets on elections. I don't know how much of the transparency that seems to exist around what Bloomberg is doing is normal for campaigns, but that is also a plus.
The short answer is yes, but those studies are kept internal to the companies.

The longer answer is we can only study the people that joined the company and failed to perform rather than those that COULD have been outstanding but our interview process selected them out. So there are flaws, of course.

I'm not sure how you could do the latter unless the biggest companies shared their data and compared scenarios of "Candidate X failed an Company Y interview, but then later got a job at Company Z, and thrived".

Also you'd be working against the bias of "Well, that just means that the Company Z is easier to work at".

There are just too many variables, team to team.

Part of the problem is even within these massive companies there is a huge diversity of types of jobs, and an engineer who thrives on working on Google AdWords might fail on the SpannerDB team (to pick two random examples from not my company)
While domestic CS grads can't find jobs , my current manager and other managers who are naturalized citizen want to prefer H1 candidate who are either ethnically alligned or speaking one of their languages. People make fun of having rejected non H1 candidate. Being a naturalized citizen I was hired so I will keep quite with the discrimination and sympathize with H1 as getting job else where is difficult for H1. I did finally file a EEOC case in MD (531-2019-01105) to document the discrimination done by Naturalized citizens. Hopefully when our kids go look for jobs, they don't have to be party to discrimination. If you feel this needs support call a Congress man or senator to take look.
Rust's ownership rules aren't for the purpose of making the user's life hard, they are the least restrictive system that could be devised that allow the compiler to uphold Rust's safety guarantees. It was not too long ago that it was common knowledge that a programming language either has a garbage collector or has manual memory management, or possible both. Safe Rust has neither, but not without the effect of making awkward certain kinds of programming that are fundamentally difficult to make safe.

The Rust question to ask here is: Do you really need pointers, specifically? Or would some other reference mechanism work? You could put all of your graph nodes into a linear data structure like an array, and have them point to each other by holding a list of indices instead of a list of pointers. Or you could give all of your nodes unique keys and keep them in a table, and have them hold references to each other by key. The compiler will not try to prove the correctness of your graph algorithm, and in the event of programmer error that leads to dangling references your program will have to handle the scenario of following an index or a key and not finding a value, so bugs will not introduce memory unsafety.

There's also ongoing work on memory arenas in the nightly compiler, and I believe some libraries. Putting a graph into an arena is a good way to appease the compiler, because the entire arena will be freed at the same time, ensuring that hanging pointers will never exist between graph nodes.
That’s not what you said.

Student:

“I wish there was a safe place for upset students to chat to each other outside of Lambda’s slack. A worry-free environment, unmonitored by Austen & whoever has viewing permissions on our messages. Fear and uncertainty would be eliminated, and the real issues would be uncovered”

You:

“ That would not only be unwise for everyone involved but an enormous legal liability for the school. No professional environment you’ll ever be in will encourage something like that.

There are a huge number of ways to submit feedback or complaints and we read all of them.”

Which again, discussing your workplace conditions is protected, by law, under the NLRA. Why are you telling your students that “no professional environment you’ll ever be in will encourage something like that,” counter to what’s guaranteed them by US labor law?
Wuhan woman with no symptoms infected five relatives with coronavirus: Study
How it happened?
see my edit for why it doesn't matter that these 30 minute algorithmic questions do not need to be directly applicable to day-to-day job tasks
There are thousands of questions on Leetcode.
Your own link shows that people went to Buttigieg more than 2:1 over Sanders in the second alignment.

Apart from that, the movement in vote total between the first and second rounds combines two effects, but we’re interested in just one of those. Your analysis of the second round data marks a positive count for a candidate where someone moves to that candidate in the second round from a candidate that didn’t hit the 15% threshold in the first round. (That’s the only way for someone to switch.) But it also marks a negative count where a candidate doesn’t meet the 15% threshold in a precinct and his or her supporters have to move to another candidate. We don’t really care about that second effect, because that just measures whether a candidate is able to consistently get above 15%.

What we want to predict is, as you knock out Biden, Warren, etc., where do their supporters go? You can find that out directly from the released caucus data, by looking at where supporters of those candidates go in precincts where those candidates don’t hit the 15% threshold. Most of those supporters don’t go to Bernie, which means Bernie is not their first choice or their second choice.

Polling backs that up: https://civiqs.com/documents/Civiqs_ISU_banner_book_2020_01_.... Right before the Iowa caucuses, Sanders was the first or second choice of 37% of eligible Iowa primary voters. That means for 2/3 of the party, Sanders was neither the first nor the second choice.
This is probably one of the dumbest things ive read.. thx for that
It's not remotely the same. IBR is not capped, takes 25 years for forgiveness, requires payments the entire time (regardless of whether or not you have an income), and the amount forgiven is treated as taxable income (so you get a tax bomb when you actually receive the benefit).
Another great space of exercises in this vein are in-place operations on binary trees.

Specifically, rebalancing [1] proved particularly tricky for my students. I think it's a good litmus test for whether you understand ownership, borrowing, and algebraic data types.

[1] http://cs242.stanford.edu/f19/assignments/assign6/#22-bst-in...
NFL Has a GitHub Page
How do you transpile f# to ocaml? Does this mean you can get a native self contained binary out of f# code, by first converting it to ocaml code?
In your graph, the nodes are not owning each other, are they?
Why We Chose a Marketing and Application Monorepo
”Seeing that in over 20 years and very successful track record of getting jobs quickly that I’ve never done leetCode or had an algorithm interview - how did you get that out of anything that I said?”

Well, first...you were replying directly to a post that was talking about whitebord/algorithm questions and how they’re out of control. On an article about same. So my answer is: ”because I bothered to read the post to which you were replying.”

Regardless, if you haven’t done an algorithm interview in “over 20 years”, you either haven’t changed jobs, or you’ve had a unicorn career. Either way, you’re clearly not representative of the vast majority of devs. True or exaggerated, your experience is so exceptional that it isn’t worth discussing.
You could have an open source addon or reader app which provided only that highly aggregated data.
Meanwhile in Android land, Chrome gives all websites access to sensor data without any permission prompts!
Check their profile. I'm guessing it's the same company.
Monkeys didn’t need a patent system to come out of the trees.
fixed! yes it was 1,000 even, or about 200 per year. 10,000 resumes screened.
Maybe just be more rigorous: Provide builds only for people who pay.

I've seen such an option many times in former days where you could buy a binary or build the source code your own. The advantage was then that you didn't have to invest time into building.

Your current plans are more honest, probably too honest. Remove one "free" option so there are only two options left, one free, one paid.
Right, which misses the point of having this interview style in the first place.
Psychedelic drugs may transform mental health care
> Specifically the lack of a user friendly loop/sample-based recording tool like Ableton Live is glaring.

Slowly I'm trying to get https://ossia.io there... any help appreciated :D
The last part seems like it could easily be improved by simply tying it to the portion of the curriculum covered.
It stands enough weight for above average weight of people in the 70s. It was designed with that in mind probably. Times/people changed though.
I suppose it is, in binary. Although humans generally use base 10.

I might have to start saying "a binary order of magnitude" instead of "double" when circumstances call for gobbledygook.
Totally agree. And speaking to that, what major patents are expiring in the next few years? It could be an interesting HN thread in itself.
> I've personally seen no correlation between people who can solve problems and program when watched by another person versus people who can solve problems and program when left alone with a real problem, and ample of time to noodle on and resolve it on their own.

At most of my companies, we tried moving exclusively to take-home interview problems for this reason. Short problems that could be solved in 2-4 hours of time, as benchmarked against current employees during daytime hours.

Inevitably, some candidates hated this so vocally that they'd ghost us, or some times even take to social media to lambaste us for trying to take away from their free time. Or we had people refusing to do the toy problem (not real work, same test for all candidates) unless we paid them hundreds of dollars to compensate their time.

It didn't matter how much we tried to explain that the entire purpose of the take-home problem was to grant flexibility to the candidate. A large number of candidates vocally hated any interview technique that didn't involve company employees giving 1:1 interview time to them.

We just filtered those candidates out of the pipeline, but I walked away with a clear understanding that interview practices will never make everyone happy.
I am sure they would if they could, they are Apple, after all...
Open source software depends on copyright to work.

Ignoring IP laws is a great way to catch up to stronger economies that are growing on innovation. Once you catch up, though, the only way to keep growing is to develop your own innovations... at which point you start caring more about IP laws. The U.S. went through this transition and China will too, pretty soon I think.
I think a good tell is that when I want to practice for interviews, what I do looks very little like what I do to actually get better at my job. The hands-down most effective ways to practice for it don't much resemble legitimate continuing professional education (i.e. drilling leetcode on physical whiteboards) and, if they help me get better at my job, it's only marginally so and essentially by accident.
When OS X Snow Leopard was announced, this was the intro slide: http://2ig18m1zutag3bjpoclbo8am-wpengine.netdna-ssl.com/wp-c...
Hardware-based keyloggers come to mind (especially the kind that MITMs the keyboard cord).
> Based on the recent observation, LIGO scientists estimate that these heavy pairings should be almost as common as the lighter binary star systems that astronomers have been studying for decades. Big neutron star pairs should be all over the universe, including our own Milky Way. Why, then, have they never been spotted before?

I don't understand this part. Observations: lots of light neutron star pairs, one heavy pair. This implies heavy pairs are as common as light pairs? How? I would've thought it implied heavy pairs exist but are much less common. What am I missing?
In the life sciences, I feel like bioarxiv is the most useful publication medium. The very long publication times for journals is one factor, it is just too slow to be practical. The other is that preprints paradoxically are becoming higher quality than journal articles on average, because low quality or fake content is less likely to get submitted to bioarxiv (although this is going to change as bioarxiv becomes more legitimate).
There are no sure signals on the stock market. To the extent such a signal briefly exists, it will quickly be priced into the market. You just have to look at the details on each specific offering and try to find an “unsure” signal that you have confidence in because of some special expertise you developed that not everyone in the market has.
Presumably, the astroturfers are not the only money that is making its way to regular employees.
Good point. Wherever the dart falls is not corrupted yet. A new system comes into existence, it is efficient for a while then gets corrupted again and the cycle repeats
It would affect US buyers or more concrete re-sellers of Gram tokens. Given that you normally buy this kind of tokens to either trade them or keep them as a security you sell when you need money it matters a lot.
Here is a good infographic [1] taken from DataCamp [2].

The infographic and article show what skills and tools are relevant for a job as a web developer (more specifically doing Python Web Development) and compares them with similarly important skills and tools for data science. It includes average salary expectations and links to websites where you can both learn, practice and search for a job.

[1] https://s3.amazonaws.com/assets.datacamp.com/blog_assets/Pyt...

[2] https://www.datacamp.com/community/blog/web-development-data...
Is there a bug bounty program for SILE? Does the payout double for every bona fide bug reported?

I'm sympathetic to the motivations that would lead someone to write a new typesetting engine. The problem is that in terms of essentially bug-free behavior and being completely understood and documented, TeX sets a bar that, despite its age and certain kind of clunky, is very, very high.