skysight-inc/HackerNews huggingface dataset:
I created the f7u12 subreddit, so I thought it would be funny if I put the "reddit is down" graphic over the subreddit front page with CSS.

It had millions of subscribers. They all kept refreshing.
Feigning surprise is a rhetorical device, and a useful one. I'm surprised that more people didn't know about this.
Red Bull's World Record Pit Stop in the 2019 British Grand Prix [video]
>Instead of spending 30 hours reading a book, you can just listen to conversion among smart people in 30 minutes in podcasts

I don't understand this. Why can't that 30 minute conversation be transcribed into a script which you can read in 5 minutes? Either way, you're missing practically everything in the book.
One thing I don't get but is interesting is that humans inhabited Indonesia, Australia and Melanesia way before humans populated Madagascar. Now, apparently there were land bridges to Indonesia at different times (but not Australia or Melanesia but those migrations happened later) but Madagascar is populated much, much later into historical times.
What's the problem with just politely saying, "Can you please not interrupt?"

I'm assuming this option has already been exhausted and didn't have any effect.

I've worked with people who prefer to apologise all the time instead of changing their behaviour. When you bring that up they... apologise and move on.
XSS compromised a remote web app, not the vehicle. The vehicle hacked Tesla HQ, not vice versa
I'm wondering if the fact mine were He filled refurbs could've been a factor.
I mean...

If you don't like writing `if err!=nil {...}` throughout your code base surely you can just create some middleware function in its own package that has switch statements based on error cases. Checking for errors frequently in the running of the code is more or less a Good Thing.
Tell people that you're experiencing it. If you trust someone who doesn't seem to have as much trouble, confide in that person first, but continue to tell people privately when you experience it. In my experience, most people will take it seriously, and some will start to notice and do things like point out that you were cut off, or bring the conversation back around to you.

If you get pushback when doing this, I'm sorry you're experiencing that. My recommendation would be to find a new job, unfortunately.
Is your code still running? Did it suffer significant downtime? Did anything else break because of the new code? Did anyone do without water?
These satellites employ what are known as passive radiometers: devices that detect how much radiation is present in a specific frequency band. This radiation comes from water molecules in the atmosphere.

The problem is that 5G might emit in the same frequency range as well. This means your detector now measures the base load of the H20 spectrum in addition to the added 5G spectrum, with no possible method of separating the two.

Your proposal will therefore not work. Any measurement will conflate the two and lead to too much noise to discern the (H2O) signal.
We don't need 30 duplicate lines across country for competition so we don't need them for the last mile. And quite a few municipalities do allow multiple wires. But even so ISPs don't invade each others territory. The over-regulation stories, among others, are simply untruths promulgated to provide plausible pro-monopoly sentiment.

If the US wants something that works, then just do something that works. For example [1]

At any rate, the ISP arguments are well known. And are about as moot as appeals to a free market or the public good. In the current environment, no amount of evidence concerning monopolies will change policy that is fundamentally based solely on political favoritism and retribution.

[1]https://arstechnica.com/tech-policy/2010/03/uk-regulators-of...
As a show of respect and professionalism, I do my best to listen intently and to not interrupt my coworkers. If I am interrupted, I will stop and listen-- provided that the interruption served a purpose.

If someone repeatedly interrupts me without need in a conversation, then I will get annoyed with them, consciously ignore their interruptions and finish my thoughts, even if they keep talking. This usually sounds unintelligible to everyone involved. Once they are done trying to talk over me, I'll ask them a question relating to something I just said, which makes two points: 1. Now it's their turn to talk, and 2. They don't know what I just said because they were talking when it was not their turn to do so.
Well thanks for the insight!
With all the recent articles about sand running out (from rivers), microplastics, global warming, bugs dying... it sounds like we're screwing the earth big time. While I'm not the person who cares enough to completely change my life style, I'm getting worried.
I wonder whether this is just me, I hope not, but then again it also feels like the industry in general still doesn't care enough.
You need a better meeting leader. Their job should be to facilitate, which means keeping the meeting on track with the agenda, calling out interrupters, and making sure to circle back with the person who was interrupted to get their input, and then blocking the others from interrupting again. And a really good meeting leader will figure out who the soft-spoken people are and make sure to ask them for their opinions explicitly if they seem to have one that wasn't heard.
You can't compare it to Java checked exceptions. Java checked exceptions are one of those billion dollar "mistakes". It is the single worst thing in Java for me. Checked exceptions add nothing and break almost everything around clean design & code.

For that comparison to work, java would have needed to only have checked exceptions, with some added language features to deal with them cleanly, and then it might actually have been a viable design. Littering your code with try-catch is what makes exceptions infeasible for error handling.
I don't think folks are on 2.7 because they love it. I think they're there because it's difficult and expensive to migrate Python code.
Before you do anything, you should take Coursera's Learning How to Learn to make sure you have efficient study habits.

Khan Academy is probably your best bet. Paul's Online Math Notes, PatrickJMT, and BetterExplained can be useful supplements.

If you want to "bring a nuke to a knife fight", you could work your way through all of the Art of Problem Solving books [0]. They go much deeper than a standard curriculum so your foundation would be extremely strong (especially if you use Anki to schedule your review of problems/definitions you've understood and solved). Completing it would mean there's unlikely to be any math book that's outside of your reach. This is complete overkill, though.

[0] https://artofproblemsolving.com/store
I am pretty sure He uses lisp^H^H^H^H perl:

https://imgs.xkcd.com/comics/lisp.jpg
Yes. I have this tendency, and I have ADHD. I know I can tend towards it. I often find myself circling back to someone after a first meeting with them (when I realize I interrupted them a lot) and apologizing, letting them know I am aware that it's a weakness, and to please let me know if it ever gets out of hand (I intentionally ask them to decide for themselves what "out of hand" means, as some people are entirely ok with an interruption packed conversation).
Java-the-language was designed to be anti-clever, but a decade later, most code written in it ended up being the epitome of hyper-cleverness.

Lack of abstractions (a.k.a "cleverness") on the language level, pushed developers to abstraction on the code level, often based on reflection and supported by XML files and (later) annotations.

In retrospect, by avoiding cleverness in Java, we ended up with multiple incompatible framework dialects which implement their own cleverness.

Go avoided this fate so far by having weaker support for reflection, and since the collective developer memory of Java framework excesses is all too fresh. This makes Go code more readable than Java on average, but I don't think it's any more readable than idiomatic code in a high-abstraction language like Rust, Kotlin or Swift - once you learn and internalize how these languages work.
If someone has a portfolio I will certainly ask about those projects. Gives an opportunity to demonstrate technical acumen and communication skills at the same time.
It was a great joy to meet Mr. Kranz in the early 90's. I was part of a university seminar and a group of us had lunch with him, then heard him speak. I distinctly remember several key points that have been valuable to me in my career:

1- No matter what happens, stay calm and work the problem.
2- Plan for every possible situation.
3- Trust the team.
4- Understand the telemetry data.

I have applied these many times in my career and have shared with my teams the value of firm, decisive, and trusting leadership in technology. While there are many differences between an Apollo mission and an application launch or system outage, the principles are the same.
It probably varies a lot by area, I imagine. My biggest complaint with GMaps vs Apple is that GMaps has a bizarre fascination with asking me to jog over one block from the established route just to get around three blocks of congestion, instead asking me to make a left-hand turn from a side-street with no signal onto a four lane arterial road during rush hour. Yeah, there's a reason that route doesn't have any congestion.
The things is, those paychecks are very large. A Program Manager (Meredith's role) averages about $125k/year, and one with Meredith's tenure might make as much as double with stock and bonus. Google has been paying her salary the last two years even though most of her work is at AI Now.

Going forward as an NYU employee, as a university researcher without an advanced degree, she will be lucky to clear $60k/year. In New York. Doing the exact same work she has been doing for the last two years
Do or do not, there is no 'try'.
The average skill of most software teams is probably not far if not lower. I've been on very good ones and very bad ones -- lots of the code becomes least-common-denominator/weakest-link quality.
>So long as we can all agree that it feels super bad, I guess this is fine.

Actually, I don't think everyone agrees it feels super bad. I personally like having all of my error handling be explicit, painfully explicit even.

>approaches the Java world back with checked exceptions where principle trumped ergonomics.

I also have to disagree here. To me, checked exceptions are the worst of both worlds. Here you have additional language features, but nearly the same verbosity. Your 'happy path' must be surrounded by try blocks. Worse, everything that happens in a try block is 'flattened.' Not only does this mean you may need many try blocks, sometimes it can even be difficult to take individual statements and put them in one try block. For example:

try {
doThing(doOtherThing());
} catch(...) {
// What happens if doThing and doOtherThing throw the same exception? Do I have to use a temporary variable?
}

Also, exceptions have been overloaded to handle everything, including runtime errors. I think this is more subjective but I strongly dislike it. I do think runtime errors should be possible to handle, just ideally through a separate, more explicit paradigm.

try {
doThing(blah[0]);
} catch(...) {
...
} catch(IndexOutOfRange) {
// Handling runtime errors at the same level as application-level errors!!
}

Go doesn't even really force you to check your errors, it just makes it harder to accidentally not check them. Like:

result, err := doThing(); // Error
return result

result, _ := doThing(); // NOT an error
return result

I think this is excellent. It may lead to complaints about an annoying compiler, but most importantly it leads to fewer mistakes. You can still explicitly tell the compiler to shut up, but it is obvious.

Language ergonomics are complicated, but the benefits of Go's approach are hard to deny. Unfortunately, nothing comes without downsides, and it seems like solving the error handling ergonomics issue is a tough one. I think repetitiveness aside, the Go error handling ergonomics are great, and that's exactly why they attempted to reduce repetitiveness. But, in reflection, a lot of that repetitiveness can also be reduced by refactoring your code, so it may not even be quite as bad as it seems.
Thats illegal. Highly highly doubt Facebook or any company in the media spotlight will ever do anything clearly, and obviously illegal.
Relevant Steve Yegge blog post: https://steve-yegge.blogspot.com/2007/06/rich-programmer-foo...
Airport email scam thwarted by UK's cyber-defender NCSC
We have that on buses in SF. During the 4-5 years when I heavily rode the bus, fare inspectors came aboard exactly three times. When it does happen, it's no big deal, takes very little time, and there's no "humiliation" aspect (well, except for fare evaders, but they deserve what they get).

(Given the lack of frequency, I expect that there's a decent amount of uncaught fare evasion.)
How to Run SQL Server in a Docker Container
So you only used a site dedicated to your online network for the first contact and your in person network for the final conversion.

Seems like networks had nothing to do with your job to me...
And now Quebec also approved transporting aircraft fuel thru the downtown of Montreal.

https://mtlcityweblog.com/2019/07/15/trains-carrying-kerosen...

People just don’t learn ...
No, that is a cynical take based on the results of our having abandoned eternal vigilance in favor of simplistic ideas about how markets work. Corporations are for organizing complex activity. They exist because they can eliminate some of the costs of everyone acting as free agents, though that competitive advantage appears to be slipping over time.
Not great for handling Bitcoin transactions. I would highly recommend against using Cobol for any new cryptocurrency projects.
All corporations' business models relies on maximizing profit however they can and therefore will violate your privacy. It's that simple. Google = Apple.

(Hint: your pithy statement is equally meaning free)
Well, I've had two 4 GB boards for almost 2 weeks. They were also available on the launch day, but sold out very fast.
Not worth discussion: this is a paid service with ridiculous limitations (for $15/mo) one gets support for 'converting' 1 API with 10 endpoints in a team of up to 2 members.
Yeah, I can't believe they would forget that it's activated honey that converts to energy. Normal honey acts the same as sugar pretty much.
There were multiple reasons based on my experience. New people were still using 2.7 tutorials because there was way more information out there than for 3. And package managers in Linux systems took a long time to change.

But the asyncio example is probably a better example of a fundamental program design change that's causing weird fracturing and incompatible library designs. Trying to use non-async from an async framework is a mess, trying to use async from a non-async is hard to integrate, etc.
Interesting, but this seems more suited for subscription-type software businesses, not anything related to products with longer periods between repeat purchases. You'd have to wait for a couple of years or more to build out churn/resurrection/expansion, etc. and cohort data for a hardware or durable goods business. No wonder VCs don't really like to fund hardware/infrastructure businesses
This is great news.

I really like how errors are handled in Go and I hated this proposal.

The current implementation forces you to constantly think about errors at each single point and it is extremely good at standing out. This is something very valuable, not something that requires or needs to be hidden behind syntactic sugar. It improves the readability of the code and the quality of the software.

If it ain't broke, don't fix it.
The Rise of Instagram Marketing Pioneer Daniel Wellington
sorry for delayed response. I'm a hospitalist, so don't have an outpatient practice...
Sounds like python.
People, usually peer engineers, but occasionally executives, would try to rebut whatever I was trying to state as I'd state it.

I learned to be an utter asshole to these people.

When interrupted, I stop speaking. Entirely. Nine out of ten times the person interrupting realizes I'm no longer speaking and…also stops speaking. I guess they think this is a conversation? I don't know.

So I restart. From wherever I started, not where I was interrupted. Because I'm usually trying to get a coherent point across, an argument, a statement, whatever.

And if interrupted again…I stop and repeat the process.

I don't raise my voice.

I may throw a glare or two.

I have found that after two or three of these cycles the person in question waits until I'm done or I ask for questions or whatever the context demands.

In turn, I consciously try to refrain from interrupting someone else, especially women. I am in no way perfect at this.

I've had people tell me (or my manager more likely) that my silence in these moments is more intimidating than if I just barrelled over the interruptor.

I have heard that in organizations where there's recognition that this is a problem, a talking stick or some other object, helps: the only person who can speak has to have the object, they "have the floor" until they relinquish it.

And for the people who are prone to interrupting others: cut that shit out. You're not impressing anyone. You're not getting your point across. You may well have a valid point or issue or comment, but if the only way you know to make an argument is to disrupt anyone else…then that's the takeaway, not whatever your issue actually is.
True. But changes of that natures vs reimplementing the entire system?
Please link to some models with 4:3 screens. I've seen 3:2, but not 4:3.
> I’ve had take away (healthy and organic of course) at least two days a week since I left home.

Yep, same here. Though if I do cook, it has to be a massive production. If there's not something to be actively preparing the whole time, it's too boring to make. Which means there's gonna be a ton of dishes... that I really don't want to do.
The battle to rebuild centuries of science after an epic inferno
Big F deal
> It's a language intended to have few primitives with an emphasis on code being transparent and errors being values, requiring you to think about what they might be at each point as you're forced to carry them up the chain.

All of this is also true of the generic implementation with Result. Except that (IMO) it's much nicer to work with.
https://en.wikipedia.org/wiki/Railway_air_brake#Limitations
I spent years as a consultant reading codebases in different languages. I can tell you that Golang win hands down for clarity of code and structure of projects (and perhaps second after Rust in terms of security. If only it had options<>...)

So yeah, it's actually quite fast to dig in a Golang codebase. You notice that as a normal user when you find it faster to read the standard library vs reading the doc, or when you read an implementation instead of reading a spec/algorithm to learn about it.

My guess is that gofmt is a huge factor in this, but also the fact that there's not a huge amount of built ins, anf that the standard library is pretty complete.
Do you see the value in interrupt-based software? Why should there be any real distinction between software message-passing and human message-passing?

The complete rejection of interruption-during-conversation is equivalent to the denial of existence of far-too-long monologues, isn't it?
This is the prime example of what makes Go different than most other languages. They don't put things in attached with the argument "if you don't like it, you don't have to use it." Go is a language designed to be written and read by teams. You don't like try. Bob does. Bob writes code that uses it. You still have to read it.
I'm guessing it is a portmanteau of 'ginormous' (itself a portmanteau that has legitimately replaced 'enormous' for my kids' generation, much to my chagrin) and 'humongous'? Maybe with some relation to 'mundo' as well.
Matt brought up RA in the context of "speak the same language". In that context, freshman calc ticks the box.

His standards are high, but fair.
If only there was a use case for it
TurboPFor for ARM – Bringing SIMD Integer+FP Compression to the Smartphone
...or the alternatives were less safe (trucks) or too expensive (realigning the tracks).
Google: we hire morons!
Sugar gives you cancer.

Smoke(any small particles breathed in) gives you cancer.

Alcohol gives you cancer.

This is really not hard people.

Limit your use to what you find fun.
This is definitely the easiest for me to use, and to take without offence.
I really enjoyed Mr. Kranz book "Failure is Not an Option"[1] (which covers a lot more than just the malfunction of Apollo 13), and his subsequent appearances in documentaries.

I heard an NPR story[2] a couple of weeks ago re: the reopening of the restored Mission Control at the Johnson Space Center in Houston, TX. Mr. Kranz was interviewed as part of the story. It was a joy to hear him speak, even briefly. He's very inspiring.

[1] - https://www.amazon.com/Failure-Not-Option-Mission-Control-eb...

[2] - https://www.npr.org/2019/06/30/737327895/former-nasa-flight-...
The bad ergonomics? Golang is an excellent language.
In my experience this is true with any language. I think this is a function of talent and program complexity (the size of the forest), not the language.
Mine started to throttle in less than 10 minutes watching Youtube. About ~24C (75F) ambient temperature. 4 GB model, SD-card, no case, mouse and keyboard connected to USB.
I’ve been to a 10 day vipassana retreat. It didn’t change my life at all.

It felt a bit euphoric the first few days but then it wears off.

If you continue your daily meditation practice, I believe it might have a net positive effect.

My friend went about 5 times now. He swears by it.

Two anecdotes.
But nobody yet has confirmed this issue. It's been mentioned but without any supporting evidence.

Does anyone have a link or other evidence that definitively shows that Chrome sends my browsing history to Google independently of my signed-in status? That's what was implied. That's what I find hard to believe. That's what has not yet been demonstrated in this thread.
I can assure you the Canadian resellers are not profiteering (I'm not a Canadian reseller but have inside knowledge of their workings).

Remember the goal of the Raspberry Pi is to make computing accessible via a low cost. This necessitates the resellers having almost no margin. In fact, their margins are most likely negative after importation duties and taxes, e-waste levies etc, and they're expected to make up for this by selling accessories.

You mention the SDCard and Power Supply. It is good that the Canadian resellers are encouraging end customers to buy these (most will not be as sophisticated as the average HN reader).

Most users who have an existing Raspberry Pi will go and try to use their existing SD card and have it not work, or buy a cheap one (hear not Class 10 or above) from their local stationary shop and end up in a worse fate.

Most users who think they have a power supply that meets the needs of the RPi4, in fact, do not. This is primarily due to the new current requirements (hear most cell phone power supplies will not work).

One would be excused for thinking that your MacBook power supply would work, however, these power supplies are "smart" and negotiate the power requirements with the end device.

Unfortunately, the RPi4 does not support this, and "smart" power supplies do not provide it with enough current.

To summarise:

The resellers are businesses and not charities, they don't make money on hardware from the Raspberry Pi foundation and must make it up on accessories or some form of cross-selling.

They will no doubt go the same way as the independent Apple resellers, until that time they are still playing a valuable role in making it possible to purchase Pis in your country.