skysight-inc/HackerNews huggingface dataset:
Over the past few years in tech, I have interacted with and observed (as a fly on the wall) a wide variety of recruiters, hiring managers, etc. from companies as small as a dozen (usually around the time a founder/CEO brings in external "support").

There exists an incredible amount of arrogance and ego among them by-in-large. The best are humble and curious while maintaining clear and direct communication. To be fair, they are often tasked with making important judgement calls sans complete information, though that's the fault of the leadership/culture as to a poor approach.
Rich people tend to think they're going to have high quality kids and K select as opposed to the R selection the poor use? /not entirely serious
And often you won't have any idea what caused you to lose the job in a particular interview. There's generally no feedback at all so it can be very difficult to try to improve.
I bet that Mazda is stupidly easy to get into, start, put it in gear and drive though, and I bet it will behave predictably on the road like a normal car would. Everything else is secondary. Teslas definitely have a learning curve if you have never driven one.
I'm aware, but that's not related to my comment, unless you're actually claiming that programmers have lower standard of living in the western Europe compared to eastern Europe (which I believe to be false).
It’s kind of funny since before the Nazis, Communists were the original archetype of a violent fringe political movement that had lots of people murdered for no good reason. People were terrified of Communists and resolutely devoted themselves to making sure to stop Communism as fervently as possible, by any means necessary. Considering the millions of people murdered by Communists this is even a completely understandable and justifiable impulse. This is exactly why the Nazis exploited this fear.
It's worth noting that this appears solely to be a failure with Office 365/Click-to-Run-based installations. If you buy your software instead of subscribing to it, and service Office with traditional Windows Update mechanisms... everything is fine today.

This is what happens when you rip out well-tested IT infrastructure that has a reasonable update distribution process and entrust the cloud to update your software for you.
Did Microsoft adopt Scrum?
Why not MercurialHub?
Facts can be maliciously used to derail conversations and debates on purpose, or be used without proper context to push a certain view. Not everything is black or white.
... apparently you have to know that your (personal) Office 365 account is no good here? I thought maybe Microsoft cleaned up their confusing mess of logins a few years back. Perhaps not!

> You can't sign in here with a personal account. Use your work or school account instead.

Of course it works if you instead go to https://www.outlook.com/
Show HN: Tool for diffing websites and mockups – Matchstick
JD Powers get maligned a lot, but they're an industry tool

They sure are.
> We clearly need better tax laws to combat this, but I'm glad the commission is trying to fight this to the extent they can within current laws, and I hope they win the case on appeal.

I fully agree with the former, but—to an extent—disagree with the latter.

The thing that bothers me about this lawsuit is the fact that it is in essence an after-the-fact tax increase. If they want to reform tax law, then it should be forward facing, not trying to reverse previous established policies. Particularly not for the length of time this covered.

Globally, the US, EU, (UK now), Canada, etc, all need to get their ducks in a row and get taxation sorted out in a sane way.
I don't know why, at least consciously, but I've started to sleep less with the lockdown (italian here): from ~8hrs to ~6hrs, more or less, waking up fresh&ready.
I've also been more energic: I started running and started being more consistent with the weight training, sometimes both in the same day. Also lost 6Kg in the last 4 months!

But work has been the same: no increase or loss in productivity. Lockdown forced WFH, but I used to WFH for years. The only difference is that in the last 10 months I've been going to the office daily because of a new job, enjoyed the atmosphere and the colleagues. And because it was only an 8 minutes commute.
Apple excluded an app for Hong Kong's pro-democracy election from the App Store
> Very low CD8 T-cell responses

Do we know if this is actually an issue? A lower CD8 t-cell response might be expected given it's an RNA vaccine.
His mention of people getting through the writing gave me a thought. Many blog writers follow the advice that Google like 1000+ word posts. Some people even go so far as writing 3000-5000 word posts just to get ranking in search engines. From a readers perspective, I do not want to read a really long post. I am strapped for time, and I just want to get at the little bits of information I need to answer my question. How do you feel about lengthy posts?

That quote at the bottom is usually attributed to Aristotle.
> Tesla's have lots of new and untested technology. That's their appeal.

This saw gets trotted out whenever Tesla gets dinged for reliability. So let’s dig into it. What untested technologies are Tesla deploying and how does the affect reliability?

Well let’s review. The Model 3’s initial problems were metal panels not being installed correctly. A technology that has been successfully deployed on automobiles for over a century.

Now gaps are fixed, but they shouldn’t have been a problem at all. From what I understand the problem was caused by trying to have robots do final assembly and just lax quality controls, problems “legacy” manufacturers had solved decades ago.

Tesla’s iconic touch screens are delaminating [0] because Elon ordered screens to be installed that aren’t up to automotive grade standards. This is another unforced error.

And we haven’t even touched on the problems with the actual advanced technology, autopilot, which is once again oversold and underdelivers.

[0] https://www.thedrive.com/tech/27989/teslas-screen-saga-shows...
Would have to disagree. With any ad/tracking protection or non-chromium based browsers, the web client is not very good. For MacOS, it constantly requires reloads in order to get different folders, emails, or other basic functionality (Calendar, Categories, etc) to work correctly. The text editor is completely random in what it decides to do with formatting, links automatically have a gigantic preview link inserted into the text body, the UI is very much so different than the Outlook Client UI and does not port over any of the Outlook Client items (this is more a design decision in general from Microsoft on what is client side vs what is server side...)

The Web Client in its current form is functional, in that I can write and receive emails, but the experience is greatly diminished. Don't mistake me for liking the Outlook client (I am a very modest email user, no more than 400 some per day + a Tetris-style calendar), but this load crashes the client on a daily basis, on start up it takes a good 30 seconds before the client becomes responsive (with multiple local profile rebuilds), and sometimes just crashing randomly when reading certain HTML formatted emails.

Outlook is an exercise in frustration in general that unfortunately my entire company has built its foundation upon. The core ideas are great, but the execution on all fronts is awful. I'm actually almost disappointed when I open the mobile app and it __hasn't completely changed some UI/UX element__ as daily changes are the norm for me.

(all this being said, I'm shocked that Gmail somehow took Outlooks unusualness as a challenge and designed a worse UI/UX experience...)
JD Power is akin to paid studies like an IDC "Study", or Gartner and Forrester "research". Or even better - Tolly "reports". And finally the complete sham that is NSS Labs. They're all pay for play - and using NSS as an example, they get paid on both sides. First the vendors pay the "lab fee" (source: I worked for a large security vendor and was involved in this process) to be included and for any reruns of the test if you don't like the results. The other half of it is charging customers for the "unbiased" reporting / research. It's a racket. Someone sent me a link to this JD report last month and I just responded with a rolling eye emoji. JD Power has declared GM/Chevy the winner for their entire existence if you watch any of their commercials. Clearly it works to an extent. And their loyal buying base oft references the "quality" represented from personal experience.

However, starting that conversation about the JD link got me looking. I started comparing reliability of Tesla to all other luxury brands in my subscription to Consumer Reports (they, at least, they buy what they test and have no brand influence or conflicting interest). While the Model X seems to fare the worst the Model S doesn't rank lower than comparable BMW, Mercedes, Audi, etc for the most part. In a lot of those direct comparisons Tesla has higher reliability, but still relatively poor given the cost of the product.

I fully agree with the parent comment here. Tesla likely told JD to go fly a kite and JD's enterprising sales folks went to Detroit and conjured up a nice fluff piece. Or, maybe this is a sign of Detroit starting sling mud because, too little too late. From my perspective I hope Detroit gets their act together quicker than they have been as I'd like more choice for EV. I don't own any Tesla products, but I likely will in the next 3-5 years if the current landscape of EV options doesn't significantly change. I like the idea of a lot of the concepts Tesla has brought to market, but as a consumer I don't really care what badge is on the vehicle anymore. It's unfortunate those who are competing are often lacking in many ways when compared to the current market leader.
Yeah, my impression is that they haven't found anything interesting except shitty security of a widely deployed web app.
Chrome does warn you every time you open an incognito tab that "Your activity might still be visible to: Websites you visit".

And as long as you don't log into Google, Facebook, Amazon, etc. accounts during that incognito session, third party sites really can't track you once the session ends. (Yes fingerprinting is a thing but I don't think it sees that much real-world use.)
Yes! Well first and foremost, Alyssa is an amazing entrepreneur, someone I really enjoy speaking with, and is Canadian, so not much more to ask for there.

We catch up from time to time and I can imagine us partnering down the line. Notably, we do already partner with major female fertility companies in this space to offer packages for couples (like with Ava Fertility, a very rigorous and data-driven company that helps women track their ovulation periods)

I'll just add that we actually do testing & freezing as two linked but independent offerings. So Lilia matches the freezing component of what we do. A company like Modern Fertility (also YC) is closer to the testing component of what we do.
I wasn't referring to that, thanks. I was referring to your own irrational willingness to hand over the same data based on how they ask for it. Maybe it is rational; you know they're not getting any useful data with an opt-in, so you'll play along with their incompetency by handing them a single datapoint?
> The theory is that the incineration of so many cities, and the subsequent firestorms would put vast amounts of smoke and particulates into the upper atmosphere. It’s this rather than the bombs themselves that has the main climatic effect. The fact that all these particulates would be radioactive is an extra dimension to it all.

Some later Googling of mine found some stuff about how the nuclear winter theorists's models made predictions that oil well fires would result in a small scale global winter, but the Kuwaiti oil files did not confirm that prediction.

https://en.wikipedia.org/wiki/Nuclear_winter#Kuwait_wells_in...:

> One of the major results of TTAPS' 1990 paper was the re-iteration of the team's 1983 model that 100 oil refinery fires would be sufficient to bring about a small scale, but still globally deleterious nuclear winter.[109]...

> In articles printed in the Wilmington Morning Star and the Baltimore Sun newspapers in January 1991, prominent authors of nuclear winter papers – Richard P. Turco, John W. Birks, Carl Sagan, Alan Robock and Paul Crutzen – collectively stated that they expected catastrophic nuclear winter like effects with continental-sized effects of sub-freezing temperatures as a result of the Iraqis going through with their threats of igniting 300 to 500 pressurized oil wells that could subsequently burn for several months.[110][111][112]

> As threatened, the wells were set on fire by the retreating Iraqis in March 1991, and the 600 or so burning oil wells were not fully extinguished until November 6, 1991, eight months after the end of the war,[113] and they consumed an estimated six million barrels of oil per day at their peak intensity....

> The atmospheric scientist tasked with studying the atmospheric effect of the Kuwaiti fires by the National Science Foundation, Peter Hobbs, stated that the fires' modest impact suggested that "some numbers [used to support the Nuclear Winter hypothesis]... were probably a little overblown."[119]

> Hobbs found that at the peak of the fires, the smoke absorbed 75 to 80% of the sun's radiation. The particles rose to a maximum of 20,000 feet (6,100 m), and when combined with scavenging by clouds the smoke had a short residency time of a maximum of a few days in the atmosphere.[120][121]

> Pre-war claims of wide scale, long-lasting, and significant global environmental effects were thus not borne out, and found to be significantly exaggerated by the media and speculators,[122] with climate models by those not supporting the nuclear winter hypothesis at the time of the fires predicting only more localized effects such as a daytime temperature drop of ~10 °C within 200 km of the source.[123]
But the salesguy said these things wouldn't happen!
Using Data Science to Help Make Dangerous Bus Stops Safer in Detroit
The article does actually point this out near the end.
But batch size is prob least problem since you can do data parallelism (send half batch to each gpu, combine on cpu).

I think only model bigger than gpu mem is where you really wish for nvlink on v100s.
Probably would be best to put a time limit on it - first five minutes you can edit and then you're done. I know I've sent more than my fair share of tweets only to realize I'd misspelled something and have to decide if I want to live with the shame or try and fix it before it's noticed.

Anything longer than that is probably going to get into the historic revisionist problem.
I mean this would apply to going on a first date as well. First impression is what matters and once the impression has been ruined, all bets are off.

It is not specific to the interview process.
Lithium Treats the Brain [video]
+1 on spelling. Having gone through thousands of resumes, I've seen some hilarious things. I'd never take away points for a couple of errors, but blatant ones are definitely a turn off.

Also, a public service announcement: if you were leading a project in the past, its "led", not "lead" :)
> instead we have a shrinking middle class, as the fuel is drained from the engine.

And yet in recent years, the middle class is more and more blamed for the inequality and other big problems of the world.

In multiple EU states, there's no mainstream parties representing the interests of the middle class.

At the same time the truly rich are laughing on their way to the bank.
I'm not commenting on how anyone else does it, or saying that there aren't bad patterns out there. I'm telling the room about a strategy I found that lets me twist the bad into good.
I have found errors in sections of my resume from ten years ago, looked at by me and many others dozens of times.

They can lurk.
There is literally no way right now for any company to assess the false negative rate, i.e. how many well-qualified engineers they turned away. They can only assess internally the false positive rate, i.e. how many engineers they thought were going to work out that did not. The fear of making a "bad" hire, is so pervasive that we optimize entirely to minimize the number of false positives, completely ignoring that making the interview more and more difficult is probably having a marginal effect on reducing the FPR but is drastically increasing the FNR.
Here's also a demo of the dock in action I recorded a while back: https://www.youtube.com/watch?v=yBeza4UNOm8
Agreed, what would be better would to maybe put the engagement stats(faves,replies, etc) to the right, expand replies to each tweet when clicked on pop from the right and then descend, but the thread itself a contiguous block of text/tweets all the way to the authors last tweet in the thread.
I have a background in IT. I basically moved back to IT. I still write some code but its not the majority of my work. The code I write now relates to automation and integration and not so much building a product from the ground up. I have to build for reliability but I don't need to build for Internet scale.

Edit: I should say that the interviewing experience that put my over the edge was actually not a whiteboard but a take home exercise. What I didn't know and didn't appreciate was that it was designed with an adversarial review. There was a long list of requirements and I thought I met them all. The response was kind of rude and was a big turn off. After a second pass I was told that I was missing some fundamental things, which were never requested or discussed. The whole thing seemed designed to exclude rather than assess.
Programming in general is language and framework agnostic. Someone who can write an extensible and maintainable C++ application can most likely do the same in C#, Java, Rust etc. There's decades of best practices and knowledge around what makes good software and almost none of it is specific to a language.

Most devs use a handful of algorithms in their entire career. And any algorithm they do use was probably adapted from pseudocode on Wikipedia.

It really comes down to what do you want the developer to do? Are the things you're testing them on even relevant to the job?

I'd argue what most companies are testing through their interview process is largely irrelevant.

If it's a generic programmer, then it's perhaps a position where's there's a range of technologies, maybe a range of languages to pick up and a range of existing software to support. Well in that case you want someone who's quick to learn and eager to train themselves, not afraid to ask questions, not afraid to admit they don't understand something, etc. Whether they can write quicksort on a whiteboard is probably the stupidest thing you could interview them on.

I think the best kind of interview isn't overly technical, but rather one that prods the interviewee to think about problems. Describe a fictional system, what would they suggest to make it scaleable? What would they suggest to improve performance? What would they suggest to reduce the time between writing the code and shipping it. Do they understand what a CI/CD system is? Are their first thoughts "rewrite everything!"? Do they think about iterating software development or are they the kind to dump 200 files on someone for code review?
If the reason why your lungs don't work is a virus, as in this case, you're not just talking about your own freedom, you're talking about the freedoms of others. And given that these brave people are the first ones to line up in the ER, this is obviously an issue of public health, it has the word 'public' in the name for a reason.

We're living in complex societies where reckless behaviour puts others at risk. If you live on a sheep farm in the appalachians do with your lungs what you want, the reality of modern urban society is that we're interconnected. In that context freedom and safety are mutually dependent, even reinforcing.

The idea of "I can do with my X whatever I want" and then stop thinking there and calling everyone a fascist or an oligarch made a lot of sense if you're a 18th century homesteader, it doesn't make much sense today.
It's also useless in time frame. This is over the first few months of ownership. I've owned two of the cars that rank near the top of this list and it's problems after 5 years that I care about. That's when you start to pay out of pocket and the problems get big. Most cars, now, don't survive ten years, but I want a car that's reliable from year 5 to year 10.
They used to have real-time graphs and stuff on their status page. That was a thing of the past; with more distributed system, they're probably not sure if the service is down everywhere. If a node somewhere is still up, they might consider the service up. I don't know much, but it's up to the kind of downtime measurement system they have.
PGI's Fortran compiler, bought by NVidia a few years ago, has excellent GPU extensions. You set an attribute on an array, move stuff on there, do your computation, move stuff back. It was the easiest GPU coding experience I've had.
> A lawsuit settlement agreed to by Eberhard and Tesla in September 2009 allows all five (Eberhard, Tarpenning, Wright, Musk and Straubel) to call themselves co-founders
2014 I got my tesla. I’ve had one issue and one recall... equivalent expensive luxury cars range rover,bmw, Benz of the past... by 2-3 year mark all are thousands in maintenance monthly. Tesla for me at least has been a game changer. Cost aside I don’t think about my car much except for the occasional thread like this...
Right but I also do think that FAANG is over-estimating how many of and how bad these "bad apples" aka. slighly above average developers would be and how terribly difficult all the work they do is.
Personally, I think this is a measure of the expectations for the brands. Dodge and Kia offer entry-level vehicles at a really good price point.

Most people aren't buying Dodge vehicles for their luxury interiors or refined ride qualities. They're getting cheap kid haulers or affordable muscle cars.
A pro tip for anyone reading this who ever ends up in a similar situation: just postpone the interview. I promise you that everyone will understand. Everyone gets that these things are a little goofy[1] and wants to set people up for success and not doom them to failure.

1. Yes, there is a larger and more complicated discussion to be had about making the whole system better. But that isn't gonna happen in the short term. This is advice for dealing with the situation as it exists today.
Oh, now I understand.

I'm pretty sure that's the local Google Maps client app rifling through the locally-stored photos (because it has permission to see the metadata for photos on the device). I can see how one could find that creepy, though I think it's relatively harmless. Is the specific issue that one doesn't want Maps to be able to infer you took a photo at location Y just because you once uploaded a photo at location X? Is the issue server-side Maps making the inference or client-side Maps (b/c client-side knows where you are and can see your photo metadata, so it doesn't actually need a server in the loop to ask that question)?
It depends on the culture setting.

If you're in a place where an IC can potentially make half a million or million dollars a year and drive some very interesting project work and be highly respected, no.

If you're in a place where not making it into manager track puts a very low ceiling on earning potential and respect, then yes it can be condescending.

This varies a lot by country, industry, etc.
At least you won't have to rename "trunk" to something else years later for some PC reason.
AKA, nothing to hide argument.

https://en.m.wikipedia.org/wiki/Nothing_to_hide_argument
Likely unrelated, but I recently noticed that GitHub stopped updating my activities overview for july. I definitely pushed commits, but they are not noticed. Anyone else having a similar issue?