skysight-inc/HackerNews huggingface dataset:
Re: Uber Eats, now they also mark those notifications as "time sensitive" in the current version of iOS, including asking you to rate your meal or knowing that your delivery person says thanks for the tip. Even if I'm OK with getting those notifications, they are by definition NOT time sensitive
Most of them aren’t forking mastodon with a big name as a supporter as its only value.
Most fatalities happen off highways, despite highways accounting for a disproportionate number of miles driven.

Accidents still happen, but it’s hard to believe they would be less safe than human drivers, when most accidents are caused by fatigue, reckless driving, illegal maneuvers, and unusual driving on the part of the operator. It’s even harder to believe that it wouldn’t become safer with effort, when both the road and the behavior of cars is far more predictable.
> Does the candidate's degree (assuming no job experience) not obviate the need for this kind of thing?

I've met people with degrees who can't program out of a wet paper bag. And also people without a degree who can program circles around anyone. It only seems to be an indicator of your ability to finish a long term project, unless it's a top school. Then it's a slightly more positive indicator.

> Do past programming gigs not absolve them of the need to perform in a way they'll never be asked to perform on the job?

When I was doing interviews for Netflix for Senior Engineers, I always asked FizzBuzz on the phone screen. These were all people who had at least five years of programming experience on their resume with titles like "Senior Engineer".

50% of them were unable to do the assignment in any language with unlimited time.

So it appears that a resume is not sufficient either.

I hate puzzlers and quizzers and never use them (other than FizzBuzz, which frankly anyone who can code should be able to do). But I don't know what exactly we can replace them with.

I personally just ask the person more general questions to understand their depth of knowledge and then explain what the work will entail and ask them if they think they can handle that. Then I hire them and give them work and let them go (or let them quit on their own) if they can't handle the work.
> How much would you pay to get an organic HN front page discussion of your company’s roadmap?

Dozens of dollars! Seriously, that is the going rate for boosting an article to the HN front page (not to say it will stay on the front page, flagging and dang are quite effective).
Hi everyone :) This is from some new research I just published. You can read about the full methodology in this 22-page writeup[1] and I also made a tracker [2].

[1] https://github.com/kylemcdonald/ethereum-emissions/blob/main...

[2] https://kylemcdonald.github.io/ethereum-emissions/
Swift uses automatic reference counting. From some cursory reading, the major difference from Rust in this regard is that Swift references are always tracked atomically, whereas in Rust they may not be atomic in a single-owner context.

To my mind (again, with admittedly limited familiarity), I would think:

- Atomic operations in general don’t necessarily provide deterministic timing, but I'm assuming (maybe wrongly?) for Rust’s case they’re regarded as a relatively fixed overhead?

- That would seem to hold for Swift as well, just… with more overhead.

To the extent any of this is wrong or missing some nuance, I’m happy to be corrected.
> In my experience, porting code more or less directly from one language to another is faster and easier than people assume

Converting code to Rust while keeping the logic one-to-one wouldn't work. Rust isn't ensuring memory safety by just adding some runtime checks where C/C++ aren't. It (the borrow checker) relies on static analysis that effectively tells you that the way you wrote the code is unsound and needs to be redesigned.
My best interview experiences were light on the technical questions are mostly back-and-forth discussion around my experience/tech.
To keep with the computer jargon, it's closer to firmware. Like the ROMs that hold the boot-up code.
Stratasys | Fullstack, SRE, DevOps | San Francisco, Bay Area | REMOTE

Stratasys makes 3D printers. Our SF office designs and builds an IoT-connected DLP printer designed for mass manufacturing.

The printer runs on Node.js, C++, and we're adding Rust. Our cloud is hosted on Google Cloud Platform, running Node.js services in Kubernetes clusters. Web app and printer UI's are written in React and communicate with the API via GraphQL.

Our 3D printers are being used in production by customers internationally, are fast, and accurate to 100 microns.

Our software team is currently hiring:

* Senior Fullstack Developer - Working on our cloud backend, frontend, and printer UI. Plus, since most of the printer runs on Node.js, you can implement functionality end-to-end. https://careers.stratasys.com/job/San-Francisco-Sr_-Software...

* Site Reliability Engineer - Looking for a DevOps professional to maintain and monitor our cloud systems, set up alerting and on-call rotations, improve our infrastructure. https://careers.stratasys.com/job/San-Francisco-Site-Reliabi...

We're a very small team; your impact will be sizable!
Implicit CLSX in React
The way I structure my coding interviews is to have a simple first question that anyone should be able to solve, and then a follow-up "ok, let's now add this feature" question. I tell them upfront that googling is ok and give hints whenever I notice they are stuck. At the end of the first half, I ask if there's anything about their code that they'd like to change - basically a chance to code review. It tells me a lot about not just technical chops, but also awareness of what good practices are, as well as whether they are proactive and have an eye for quality.

The second half is the brownie points session: it's where the candidate gets a chance to demonstrate that they're better than average, be it by demonstrating strong algorithmic thinking, or good refactoring and/or testing practices or what have you. Good candidates ace questions on multiple dimensions and it's pretty easy to spot a gold nugget.

When the candidate doesn't meet the bar at this point, it becomes geared towards looking for growth potential (as far as me collecting signals go) and being an opportunity for learning for the candidate. It can be me giving feedback about types of things they could take into further consideration or, for less qualified candidates, a discussion of how to formulate an algorithmic idea, either in terms of thinking from first principles, or in terms of erasing dissonance between abstract ideas vs how to express them in code.

I try to always pace feedback in such a way that by the end of the hour, the candidate has completed the exercise. Sometimes, that does mean that I'm literally walking them through the process of coming up with the solution. Some think this is a waste of time, but IMHO, it's important for the candidate to leave with a good impression of the interview process. If a session is a complete bust and a waste of my time, then at the very least the candidate should be getting something out of it.
The railgun test videos I've seen were a lot more than "just make nice holes."

At that energy level you have significant damage from spalling from anything the projectile passes through, the superheated metal the projectile actually passes through is launched everywhere, there's the shockwave of the projectile, etc.

That's easily enough to be anti-personnel, incendiary, and obliterate electronics and cables and pipes and hoses. And have lots and lots of penetration, which on a ballistic arc could mean exiting below the waterline, and I imagine something traveling at supersonic speeds hitting water probably does some pretty impressive things.

If you send one of those projectiles through a magazine, missile battery, or fuel bunker - a lot of people are going to have a very, very bad day.
> And that's fine, isn't it?
Misleading begginers with bad routines that are possibly injury-prone wrapped in social media branding so it gets reposted everywhere isn't exactly fine IMHO
That’s interesting: I’d think a 30min commute would be much better if the 20-25min could be spent disengaged.
All their hardware engineering positions say they’re working on a mining ASIC, but it just seems like a huge stretch how that’s part of their business.
Anyone else think this is part of the natural life cycle of social media? Once something becomes big enough, even the users begin to monetize the content itself (meme pages, influencers). This is the beginning of the end. Everyone's just trying to milk it before it dies.

I don't see any ways to address this. Once enough attention is captured it will be inevitably used by someone to sell something. Developers want to get their ROI before someone else does and I don't blame them.
Take it to Telegram channel.

No algorithmic mess.
As far as I'm aware, survivorship bias is misestimating the probability of success.

It's not inherently bias to disagree about whether a risk is worth taking.

The choice depends heavily on the consequences, the relative value of success and failure, not just the probabilities.
I had an in-person interview where I should have said that, multiple times.
Communism and rent control's 100% failure rate has never dissuaded any of their adherents.
BUT!! The US has great magnet fishing - tons of guns thrown over bridges. (Be careful though - WWII guys threw contraband over these bridges - grenades etc).

https://www.youtube.com/watch?v=kQ9D1hcwq-8
Someone could do that, but the point of having the dest buffer size is to at least give the programmer a chance to try to get it right.

I also wonder if a linter could notice that the dest buffer size passed isn’t the actual size of the buffer. (That leads the the next problem in the code, if you look at the definition of that buffer, so that’s good.)
If I can do it in a way that's better suited to my use case, learn something from it and/or entertain myself, that may not be as bad a tradeoff as it may otherwise seem.

Reinventing wheels out of plain curiosity has exposed me to a variety of problems and their solutions, and I believe it exercises my general problem solving skills.
I learnt that in Community.

Jeff Winger:
Conversation was invented by humans to conceal reality. We use it to sweet-talk our way around natural selection, You know who has real conversations? Ants. They talk by vomiting chemicals into each other's mouths. They get right down to brass tracks. Bleh! "Which way's the picnic?" Bleh! "That way." Humans are more evolved. We lie.
I wholeheartedly agree with your idea of having a 2-way street of respect, and treating interviews less like interrogations and more like discussions. It certainly feels more natural that way, and puts less pressure on the interviewee.

Regarding Google specifically, I just interviewed there about 2 weeks ago, and although I didn't get the job, I will say I felt very respected, and with the exception of maybe one interview, thought everything felt like a discussion. There were no trick questions, everything was fairly straightforward. Basically a leetcode medium/hard for the 4 technicals and just discussing my experiences in various situations for the "Googleyness" interview.

I have heard similar stories about Google using these trick questions, but from what I understand these were mistakes made in the earlier days of the company and have been effectively phased out, although that is purely speculative.
They're not wrong. When I build something, it's mine and I control it. I get to learn about all sorts of interesting stuff, making me a better programmer in the process. If I publish it on GitHub, it becomes résumé material, helps other people and might even start a community if enough people start contributing. I get to contribute to the state of the art in free computing, advancing it not just for myself but also for everyone else.

If I pay for something else, I don't get source code, I get borderline malware that spies on me constantly, I'm subjected to idiotic non-negotiable terms and conditions and I'm at the mercy of some gigantic corporation that can kill the product at any time.

We don't pay for "something better" because it's not actually better at all. We're not laymen, we actually understand the fact it's a shitty deal. We're not some mindless consumer companies can just dump these products on. We have the power to create. The more we use this power, the better off we are.
I hate those websites which just proxy github or npm with a different stylesheet so much.
as a senior IC, I've been asked to give technical peer interviews for candidates quite a few times.

A LOT of the places I have worked there's no budget for sensible interview tools even for remote interviews (shared IDEs, etc), so you are stuck with what you can cobble together (an ad hoc shared REPL, a shared virtual whiteboard, etc). They suck a lot, and I try to keep that in account when working through problems.

The best experiences are always in an actual simple dev environment where you can collaborate on code, have a live preview of UI stuff, allow access to stack overflow and other references, etc. it allows you to present a problem very similar to day-to-day work but smaller scale.

And I gotta say, even that is just somewhat useful for gauging how working with that person for real would be.
Interviews suck - nerves are frayed, it's not always representative of that persons skill, ability or non-assholishness, AND it doesn't allow for assessing general skill, ability to learn or ramp up, because everyone necessarily in the interview has to have some skill in the language and platform you are working in during the interview.
Also, there's not a huge angle from "where the ball is supposed to go when it fires" to "where he's crouching adding energy to the system".
Did not appreciate the casual ageism displayed in this post, it added nothing.

“Leave it to another GenZ author.”
To be fair, the first 20 years don't count. That's just the beginning and the brain is still developing while being crammed full of miscellaneous junk. Many people die of cancer much earlier. Never ever take life for granted.
Sounds more like the parent holding company name change, Facebook.com is still Facebook and not changing, meta is just the parent company like Alphabet. I'm assuming the same for square.com.
You can have a "Close friends" list or multiple accounts. Neither is particularly UX-ergonomic, but that's what people do to address that need
>This is why I will never interview for Google or any other company that has multi-stage interviews and also employs time-wasteful, and sometimes esoteric, methods such as "How many jelly beans fit in a school bus?"

I said this once upon a time. then I realized I like money and I'm willing to dance a jig if thats what will get me beaucoup RSUs to fund my personal startup venture
In my personal experience, it doesn't take much to make the difference between a computer setup that causes RSI versus one that doesn't. When I was using my Amiga 500 for a number of years, I started developing carpal tunnel symptoms in my teens. Switching to a detached keyboard that could actually be placed at the right height for my posture was thankfully enough to allow my body to recover.

In the past decade the best change I made is switching to a combination of a standing desk + kneeling chair + regular office chair. By switching between different positions, my body feels a heck of a lot better. The kneeling chair is particularly effective at forcing my body into a much better posture position, and is good from recovering when the other options start to irritate things.
I lost a ton of weight walking a hilly 5k 4 days a week.
I was traveling for several months and would buy only as much food as needed. Worked great. Except once when I hit limit half way through my 5k.

Stopped traveling. Now house is full of snacks for kids. So yea…

Bad combo
Horrible name, horrible logo

Will be nearly impossible to find relevant search results about them, is that a bug or a feature?

Logo requires color gradients... will never look good on a t-shirt or business card. Even the favicon looks messy. Is that a bug or a feature?
It's difficult to know how best to react to interviewees being stuck. If you leave them stuck, they may take it badly; if you redirect them, they may take it as a sign that they "failed" this part of the interview.

I try to say something along the lines of "OK, I think it's time to move on to something else; in an interview situation, you sometimes go down a blind alley, but that does not really reflect on the real world, and I think I've seen enough to move on to the next subject."
when was this? I'm pretty sure facebook explicitly mention this in their preparation email now.
For the same reason we have Intel and amd
OMG the red tape at Apple is unbelievable, but this is the first time I've seen anyone mention it. On my first day at Microsoft, I checked in code. At Apple it took nearly two weeks to get granted separate access to the apps's sourcecode, secret OS version, secret Xcode version, secret new OS headers (for some reason this was a separate line item), upcoming hardware versions (which I never saw anyway).

Once up and running as a senior engineer with tons of experience, I had no autonomy and wasn't allowed to do something as trivial as add a comment without a bug database number and two code reviews.
> At the time optimized jar change broke antivirus scanners, which further sped up Firefox startup :)

I'm pretty sure that counts as cheating.

AV overhead is a real issue though. I was recently copying a directory full of small files from one fast SSD to another (larger) one. I started the transfer and Windows estimated about 8 hours to finish the transfer, and the overall progress seemed to be roughly on track. On a whim I tried temporarily turning off Microsoft's built-in antivirus scanning. Total transfer time dropped to about 40 minutes.
It's worse than TV, it's home shopping network.
> Can you go into more detail on the ethical obligation an engineer has regarding rigorousness of code review?

The comment I responded to was not talking about rigor. They said they weren't doing the code review at all.

> How does neglecting code review to interview elsewhere compare to neglecting code review to get other features out for the same employer?

If my employer pays me to prioritize new features over code review, then any bugs that arise are their responsibility.

If my employer pays me to do a code review, I take the money, and I don't review the code, then I'm responsible. My employer assigned the right amount of resources to code review, and I was dishonest about actually doing it.

> How about for a different employer that you're also being paid by?

I don't understand this one. You mean if you're a contractor and are neglecting code review to work on another contract?

If you're a contractor, it depends on whether you're being paid for time or whether you're being paid for good code.

If you're being paid for time, the above applies as well. If you're being paid for good code, then it's always your responsibility to review the code.
I think you’re making the GP’s point. No one cares about how much engagement with their pants they are getting.

They care that the whole experience delivers them what they value: fit, trendiness, status, consistency of the experience and the product, etc.

They care about innovation only when it reliability delivers an obvious gain on any of those stats, or when the market has moved to the point where keeping up with trendiness demands it.

So many brands are “premier” because they know all of this and just relentlessly deliver that familiar experience, maintaining their market position.

Software hasn’t quite, as an industry, figured out that sweet spot of innovation and consistency to be truly lasting. We’re too familiar with disruption - which is true, by and large, and sets us apart. Except once a category is defined enough not to need it. No one’s really disrupted email, despite many attempts, because it’s too ubiquitous and the consistency of experience demands are too great. It’ll happen eventually, but only as a long term evolution of overall trends and underpinning standards. Like the move away from breeches and onto pants.
> Always stuck me as weird as multiple papers have been written about that problem, are you really expecting someone to implement a solution to a problem that people spend weeks (months?) thinking about before publishing

except that these things aren't research material anymore and are now taught at undergraduate level.
Intro to Hubris OS [video]
The article also suggests that, even among products that are in no way nefarious, you should consider the geopolitics of the device’s server hosting location.
There wouldn’t be flame wars if you stopped letting people spread propaganda and lies. You rate limit me but allow the others who are spreading misinformation to run wild.
Does Hacker News think the singularity will happen?
Grab's pit stops along the road to its IPO
But many would if they could ;)
It is possible to stand up and tell the interviewer (while he's in mid-sentence) that it's not a fit, politely.
> This is especially jarring on a phone. Multiple times a day, I see this, and it pisses me off each and every time. Nothing like reading an article to all of a sudden have some image load somewhere (likely not even visible on screen) suddenly cause what you're reading to disappear off screen.

This is the worst on picture rich recipe blogs. I hate it.
For anyone wondering about the official documentation of the file format, PKWARE has:

* https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

* Via: https://support.pkware.com/home/pkzip/developer-tools/appnot...

6.3.9 was released July 15, 2020.
NIST is broadcasting a test signal on minute 8 of the hour on WWV and 48 on WWVH
My worst tech interview was with me as the interviewer. An applicant was a friend of a coworker and forwarded the candidate's resume to HR. HR set up a round of interviews.

He went through the five interviews. After, we met for 20 minutes to express our thoughts. Pretty uniformly we agreed: the candidate was middling and we'd be better off waiting for someone better. We rejected him.

A day later the rejected candidate called my phone (how did he get it?) and said something like: "Hey, this is <candidate>. Why the hell wasn't I given an offer? The recruiter said that you (that is me, personally) had rejected me. Explain why." He insisted he had done great and we should reconsider.

The candidate hadn't reacted well to the rejection, and rather than being the firewall that shields the interviewers, the HR guy passed the buck and blamed me. We didn't reconsider, and I gave the HR guy hell about it.
The video doesn't start until 7m39s, but HN wouldn't let me post the following link to that time: https://www.twitch.tv/videos/1220717732?t=0h7m39s

For those who prefer text (albeit a lot less detailed), the announcement was recently discussed here: https://news.ycombinator.com/item?id=29390751
There is plenty of outrage to go around, but couldn't prison conditions contribute to such violence?
https://nitter.42l.fr/blocks (the main nitter.net is down, this just the first mirror instance from https://github.com/zedeus/nitter/wiki/Instances)