skysight-inc/HackerNews huggingface dataset:
I interviewed for the first time in years in 2018 and hell yes it is stressful.

I wish every hiring manager had that experience as it gave me a lot of empathy for candidates.
OwnCloud founder: Why I forked my own project and my own company
There is a nice diagram on this page:

http://www1.lsbu.ac.uk/water/water_phase_diagram.html
Knowing vi basics is useful, I agree. However, for interviews I really don't think that putting a candidate who is not familiar with it is a nice thing to do.

Any modeless editor should not cause trouble but vi (especially) is quite pernicious and the candidate would be just losing time.
> The fears are justified to an extent, but the simple truth it comes down to is... You're a manager. It is your responsibility to be responsible for those under you.

A lot of people aren't squeaky clean paragons of virtue in everything they do in combination with being secure and confident in their position in the corporate hierarchy. So your suggestion seems to be boiling down to 'figure it out'. What is your fallback if the required behaviors are complicated or hard to figure out? Men-women relationships are fundamentally asymmetrical and unbalanced, and it is the case that most people are poor communicators.

There is an underlying theme to these conversations that everyone should have a basic expectation that they can come to work and enjoy a safe, respectful work environment. That applies to managers just as much as subordinates - if companies are going to act on accusations then they need very clear policy on how much evidence is needed to put a manager's career at risk.

Unless the state of the field is very clear, it isn't reasonable to tell the managers that their role is to put themselves at risk professionally and work it out as they go. The conversation needs to be more detailed about what, exactly, the managers are expected to do outside the formal frameworks and what level of evidence is needed for them to get into trouble.
I use poetry. It has bugs (`poetry install/add/update` treats git-URL dev-dependencies as end-user dependencies). I sent a bug fix and it was not merged for months. I now use my own fork of Poetry with this fix added.
Yeap. Even the hard-core Emacs fanboys at my work know a few basic vi/vim commands. I mean, you're almost certainly going to use it at some point in your career, might as well learn "i -> type something -> :wq" at the very least.
Exactly! How is it relevant to the job if the applicant is able to adapt to a new editor and new keyboard quickly? Even with a new computer, they will set it up once and then never do it again. Let the programmer chose whatever language, whatever carefully crafted settings in IDE that make them comfortable, to solve the problem effectively, because that's what matters. Problem solving is influenced heavily by these seemingly irrelevant details. It's like inspiration, you need a clear mind for that.
Cal Newport's work is essentially a reaction to the fact that all the literature on time/task management succeeds mostly at shallow work but isn't optimal for deep work.

So if shallow work is your weak spot where you'd like some improvements, then all the classics like David Allen's Getting Things Done or perhaps Covey's 7 Habits of highly effective people would be relevant.
I wouldn't use those exact words, no :).

But hopefully you have some ideas on what you want to try (and what your experience says you shouldn't, equally important) and talking about that thought process is exactly the kind of data I would want.
It's no joke. https://federated.withgoogle.com/#learn
> spying on teens

Worth noting that "the app was targeted to users ages 13 to 35 (5 percent of whom were teenagers)." [0]

Google had a similar app. I don't think that makes Facebook's app better, but it's interesting how the media reports on the Facebook app and not the Google one.

[0] https://arstechnica.com/gadgets/2019/01/facebook-and-google-...
Fair enough. I haven't run into that, probably because I interviewed with smaller companies. I have no tips on solving that problem.
You are right thats ambgious, but in this context compression refers to the dynamic compression of the adio wave (so essentially reducing the difference in perceived loudness between the loudest and the most silent parts of a recording).

Data compression doesn’t make much sense here, because you usually use uncompressed audiofiles anywhere unless it goes to the web.
Can you actually generate lightmaps with three.js?
I did a lot with it years ago. Really nice abstraction library.
> I brought in a guy that hadn’t programmed professionally in years, in fact he didn’t even have programming on the first page of his resume. However, he had been practicing while looking for a job and he rocked my programming interview. He reasoned through the problem, wrote the code, it ran perfectly the first time. I hired him.

And yet, I have a computer science master with an 8.1 (equivalent to a 4.0 GPA) and companies like Spotify/Google won't even give me a chance to do an automated online coding test.

> One other thing: if I ask for a program sample ahead of an interview, don’t even think about sending in code that doesn’t include unit tests.

I haven't learned about testing in school or at my previous jobs or freelance gigs. Where's a good place to practice it? I mean, I know what assert does and all but I don't have a strong mentality to write a unit test, unless I'm writing code that is finicky like a Red Black tree, then I do write some tests.

I hate these snarky posts, because I don't even get to an interview. In all fairness, maybe I shouldn't apply to A-tier companies such as:

- Google

- Facebook

- Spotify

- Digital McKinsey (I did some business studies back in the day)

Shout out to Optiver and OpenAI for giving me a chance though. Optiver made me realize I needed to brush up on my algorithms in the first place. OpenAI made me realize that I need to brush up on my math.
Well, if you are a good programmer then getting a Fizz Buzz on the interview is a jackpot no? It seems weird that half of the complaints about tech interviews is that they are too easy and the other half is that they are too tedious (I know that these are not mutually exclusive). The one alternative I see is to give one, really hard problem to people, but then the complaints about difficulty would come.
> He reasoned through the problem, wrote the code, it ran perfectly the first time. I hired him.

I get the overall sentiment, but come on, "I hired him" sounds like self-absorbed anecdata - so this post is about how to quickly appeal to some manager dude on the interwebs? A more useful metric would be, did this hire survive the first two years, and what do the people around him have to say about his performance.

> It’s funny how many people can’t edit text on any machine but their own

How often does this person himself get thrown into random-ass editors and forced to quickly work through some rando algorithm while absolutely not forgetting to eloquently detail out loud their entire thought process? Self-absorbed, out of touch with how humans work.
I’m actually looking forward to the end of Moore’s Law. Instead of keeping up with a rapidly shifting landscape of new and creative ways of wasting CPU cycles, we can maybe build things that have a chance of lasting a hundred years.
The colleague who interviewed me later confided that i was the first he ever had who brought his own laptop for the interview. Apparently, it is not common!
> It's everywhere.

It almost litterally is. Even busybox contains a vi clone. While I have encountered more systems without nano nor Emacs than I can remember.
Plus, there is no excuse for learning the basic set of commands: i,ESC,x,u, and maybe navigating with the letters (which I'm not proficient at).
Honestly, the guy has valid points, but he is probably an asshole I wouldn't want to work for. I appreciate getting valuable advice, but the tone doesn't have to be like this. Maybe he is mad because of the "bad candidates", but that is his job, so he should be able to handle it.
You're trying to cure the symptom, not the disease.

The disease is people being morons. If you want people to not be affected by fake news, making platforms censor people won't have any positive effect. You have to educate people.
If you really want "small tiles to such precise specification", you can get stone cut with a waterjet...
https://www.waterjetwonders.com/

...but that doesn't seem to be required. I guess it depends on how much you hate grout lines. My square 18" (45 cm) tiles have grout lines that are about 3/8" (1 cm) thick. There is plenty of wiggle room for inaccuracy. You could cut down big tiles with a chop saw.

If you want thin grout lines, or even none at all, you can pay for that. Using a waterjet might also save on wasted stone, which could matter if you use something costly like jade or lapis lazuli.

They wouldn't need to be numbered. There are not very many distinct shapes. It looks like a dozen, judging from those images somebody posted. (last 6 at the bottom of the page) Maybe you'd need numbering if you had the supplier cut unique edge tiles, but you could just cut those when installing.
You could, but sometimes the interviewer doesn't even know exactly why they are doing it.

First, it's a natural tendency. If you want to find if somebody "knows" a particular subject, an inexperienced person would start asking for factoids and interpret every incorrect answer as the proof that they don't really know the subject.

Second, many interviewers learn from other interviewers or just by trial and error, or from some courses, many of which have very dubious origins. There are many beliefs that are simply wrong, but still get circulated among interviewers, because nobody does 30 year careers in interviewing React programmers - wonder why...
The risk is that things 'just work' for extended periods of time and the maintainers are optimised out of the system because they aren't needed in the short term.

My personal guess at why civilisations can collapse so slowly (100s of years for the Romans, for example) is that the people who maintain the political systems do too good a job, and so the safeguards are forgotten.

For example, after WWII the Europeans learned some really scary lessons about privacy. The Americans enjoyed greater peace and stability, so the people with privacy concerns are given less air time in places like Silicon Valley or Washington. The two-step process at work here is that when things are working, standards slip and the proper response to problems are forgotten. Then when things don't work, people don't know what to do and the system degrades.
Imagine a situation where an APT has been around your network for 3 years without your single, old and crusty “security guy” noticing a thing, and is only detected after they cause excessive CPU load on a database server whilst running a bad query.

Would you be keeping the appropriate logs to know for sure if they had accessed customer information? Couldn’t you say to yourselves “well we have no proof that they accessed any customer information, because we have no logs at all!” and therefore not need to contact the German authorities?

They where all over the network for years. What do you think they accessed? Just a thought.
>Shoppers need a quarter to rent a shopping cart. Plastic and paper bags are available only for a fee. And at checkout, cashiers hurry shoppers away, expecting them to bag their own groceries in a separate location away from the cash register.

This just described how I've been shopping here in Sweden since the 90s.
At the same time I don't see people having too much bad opinion about people working in defense industry. Ethics is not an issue with hiring.
I have invented the holographic lens, bicycles and network cables. Each time, it turns out someone else invented it before I was born.
Black is specifically designed to avoid being customizable, so you can't just exclude some cases.
It seems to me that there is a cultural problem that deep expertise is not valued, because it is difficult to understand and to get somebody "flexible" is easier.

I was just at a workshop about https://en.wikipedia.org/wiki/Design_thinking. The whole premise was that you don't actually need to hire an (expensive, inflexible) expert, who understands how something is done, but rather what you need to do is to "observe" an expert.

But imagine what happens when everybody does that! Everybody gets rid of their experts, assuming that the client (who they are supposed to provide the service for) has the actual expertise. And they are assuming the same about their clients and so on. The end result is complete disregard for expertise.

So expertise is a positive externality, in an economic sense. Nobody is incentivized to keep it more than neccessary. This leads to losses over time.
If you interview for Java or C# positions, editor matters. Give me an IDE. It'll take me hours to get the details right, because I'm used to the IDE fixing it
Thanks. From the Nature paper cited in TFA:[0]

> Here we use laser-driven shockwaves to simultaneously compress and heat liquid water samples to 100–400 gigapascals and 2,000–3,000 kelvin.

And in the phase diagram that you cited, it stays at ice XVIII over the whole temperature range.

0) https://www.nature.com/articles/s41586-019-1114-6
Oof, this is pretty antithetical to hiring. Author seems pretty frustrated. I hope this guy takes a long vacation. If I’m a candidate, I’d say this guy is clearly way overworked and I’d bail. Good points, but the volume of negative sadly speaks louder than the rationality of the points.

I see there being two parts to an SWE interview:

1) What experience does the candidate bring? Do they have compatible core competencies? If yes, then what’s novel about their experience—- will they help the team grok unknown unknowns? (And if the team’s burning issue is not unknown unknowns... then how does the candidate’s background add to the team’s creativity?)

2) How well does the candidate adapt on their feet? How effectively can they communicate? (If English is not a primary language, can they still get an idea across, perhaps using code instead of prose?). Can they code their way out of a paper bag?

The interview session is the interviewer’s responsibility to make the strongest case possible for the candidate. Let’s say that again: the interviewer needs to play doctor and adapt to the candidate. The interviewer is getting paid, not the candidate. Only once that sample has been taken properly can a hiring manager (who might very well be the interviewer..) begin to make an effective prediction as to how the candidate might do on the job.

Folks, demand for SWE jobs far outweighs supply. And it’s gonna be that way for at least another decade as universities catch up. It’s time to stop discriminating for the wrong reasons.
Yeah. It's really something.

Recently I started writing a bunch of tests for a Phoenix application for my first Phoenix app.

After a day of hacking around and learning as I go I had 63 tests of which 57 of them are full blown controller tests where a good amount of those tests are dealing with a "current user" and reading / writing things from a database. I'm even using a "Faker" library to generate fake data for all of the DB attributes.

The entire test suite runs in 600ms. That's 600ms for ~60 controller tests from start to finish. That's in a worst case scenario too where the code is on a non-SSD and that code is volume mounted into a Docker container on Windows while I use WSL.

Sometimes things work so fast that I'm actually worried it's not doing what I think it's doing, but then I run --cover and see that I have 95%+ test coverage on the things I care about, so that code is getting reached.
For every time I read about the threat general AI poses to humanity I try to find an article like this and it calms my nerves.
magnet:?xt=urn:btih:D69E07DD344D26ED13396141F6EA77A1DFC2348C&dn=codex-atlanticus.it
So author, who are you? You start already with an authoritarian touch. What makes you believe you are not an incompetent interviewer? How can an applicant assess your skills, you could easily be the greatest fuck up in the company. Is your company really that cool that I should want to die to work there? Did you first weed out all the incompetent staff that is duck sitting there playing business politics?

IMAO most companies are not any better than the applicants applying. And no, you didn't hire only the best from all candidates, you just have a rich imagination that favours your ego.
Passives are an information structuring tool that writers use to control how information is presented in a sentence. They can be used well or they can be poorly.

For example, on the page you linked to the first line of the body text reads:

> This example was created for training and is not official agency text.

The first clause of that sentence is in the passive voice — “was created” — and is a good example of how passives should be used. Nothing is gained by replacing it with:

> We created this example for training and it is not official agency text.
Ancient Romans Used Molten Iron to Repair Streets Before Vesuvius Erupted
ad 1.) yes, being a contributor doesn't automatically make you good programmer. But having 7 years of coding practice in several companies kinda does, because why else would those companies have you for so long? Yet these programming interviews are required even for them. Probation period is much much more telling about a programmer than the 15 minute coding task.
> An engineer at Stripe told me about their careful balance of email, forums, and Slack. They recognize that Slack is not suitable for meaningful conversations, so they automatically delete chat messages older than a few weeks to discourage relying on it for long-term archival. In retrospectives, team members often reflect on whether they chose the right medium (email, chat, or forum) for various conversations.

This is bad news for Slack's freemium economics. I'm going to recommend we don't upgrade with this in mind.
I think the only advice you need is:

- if you are creating figures: research and be empathic to the real reasons why people act like they do. Observe life

- be aware of the functions certain words, phrases, sentences or sections fulfill in the system of your text

- become a good reader: if you’re sensitive to language, this can be your failsafe, it will protect you from writing things you didn’t intend

- Just write and don’t be afraid to throw things out.

- don’t overly rely on dramatic systems, because you will end up telling low impact predictable stories like everybody else
Minecraft at 10
It's a good investment for the company, if the interviewer can red flag a candidate who is blatantly lying on his resumé because the candidate would assume no one would know said technology, it would save a lot of money from cutting ties with an employee in a later stage.

As an anecdote, I used to work for a company and would require candidates to know some Ruby, for one guy with several years experience in Python we changed the requirements of the home assignment so he could write it using whatever he wanted. he hands over a nodeJS application claiming he took the opportunity to learn something new(why not Ruby?), seemed like it was well done, so we bring him in for an interview, unlucky for him, there was one member in our team with some nodeJS experience(me), having reviewed the code, I asked him to do a minor feature addition to his own code, he froze, couldn't do it because he didn't write the code(copying from some repo) and didn't know any nodeJS at all, asked him to do it in Python instead and he still couldn't do it, he had just spiced up his resumé with tech we didn't use to see if he could weasel his way in.
A few years ago I went deep into an effort to make my own 3D animation company, all in-house software and everything from the ground up as much as possible.

I wanted to make the next Pixar, went far with the idea. Built a lot of working prototypes for the software we'd use all by myself. I built something I was pleased with and sought for a seed round and everything. I certainly don't know everything but I know way more than my fair share in graphics programming.

That's stellar experience and even with that I can't find any relevant graphics opportunities. I keep knocking on Pixar's door and they never have any open roles for the things we're looking for, and they never bite when they're open.

I work at Adobe now. Even here I'm not touching graphics :)

I'd love to hear someone else's take, because all I can conclude is that it's a saturated industry, it's a primarily academic industry (I don't have a degree), or I'm outside the industry network.
It's a very easy way to find the 0.5x engineer.

But I agree, it should not be a show stopper.

(Emacs and vscode user here)
I was interviewing a guy for IT position 6 years ago. After one of the questions, he went silent for a long period of time. It has not happened to me before. I did not think for a moment about interrupting him, it was obvious he is thinking how to approach the problem or his answer.
Interviewing people requires patience, cut down on caffeine before an interview
This PDF is not easily readable and it is from 20 years ago. Did the situation evolve ? Is it still relevant ?
> - "Let's see if you can do Fizz Buzz!"

Yes, exactly. I'd like to verify that you can string a few lines of code together to solve a trivially simple problem. This is not an unreasonable ask, and I really don't care how impressive your CV is. If you can't solve fizzbuzz you're not going to be able to solve any of the much more complicated problems we wrestle with on a day to day basis.
HPE (enterprise) was split from the slow-growing printer company a few years ago
But there is a reason people seek advice: writing is hard.

I've always wanted to write, and I sought the help of some pretty good writers. They gave me great advice. But no amount of advice can be applied to a blank page.

So I wrote, pretty badly at first, you can see it on my blog.

Writing is hard. Imagine, you have an idea in your head, and you like it. You grab a keyboard and write it down, somehow you write something else, not the idea in your head. You have to force your brain to say what it means to say.

There is no problem with reading other's advice, as long as you have some writing to apply it to. However, in my case I benefit more from reading what those people write, rather then read their advice.
I only have to edit a file on Linux once every couple of months of so - I tired of forgetting how to exit vi (or enter/exit edit mode, save the file... just about anything really), so started installing nano as the first thing I do on any system. Nano is so much more obvious than vi.