skysight-inc/HackerNews huggingface dataset:
Former Chicago suburbs native. Once you have kids, you’re not willing to take them to the Bean on a weekend and end up in the middle of a shooting. Taxes are higher in NY or SF, but if you have kids, you’re not moving there anyway (I’d pick Des Moines, IA or somewhere safe in the Rust Belt first). The weather might get better with climate change, but probably not enough to make the winters tolerable. It can get very cold, and you might as well live in Canadian latitudes those times of the year. CPS quality is low and likely to not improve in the time my kids would rely on it.

Chicago could be great, but the effort required makes it a deep long dated out of the money call. Some deus ex machina intervention is going to be required to reduce crime, reduce the debt burden, and right size public services so a productive tax base will stay. Ideally, one works remotely for a Chicago firm and visits when the weather is good (between Memorial and Labor Day).
LRO is that camera and that's what took the picture we have.

It's getting up there in years so we could probably build something better today but we haven't yet.
Send over the Chinese rover to investigate!
I just use files
I heard the same thing when off-shoring was the rage, and salaries are higher then ever for tech workers. I also suspect that with declining birth rates in 'industrial' countries, the market for tech workers could get even more competitive as people retire.

I've also been fully remote for 20 years now, and it just gets easier/better all the time...
Honestly it's not always a gift to have someone point out to you the 'movie continuity errors' to you all the time.

I tell my boss you want 2-3 people like me on the project. If everyone was like me we'd make each other miserable. I have worked on trying to frame these things in a positive manner. Unfortunately the guy who would have been the best mentor in that regard went into semi-retirement.
Guessing you don't write emulators. Or even read linked articles.
If you're concerned just get a roll up picture or greenscreen for your background
> most desktop computer users are able to use Firefox

Desktop-using software engineers can write software for desktop users in a ton of different ways. There's so much freedom and there exist multiple mechanisms and platforms to deploy your code.

Desktop-using software engineers are not free to choose how to deploy software to mobile audiences. They've got to go through Apple to reach 50+% of the US market. Apple sets unreasonable rules.

Unfortunately, Americans spend most of their time computing with mobile devices now. We've been forced into this situation.

Both Apple and Google have made our industry worse and more locked down than Microsoft in the 90's and 00's, and they both deserve to the the target of smartphone and browser antitrust lawsuits.
> Some of the explanations are questionable: I think they were overly simplified, and while I applaud the goal, some things just aren't that simple.

I am an expert on the subject matter, and I don't think that the overall approach is questionable. The approach that the author took seems fine to me.

The definition of certain basic concepts like 'consistency' is even confusing to experts at times. This is made all the more confusing by introducing concepts from the distributed systems world, where consistency is often understood to mean something else.

Here's an example of that that I'm familiar with, where an expert admits to confusion about the basic definition of consistency in the sense that it appears in ACID:

https://queue.acm.org/detail.cfm?id=3469647

This is a person that is a longtime peer of the people that invented the concepts!

Not trying to rigorously define these things makes a great deal of sense in the context of a high level overview. Getting the general idea across is far more important.
> If you fork a project often enough most forks will have such a thin developer base, they wither.

Spurious forks are a vector for attack. If your commercial product has FOSS competition, just encourage (finance) two or three forks of it, along the lines of any contentious issues. It's like splitting the opposition vote with fake candidates. It's not necessary for Firefox because it is a completely captured opposition, but it could be happening to other projects.
Ubuntu Security Notice 5494-1 SpiderMonkey JavaScript Library
This has existed for years before crypto, M-Pesa and PayTM to name a few, this is not new.
Sure, there's no problem donating now 5 months into the war. But what about when the war just started? How would someone from the U.S. be able to donate money and be confident where it was going? It's not like the Ukrainian govt had a well-known paypal address.
Somewhat, but even my pointer analogy just scratches the surface.

Filtering/selecting is big, but another interesting thing is that there are lenses (which I think are called prisms?) that only provide a view of something.

Eg you have a text document in Unicode, select all words marching a certain pattern, and then look as if they were encoded in ASCII. (No idea why this would useful :-) ).
>> There are lots of ways to provide feedback. I suggest stating the problem with the code and providing a solution. If that's the only possible solution to get past your review, state and don't ask. You can also give a carrot with "do this and I'll approve the merge."

Yes. This. Clarity is a prerequisite for tact.

Also, be consistent in your tone and style across reviews in a given project or org -- no matter who you're talking to. For instance, on one development project I was informed that all new tickets should use the language "shall" instead of "should" or "will." Consistent language gives everyone a common reference point and helps keep people from feeling "singled out."
I agree, maybe some author had this xenophobic side, but not all of them, and Gibson, which is made, arguably, the first Cyberpunk book, introduced the "japanese" tropes, and he did out of admiration.
The tone also deeply depends on the culture of the receiver.

Depending on whether their cultural background is North American, Scandinavian, German, French, Italian or Chinese (to pick from the very situations I have faced), and especially if they are more junior, you cannot expect the same outcome from the same feedback, without additional context/care in the communication.
You’re already advanced then.

Your claim about “within the first week” is a bit silly. I’ve used Linux on and off for the last 15-20 years. Just occasionally, to get certain things done in my development work. And I couldn’t tell you what any of those commands do (although I’ve probably used them a few times by copying and pasting). Advanced is subjective.
My plan to solve this "20 second bit of it" is that it's done at the analog hole. Whatever is painting those pixels, a smart TV for instance, will be coordinating with cloud services to fingerprint at a relatively high temporal resolution - maybe 5 seconds. The video itself is the signature. But we will need either trusted analog hole vendors or some trusted non-profit organization - or likely both. I think that "viewing" will be delayed by perhaps 30 seconds to allow for that signature analysis. These smart TVs will overlay a scorecard for all displayed content, and owners will be able to set device scorecard thresholds such that low-scoring content will be fuzzed out.
> Since when did having a trillion dollars guarantee success?

So then your answer is that Apple's browser is significantly worse than competitors, and that users wouldn't use this much worse product if it were not for Apples anti-competitive behavior?

> But to pretend this is about the "browser diversity

> Just say you want Chrome

I think most open web supporters would be a lot happier if Apple even simply allowed Firefox.

That would still be massively better than the status quo.

Are you saying that all someone would have to do is argue for allowing just Firefox, and you would no longer do this thing where you attack some alleged secret motivations?
I'm curious: What problems do you have with the Cloudflare dashboard that seem to be SPA-related? I use it regularly, and the only problem I can think of encountering is that it never remembers my "desired location" when it redirects me to a login form—If I go to view the firewall graph (navigating from my browser URL bar with autocomplete based on history), it will send me to a login page and then dump me back onto the big "overview of all sites" page. But this is hardly a problem specific to SPA apps! Every multi-page app I've ever worked on had to implement some sort of "login_desired_location" cookie if they want to get this right, and very few of the apps I use ever get this right—regardless of page architecture.

(The Google Cloud console is a complete nightmare, although I would argue that that's more for UX reasons then for SPA-specific ones—it seems honestly like the Google Cloud console is exactly as confusingly stateful and difficult to navigate as every PHP-based cpanel dashboard from the 90s: a hard bar to reach with any type of page architecture!)
They are regulated everywhere. Here in Iowa (as with most of the US) we don't have blackouts. Our regulators are doing something different and you might want to ask what.
Is there any good source for indie movies? I would like to watch more of non Hollywood style movies. Or at least fewer remakes and superhero style movies.
That part I agree with heavily. The upside on starting one vs being the first/second employee is massive.

At the same time if Travis Kalanick/ Mark Zuckerberg hire me as the first engineer then the odds of financial success go up massively.
I explicitly prefix Error: when I am requiring a change, Warn: if I am suggesting a change, Info: if I have an unrelated comment

Error: `< n` is an off by one error, the last element won't be processed

Warn: Consider dropping the loop altogether. We know there are always eight elements.

Info: Nice name!
Why does “high protein” food cause death?
> So you've spoken to a large number of the hundreds of thousands of African Americans who live in the neighborhoods most plagued by crime and know that they don't complain about it?

Chicago is really segregated. It's very easy to forget that one's experience in an expensive, largely-white, progressive, north-side neighborhood isn't representative of the city as a whole. Moreover, if the only "diverse" people you speak with are those who have had good educations, landed well-paying jobs, moved to a nice north-side neighborhood, and so on, you might not realize that they aren't representative of "diverse" communities more broadly (particularly when the portrait painted by the media differs so much from reality). TL;DR--we have to be careful when we generalize about "what life is like in Chicago" because it's easy to extrapolate our own experiences onto tons of people who live in neighborhoods that don't remotely resemble our own (and I strongly suspect that's what's happening when the OP says "most of the people I hear complain about crime are old white people that don't live here any more").
Well i'm off to get a library card now!
It happens all the time but often the community and the physical community don't overlap, but check out /r/MLM or other similar subreddits and there's whole groups of scammers who target particular groups (church, social, retired, veterans, etc) with particular pitches designed for that group.

Because if some rando tells you to join Amway or invest in AmCOIN™ you will tell them to get bent, but if it's a trusted friend, you're much more likely to be open.

It's disgusting, but it happens. And in a small town, likely everyone goes to the same church or two, hangs out at the same bar, etc. It can spread like wildfire, though usually after the first few scams it becomes known and starts to die out a bit.

Sometimes you recognize the situation and decide to "participate" (read: lose some small amount of money in the scam) to stay in the community.
It was a suggestion, not a demand. Anyone who reads stay/quit advice they read on the internet as a "demand" has bigger problems than I can help them with.
So your point is... that bluetooth is accessible via browser api? Yes, that's true, Bluefy is a whole browser built around that API, for example.

https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetoo...

https://apps.apple.com/us/app/bluefy-web-ble-browser/id14928...

So what? Apple has never required review of every web page you load with safari, regardless of which browser APIs they use... the browser is the browser. That is the farthest Apple goes on "dynamic content" but yes, it is potentially a pretty wide net given the various APIs and extensions. But from Apple's perspective it is also a defined boundary.
That may be true right now, but their banking system has had a lot of downtime this year.

https://www.wsj.com/articles/how-crypto-is-helping-ukraine-r...

> He noted that since “the national bank is not really operating, crypto is helping to perform fast transfers, to make it very quick and get results almost immediately.”
What would be a tldr for the paper (other than "it's a mystery":) )?
That's what people get for using Facebook.
I think of critical thinking as the art of being critical toward oneself when one is thinking.

In other words, when I read something and hear myself think, "oh yeah, that sounds right", there is another part of my mind that thinks, "maybe not".

Critical thinking is precisely what could have spared us from all of that 'cultural marxism' you mentioned, or at least, to do it in a way that is... constructive.
IE 4 and 6 were decent to good compared to competitors when released (although, IIRC, neither had ftp support?). What sucked was that they stagnated at that point in time while also becoming dominant. IE 5 for mac was well regarded, but I don't have personal memories.

None of the future IEs were very good though, IMHO.
You've done a good job here, but I might suggest stepping back even a bit further. If you want reviews to work, they must be in the spirit of "we all improve and learn together" rather than "bad dog! bad!" The tone you set in why you are doing them, who is involved, how they run makes all the difference in the world. What you want is to create a culture where it is safe to point out something that could have ramifications, and to promote a culture where there can be dialog about what's best for the health of the team and products you support. More often than not though, I've seen these meetings turn into "beatings shall continue until morale improves" sessions.

Just my $0.02.
Trollish usernames aren't allowed on HN because they effectively troll every thread they post to. Celebrity names are one variation of this, so we don't allow them as usernames.

We've learned that it's better to deal with this earlier than later, so I've banned the account. Happy to rename and unban it if you want to pick a more neutral username.

(Of course, if it happens to be your real name, that's entirely different, but in that case please email hn@ycombinator.com so we can sort it out.)

https://hn.algolia.com/?sort=byDate&dateRange=all&type=comme...
Pointing out the good in a PR is such an important thing to do, particularly with juniors!
Lots of good suggestions.

I don't think there are simple answers, and it's something you'll have to figure out separately for every reviewee, and sometimes every review.

You have to consider power dynamics, preexisting relationships, your own time, the importance of the change, and cultural differences.

If the power dynamics are too far apart, the right answer is often "don't". A high-level engineer or architect reviewing a relatively junior coder's patch should not be commenting on anything involving taste or stylistic suggestions. They should be reviewing for functionality, security, compatibility, etc. And only bring up maintainability or performance when it really makes a difference.

Some suboptimal code will get landed as a result, but it's better than creating a culture where the senior's personal preferences are always going to win out. When there's a power imbalance, nuance gets lost—the junior either has to bend to the senior's preferences even when they have a good reason to do things differently, or they have to go to a lot of effort to justify their position. Which is fine in some cases, but it's a waste of time and effort for things that don't matter as much. (This isn't about avoiding hurting people's feelings, by the way, though it does serve that purpose as well.)

I also agree that pointing out positive qualities of a patch can make up for quite a few critical comments. Explicitly constructive criticism (eg sketching out an alternative, or doing some work to provide data or justification for a comment) can also "buy" a smaller amount of more negative-sounding comments.

And of course, if you're swapping patches with someone regularly, there's no need to overthink it: state the problems you see, the things you're not sure about that concern you, the suggestions you have, etc., using as clear and concise language as possible.

In all cases, do not make the reader guess your actual opinion or intention. If you're couching a criticism in gentler language to avoid making them feel bad, that's fine, but don't play games or leave out important pieces. There's always a way to coach or criticize honestly, and you'll do yourself a lot of good by finding it.
Ask HN: Getting Started in the Bay Area?
Hey HN. I'm new to the Bay Area and here for half a year for an internship at a tech company (currently doing masters in EU). Looking to meet some cool people around here but other than some of the other interns + my housemate its been a little hard getting an intro. Meetups seem to be pretty scarce on meetup.com and the only other events thing I've found is via the bay area/SF discord, but that seems to be pretty biased toward SF. Would love to meet some cool people around here (in tech or otherwise) but it seems meetups have died down a little w.r.t threads from a couple years ago. I figured there's a good amount of locals here, any good tips? Thanks!
Why are founders assholes and cunts?
Default means that you are or have been technically deemed incapable of making any further payments. This includes repaying the principal outstanding.

You're confusing any potential amount ultimately recoverable in insolvency with some kind of imaginary ex gratia payment by a management of a imaginary going concern which absolutely doesn't exist in Ch.12. Its chapter12 in the circumstances conceived.
RFC #5: A General Taxonomy for Food and Beverages
"Get FF or some other browser a healthy market share first"

Why ? Open up the platform first.
Is it mismanagement? It's head-I-win-tails-you-lose. Why would Voyager be playing a radically different game than 3AC? That kind of leverage can mint a billionaire if the dice roll the right way.
It's a somewhat legit concern given that people have alleged they basically did that already with Firefox.

And the stats make me curious -- given that Chrome on iOS is just a wrapper around Safari, are people just switching because Google Docs tells them to, and that's enough? I'm having a hard time of thinking of a functionality reason to switch to Chrome in iOS (maybe browser/bookmark sync, I guess). I'm surprised to see a number that high.
Grab some books while you are there! My local branch totals up the money you save each year.
Seconding Database Internals - it's not just about "Internals of a database", as part 2 gets nitty gritty with the general problems of distributed systems, consensus, consistency, availability, etc. etc.
I only do this for configurations that aren't meant to be used by non-programmers. I don't want to have to explain for the billionth time that something like the path "C:\New Folder" isn't going to work as-written in a string literal, or that the name "type" is already taken.
I think we'll solve it the same way we solved similar transitions when text and image faking became easy: provenance.

For many years now, most have understood that you can't take text and images as truth because they can easily be simulated or modified. In other words, the media itself is not self-verifying. Instead, we rely on knowing where a piece of media came from, and we associate truth value with those institutions. (Of course, people disagree on which institutions to trust, but that's a separate issue.)
It's always crazy to me how much variation there is in energy use. For every person/business pulling out all the stops to try to shave a few extra kWh off their utilization fretting over leaving their cell phone chargers plugged in there's a store running a giant AC on full blast with the doors wide open to try to entice customers in with the cold air. I had an ex whose family had a giant house and all summer long they just ran the AC at max with the sliding glass wall open to keep the pool area cool.
I have a Master's in Public Administration but recently I obtained my certification in Data Analytics from Google. I got hired by Google less than 2 months later as a Policy Analyst and it has helped tremendously with my proficiency with spreadsheets and dashboards.
> Probably just people out with colds.

That's a leap. My understanding is that airlines are affected by the same thing every other employer is seeing -- they can't hire. It might be exacerbated by the fact that airlines reduced/eliminated their training pipeline. For example:

https://www.cnbc.com/2022/05/15/us-pilot-shortage-forces-air...

> The pandemic exacerbated a pilot shortage by slowing down training, hiring and creating a wave of early retirements.

> Airlines offered pilots early retirements to cut labor bills during the depths of the pandemic.

> The process to become airline-qualified in the U.S. is lengthy and expensive, making the barrier to entry high.
The town is mostly retirees and it was mostly the retirees that got suckered into it. Inflation eating away at fixed incomes and low interest rates undermining their investments.
You are describing France basically and it is still running correctly.
The tone of a code review suggestion reflects an underlying assumption about what a code review is (or should be). Often developers disagree on this point. It seems like we fall into one of two camps.

1. Reviewing code is like proofreading a paper. Suggestions are welcome, but there isn't an expectation that all suggestions be followed. The author of the code makes the final decision based on their objectives.

2. A code review is a gate that is closed until all comments have been fully addressed. The author must comply to the liking of all who choose to comment, or they are not authorized to continue.

The tone of review comments will naturally follow from their understanding. Understanding #1 yields comments aimed at persuasion. (Should we, Could we, You might consider) While #2 yields more compulsory language (Change ..., You should). Or passive aggressive language that is meant to be compulsory but softened to sound less aggressive (I would, Could you, shouldn't you).

It is my opinion that understanding #1 is most appropriate. It prevents unnecessary bottlenecks and is more respectful or differing opinions. If developers are peers, than #1 is the understanding the most accurately reflects that.