skysight-inc/HackerNews huggingface dataset:
It is not only about people who try to get lucky for junior positions. I have seen people who think of themselves as "super senior developers" who were more "business bullshit specialists" who knew names of things but when faced with technical challenges were lost right away. Those people could maybe configure WiFi router with web interface but if you get them to work on industrial grade router with stripped down Linux it is not something they can jump over.
you have an aptitude for a CTO position, but T does not stand for `tech`
Why I loved reading the io_uring paper
It should be just the opposite. Now that I have more responsibility, I care more about staying marketable. I never want to be in the position where my livelihood is based on a job instead of having marketable skills and a strong network that will allow me to get a job quickly if I want/need to.
If the plan was to launch a research-centric UX course and to have them collaborate with the web cohort at the end, who was going to be responsible for actually implementing the research that the UX students undertook once they began collaborating?

Anyone who has worked in the industry knows that most software projects fail for human reasons, not technical ones.

Like, who was going to be opening up Photoshop or In Design or Figma or whatever? Who was going to be slicing designs into HTML/CSS? Who was going to be implementing interactive prototypes and putting them in front of users? Who was responsible for ensuring that communication between the UX side and the technical side was happening effectively?

Who were the product and project managers (in title or de facto) and were they clear that this was their job?

In your interview with Vincent Woo, you said that "reviews were fine" for the UX cohort and then they suddenly fell off the cliff once labs began. This story more or less explains why: the students were strung along (intentionally or not) with the promise that it was labs that matters.

Once in labs, they find out: https://twitter.com/watsonwaswrite/status/123090468067232154...

If that was the promise, why wouldn't LS move heaven and Earth to make sure that labs was a home run? Why wouldn't LS ensure every student in the group project was crystal clear on expectations? Why wouldn't LS do a dry run version of the capstone project across cohorts to control for unanticipated group dynamics? Ensure that everyone in the web and UX cohorts has worked with at least 5-10 different people cross-functionally before capstone time?

And fine, maybe you "call an audible" — lord knows we had to do that at DBC. But why then wouldn't you then bring in 5-10 experienced project managers to facilitate things, communicate everything to everyone, and explain that this is what needs to happen to make the capstone a success for everyone?

Shouldn't asking and answering these questions before admitting a single student be table stakes?

The whole project seems half-baked from start to finish and this outcome 100% predictable.
An array (an ADT) can be arbitrary dimensional, with one-dimensional case often called vector (and two-dimensional called matrix). An array can also be adjustable, both in one and multi-dimension variants.

So a vector can be both adjustable and non adjustable, and some language do have both versions. Some language have adjustable one-dimensional array/vector as the only dynamic aggregate/ordered datatype.

And to answer the post I replied to originally, a vector in rust is a one-dimensional adjustable array. To answer your question above, no that's not what I meant, sorry for not being clear enough from the beginning.
Is it really that rare that companies have legitimate hiring processes and realistic interviews?

Take this with a grain of salt, because my experience may differ from many here (never worked at FAANG, I spent a lot of time at smaller startups in Boulder and am currently in Miami) but I have only been put in front of a whiteboard one time during many dozens of interviews and it was a generic logic puzzle to see how I performed under pressure.

Having been on both sides of the hiring table now many times, there is only one approach that makes sense to me:

1. Speak to them over the phone to make sure they are decent human being, verify again in person.

2. Be upfront with general compensation ability and expectations so that neither of you waste the others time.

3. Do a pair-programming exercise where they build a small piece of software that mirrors something that would be working on as a day-to-day there. Make it clear that finishing is not important, you just want to see their thought process and how they communicate. Ask them to refactor parts of it at some point to see how coach-able they are and how they respond to criticism.

This strategy has worked exceedingly well for me, and when I was on the other end of the hiring table the companies whose process generally looked like this were great places to work with good people.

Algorithm questions are a hazing ritual, and so many junior devs get sucked into wasting hundreds of hours practicing them when they could be building real-world skills. This practice has got to stop, IMO.

https://github.com/poteto/hiring-without-whiteboards
They obviously don’t mind the thousands of pro-trump shills, either
A hash table is vulnerable to collision attacks, if keys are derived from any kind of untrusted external input. Trees might be slow, but they're consistently slow.
Derivative of Inverse Function Animated
Even the Silmarillion appeals to readers’ emotions in conventional ways with e.g. the love story of Beren and Lúthien. Not quite as dry as Stapledon.
> They bothered to ask me how I'd deal with diversity issues if I was in HR, though. I probably didn't get the job because of my answers there...

Strange postscript that suggests you hold some problematic opinions that indicate you can't play nicely with others?

Did you fail to get the job because you didn't have the tech chops or is it because you said something wildly inappropriate on the behavioural questions?

What did you say?
Props to Apple for releasing this. The way Spotify has handled the deprecation of libspotify without a proper replacement and removing streaming/playback from their other SDKs has been extremely disappointing.
Well, I can say from personal experience that there are interviews when I've aced the algorithm question(s), and other interviews when I haven't. Not hugely different in time interviews, either. So I can say from personal experience that it doesn't correlate all that well with my own performance, or it would be constant.

I expect, though, that the issue is that the degree of correlation measured will depend on the population you're screening with it. If you are wanting to screen out fraudulent or otherwise utterly non-programmer persons, it will show a good correlation. However, among those who are actually programmers, it will show much less correlation, and if you're in a condition of developer scarcity, the false negatives could be more costly than the false positives.
I think that would be really cool, and a good discussion piece.
Related from 2016: https://news.ycombinator.com/item?id=11093781
Next Courses in Madrid
These are the official courses of the owners of the registered trademark Anatheóresis, which will be taught by its Director and Academic of Health and Sciences Ramón y Cajal Fernando Martínez Amaya:

Child Therapy Course, will take place on June 12, 13 and 14, 2020.
Basic Training Course for Anatheresis Therapists, will take place on February 15 and 16, 2020 (1st weekend) and February 22 and 23, 2020 (2nd weekend).
2nd Level Course for Anatheresis Therapists, will take place on November 14 and 15, 2020 (1st weekend), January 16 and 17, 2021 (2nd weekend), March 6 and 7, 2021 (3rd weekend of week).
Advanced Emdr Prenatal Course, will take place on March 14 and 15, 2020 (1st weekend), March 21 and 22, 2020 (2nd weekend).
Prenatal Course, will take place on September 18, 19 and 20, 2020.
Symbols Workshop, will take place on June 5, 6 and 7, 2020.

Transpersonal Anatheóresis S.L., Madrid
Dirección: Calle del Poeta Joan Maragall, 58, 2 H, 28020 Madrid, España
Teléfono: +34 91 522 8909
Correos electrónicos:
contacto@anatheoresismadrid.com
terapias@anatheoresismadrid.com
Web: https://www.anatheoresismadrid.com
Ahh so parent comment wasn't sarcasm. Welp. Poe's law strikes again.
The first thing I want to know about a typesetting system is: does it do microtype? And are there any innovations at that level? I don't see any mention of this in the "SILE vs TeX" section of the manual, but to me it seems like the most important thing I'd need to know up front. After all, if I'm not going to put in the effort to make a document look really good, why bother with a typesetting system at all?

Practically speaking, I think if they wanted users to adopt this, the best thing they could do would be to write an output format for Pandoc or similar. I could try this today if such a mode were available.
While this is true, for a metrics workload it does not work great I have both seen and heard from others, mainly due to the fact it does not have an inverted index - so finding a small subset of metrics in a dataset of billions of metrics ends up taking significant time due to the scan required to find the timeseries matching the arbitrary number of dimensions specified to find the timeseries you're looking for.

If you're building it with a specific application and a concrete schema you can create which will result in fast queries and don't have requirements for arbitrary dimensions being specified for lookup, then yes it's great as a TSDB.

Prometheus, M3DB, etc all use an inverted index alongside the column store TSDB to help with metrics workloads.
Ask HN: Would you enjoy using pen/paper over laptop for development?
I am more of a pen/paper person than computer. I had 2 ideas on how to create a bridge between laptop and pen/paper :

1. A software existed that could turn a picture of code into code

2. A software that could turn a UML diag to software classes/function/variables etc. The logic can be filled in by the dev actually implementing the feature.
What's the difference between buying flour etc. to bake a cake to sell, and buying food to eat, so I can continue to function and sell my labour?
I struggled quite a bit to pick up Haskell. OCaml was comparatively a breeze to learn, and a lot of fun too.
If people are disappointed that they can't actually buy your product, it's only because they want it and can't readily get it by any other means (otherwise they never would have bothered with you in the first place). By validating your idea, you move one step closer to satisfying their wants and needs. If you don't validate your idea, or validate by a slower or less effective method, you are delaying, possibly indefinitely, their ability to purchase what they desire. While some people may react negatively to being "misled" like this, that doesn't change the fact it is objectively in their best interest. Your desire to avoid misrepresentation does no good beyond making you feel better about yourself for having followed an arbitrary moral rule without regard for circumstance. Any ethics system that says go against everyone's best interests to make yourself feel good is dumb.
Doesn’t society put its own value on your work by sustaining the mechanism which keeps paying you? If anything, most likely than not you are paid too little as people rarely maximize their negotiating leverage.
Related from 2014: https://news.ycombinator.com/item?id=8392653

A bit from 2016: https://news.ycombinator.com/item?id=12411446
Setting it up was expensive, so there's a good chance it involved initializing libraries, launching threads, or otherwise creating state that isn't handled correctly by fork.
It is definitely not the case for C++. It has a decent standard library - when it comes to collections, richer than many other languages, in fact - and then there's Boost for more exotic needs.
Pycel: Compiling Excel spreadsheets to Python and making pretty pictures (2011)
One reason to complain is that these interview-questions usually bare so little relevance to the actual job.
What is microtype?
Have you seen the variety of bread available, and the price range thereof? If all of it is purchased on rational valuation grounds, I think we must end up with a fairly loose definition of "value"
GitHub Releases ML Based Good First Issues Recommendations
You see, I've had the opposite experience whenever I've been looking for my next challenge.

I've had recruiters talk to me at length about each of the people I'd be meeting in the on-site, their backgrounds, what they'd be covering. I've had ones give me broad strokes about why previous candidates were passed on. At the end of the day, it's not in their interest to bring too many people to an on-site who will fail spectacularly, because that means they're not doing their job properly.

I may just be lucky.
neck...?

scnr
Money Report – Feb 22'nd
> Of course, we cancelled their ISAs; we lost a ton of money training these students and they don’t owe us anything, but that’s the right thing to do.

This was not a magnanimous gesture. You fought with the students for months, when it was clear things weren't working. It wasn't until the story blew up in the media that you agreed to cancel the ISAs.

And then to be released from their ISAs, you demanded students sign a contract agreeing not to sue Lambda School.

https://twitter.com/tylernishida/status/1230969940733095937
I was forever saving for that 8880 super car. It had a real gearbox...

But it was just like saving for a Ferrari or something. A nice dream that was never to be for a 12 year old...
I'd say Lego is the best deal on market for fun/price ratio.
Just try go to any toy-shop and notice how bad everything else is.

Even if you going to buy RC car for kid - better buy Lego, it will be slightly more expensive but much better in quality.

Like programming - buy Lego Boost. 120$ for programming robot. Seems cheap for me.

Maybe for girls it's different, but my son do not want any other toys expect Lego.
Remote work ftw.
> Well, I can say from personal experience that there are interviews when I've aced the algorithm question(s), and other interviews when I haven't. Not hugely different in time interviews, either. So I can say from personal experience that it doesn't correlate all that well with my own performance, or it would be constant.

Do you even understand what correlation means? There is a significant random element to it, yes, but that doesn't mean that there is no correlation, and the random parts from the same individual can be mitigated by doing many interviews after which you have reasonable correlation. Most interview styles has close to zero correlation, so even if we don't reach anything remotely close to 1 it is still pretty good.

Edit: About the points that it is enough to weed out people using simple problems, that isn't true either. There was significant correlation between job performance and interview performance even among those who did well. The statistics showed no signs of it capping out either, so for all we know we could make them even harder, just that there wouldn't be that many left that could pass them then.
Ironic, because I work at Google and just found a bug caused by using percent-based border-radius CSS rules on a non-square element - something anyone with even intermediate CSS experience wouldn't write.
In my sibling comment you'll see that I used Firefox's reader view, which didn't include that text.

I don't believe that caption text correctly reflect Twitter's quoted response, which I quoted, and which I believe clarifies your question.
Again, we agree. But it's that word should that is the delta between how we would like it to work and how it currently actually works.
Okay, let's start with the obvious one-- why do you believe focusing on excruciatingly difficult algorithmic problems totally unrelated to the work you do is a good way of finding people?
You missed a big one - giving them an idea of how you approach a problem and work through it. That's the biggest take away.

If someone just spits out an optimal solution straight away that's not actually a great sign. It doesn't matter if you struggle a little, or need a few hints, but showing you know how to break a problem down into smaller sub-problems and work your way up is an invaluable signal.
> That is all true but you’ll get one thing working at a startup that you don’t get at a big company. A sense of legitimate urgency. I’ve worked at both and at a big company things are glacially slow and engineers love to build big “enterprise” solutions to tiny problems that don’t need it.

The "sense of legitimate urgency" is a bunch of bullshit. It's just as made up as it is at any other company. I've worked at startups from seed stage to unicorn and a lot of the real urgent things aren't things that engineering needs to do - it's other shit and usually has to do with partnering with someone. And that usually isn't an engineering problem. Engineering is rarely the blocker for things being rolled out. It's usually that product can't determine what the right product is - business can't get the partners they need - etc.

At a small company - your overengineered crap becomes the institutional bullshit that holds the rest of engineering back for years because no one can replace it because there's no time for refactoring. At least at a big company you can throw away those solutions that don't work for people. At a small company - it becomes the shit that holds you back from doing things efficiently for years.
But there is a way to filter the amount of FAANG applicants!

It is as follows:

Offer ridiculously low pay, such that only basic expenses could be paid for, like basic housing...

Then, see who shows up.

Whoever shows up... really wants a job.

You don't hire them yet.

You implement your own corporate bootcamp, where you give then coding assignments. These start easy, but progress, over a number of weeks, to those that are similar in form and difficulty to the type of work that the corporation does...

A supervisor or group of supervisors reviews their work after every week.

People who do not meet expectations are let go.

What you're left with after that process is your new hires.

That's how you cut down on frivolous resumes.

That's how you weed out the casual job seekers from the purists.

The purists don't care about money as much as working with the right people.

It's not for everybody.

People who need salaries obviously, beyond the most basic of living expenses, would be unable to apply...
Can you describe what some of your hurdles have been? Pipewire is probably not going to solve your issues as it's not a complete replacement for JACK [0] and uses the same API anyway. Realistically, if you're writing a new DAW, you're still going to want to use the JACK API. If your problems are driver-related, that definitely won't be solved by switching to a different audio daemon.

And for the record, the open source audio community is not dead. There is activity, but you have to know where to look.

[0]: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ...
Baby Boomer Employment Across Time
Not OP, but it's often not about seeing you get a perfect solution straight away, they're judging your problem solving skills - how do you approach something you've probably never seen before. Do you choke? Do you break the problem up into smaller sub-problems?
I'm not trying to start a fight on HN. I just said that you should hire the best people you can. I screwed up a sorting impl. that I never bothered to practice.
No, you get promoted to level of competence, then fired after several years instead of becoming incompetent.
Show HN: GitSpo – Monitoring and Analytics for Open-Source Projects
I wonder if "inexplicable Republican best friends"* like Rayiner, who try to tell Democrats who their candidate should be, know that they are actually showing their hand and telling the rest of us who they're most afraid of.

* https://medium.com/@CitationsPodcst/episode-69-the-rise-of-t...
Clickhouse has a table engine for graphite. We've used it for a couple years now after out scaling InfluxDB and working around it several times. Clickhouse works _extremely_ well for graphite data, it can handle several orders of magnitude more load than Influx in my experience.
> Also, think about when flight software started being written. Was Rust an option?

It wasn't, but Ada probably was (some flight software may have been written before 1980?), and would likely also be a much better choice.
I thought it was the other way around: games using arrays, non arbitrarily growable vectors to precisely be able to iterate over everything quickly in a deterministic fashion. Specially because a lot of what games have to deal with is "visit every node".
Non-mathematicians build mathematics buildings, harvest and press chalk into sticks, grow the food and coffee we process into theorems (mathematicians are significantly more likely to od on amphetamines, btw), attend the calculus courses we desperately need for funding, clean our chalkboards and empty our wastebins... the list goes on and on.

And yes there are mathematicians who vote for Trump. All you've proven with that tirade is a bound on the radius of your own filter bubble.
I believe it's referring to small intercharacter typesetting details like tracking and kerning.

From the microtype package for latex:

"The microtype package provides a LaTeX interface to the
micro-typographic extensions ... : most prominently, character protrusion and font expansion, furthermore the adjustment of interword spacing and additional kerning, as well as hyphenatable letterspacing (tracking) and the possibility to disable all or selected ligatures."
Actually problematic or just problematic to someone at Google?
Sometimes I wonder when you have such a long interview process what the point is of those super long probation periods.
I have published it on ProductHunt this morning where I shared more background about the project:

This is my favourite side project. I have built it so that I would know when people are talking about my projects and in what contexts my projects are being mentioned. The goal is to measure what impact social mentions have to product adoption and to create opportunities for developers to engage their communities outside of GitHub.

Currently GitSpo aggregates data from 10 different websites, including dev.to, GitHub, Gitter, Hacker News, Hashnode, Medium, Reddit, Stack Exchange, Stack Overflow and Twitter. In total I caught 800k+ project mentions. This excludes bot activity (I detect and filter our CI and similar bots) and repeat/ near duplicate mentions.

I am yet to figure out how to monetize GitSpo. In theory, the underlying tech would allow a pivot to a Medium.com-like company. I thought of creating a tool for recruiters to identify the rising talent. Maybe even automatically suggesting improvements to developer LinkedIn profiles based on their activity. Perhaps generating impact reports for companies that invest into Open-Source. With a bit of luck and time a problem worth solving will come to me. :-)

Viewing my own project mentions is great. Though my favourite feature has become the trending project list, https://gitspo.com/trending. I have stumbled upon some very cool tech this way in the past couple of months, and seeing the comments on social media about those projects allowed me to form an informed opinion about the potential use cases.

https://www.producthunt.com/posts/gitspo-3#comment-976111
What happens when the competing providers are killed out?
HoTT so hot right now...
Also, I'd suggest required phone/email as the end user seems to be a risk. For example my Twitter account is locked because I never gave a phone. Then a year later it comes out attackers can figure out your number. Not worth it to me.

Also, I can get an SMS over VIOP for cheap for a limited number of days. If I were an attacker the email/phone verification does nothing to stop me.