skysight-inc/HackerNews huggingface dataset:
When I mentor interns about how to present or interact in meetings, I always stress that if they are a stakeholder in a project that is discussed, they should be prepared to add something intelligent to a discussion about it.

“Something intelligent” isn’t pithy commentary, it is a contribution that adds some value to what is happening.

In the context of LinkedIn, you’re always selling something. Either yourself, your company/product or something else. Usually that means offering something that makes you look smart or empathetic to stay active in your extended network. Many people are very bad at it.

Personally, I post about the nonprofit organization whose board I serve on. I may get some brownie points, but mostly it’s marketing so I can try to liberate peoples money later to donate to the cause.
That is correct without I2P, Tor or a VPN.
>Both are relevant for how we treat people, but gender, at least with our current social assumptions, is an exclusive or, while old people have already been young.

How do you reconcile this with fluid genders and non-binary genders?
Go2hx: Go to Haxe Transpiler
(An active successor to Tardisgo)
I found myself wishing for a few code snippets here. It would be interesting. A lot of time code that handles "connection refused" or fast failures doesn't handle network slowness well. I've seen outages from "best effort" services (and the best-effort-ness worked when the services were hard down) because all of a sudden calls that were taking 50 ms were not failing but all taking 1500+ ms. Best effort but no client enforced SLAs that were low enough to matter.

Load shedding never kicked in, so things had to be shutdown for a bit and then restarted.

Seems their normal operating state might be what is called "meta-stable" - dynamically stable at a high thru-put (edited) unless/until a brief glitch bumps the system into the low work being finished state which is also stable.
>I'm quite impressed that it's still being actively developed 30 years later.

Looks like it's being modernized to build with c++11 compilers
To me “scientific consensus” is a wave of the hand response too. It’s generally dropped in these discussions by non-experts without much knowledge of who makes up that consensus or why they disagree with the dissent.

At any rate, I see both sides. I don’t trust big pharma or government, but I trust my doctor. If tomorrow he tells me “don’t get the next booster”, I’m not going to get it.
Hrm, technically speaking that is true. Sex is not even binary—it is bimodal. I was trying to give a simple explanation
Because it's not a community, it's a marketplace. Never confuse the two.
If I'm not wrong this vulnerability affects Log4j 2.x onwards and the latest EJBCA from https://github.com/primekeydevs/ejbca-ce appears to be using only Log4j 1.2.17.
Is it typical for orgs (the whole spectrum: IT departments everywhere, telecom, SaaS, maybe even status of non-technical services) to have automatic downtime messaging that doesn't need a human set of eyes to approve it first?
Thank you for the sympathy. If we are talking about the same product then it was most likely backed by 3 different storage services over its lifespan, 2013/2014 was a third party product that had some replication/fail-over baked in, 2016-2019 on my team with no failover plans due to "deprecated, dont bother putting anything important here", then 2019 onward with "fully replicated and automatic failover capable and also less cost-per-GB to replicate but less flexible for the existing use cases".
But the US is 120V, not 110V.
Thanks! This sentence mirrors pretty much everything I was looking for: "Think of it like jQuery for the modern web.". Gonna check it out. :)
I worked at AMZN and this perfectly captures my experience there with those weekly reviews. I once set a project I was managing as "Red" and had multiple SDMs excoriate me for apparently "throwing them under the bus" even though we had missed multiple timelines and were essentially not going to deliver anything of quality on time. I don't miss this aspect of AMZN!
Backblaze takes service offline due to Log4j
> It takes a lot of skill to constantly produce content at the rate that millionaire twitch streamers do.

Well, that's disputable. Most content-sources are delivered externally, in form of games and stuff they can react too. It's not like they sit there and think up something fresh by themselves for 8 hours a day. Though, yes, they have some naturally skill in socializing which they hone over time. But still I would not say it goes beyond the skill of any other natural socializer which exists in any community.

> Most of them own youtube channels as well, which requires additional time to process, edit, and mix videos, depending on what they're doing with it.

Which is most of the time not done by them. Usually they pay people for this. And to be fair, Videos of streamers are usually not really masterpieces either. They are optimized versions of their streaming-content. A good youtube-creator has significant more skill there. They occasionally also create far higher quality of content than most streamers.

> It's an incredibly demanding gig, that, at the very least, requires a pretty insane schedule, or being really passionate about the job.

How many streamers do you actually know? Well scheduled is not really what I would call most streams I've seen.

> Maybe some streamers get help in production and orchestrating their stream, but for most it's more than a full-time job commitment.

If you are a fulltime-streamer, earning money, then they pretty much all get help to some degree.

> Those average Joes you mentioned? They get 1-2 viewers, who are usually their closest friends.

Not really. They are many dedicated hardworking people with similar skill-levels even on the lowest levels. Success in streaming depends far more on luck than skill. Though, luck is also a skill in some way, so hard to say...

But the skills I was talking about are not the ones you are getting naturally but being alive or just doing stuff long enough to acquire them. Obviously if you stream long enough you get a bunch of skills and knowledge automatically, which any non-streamer is missing yet. But that is nothing special.

Special is stuff not everyone has or can acquire on it's own. Like a professional who went through a long professional training, reaching a level of quality a normal selfmade-streamer never can reach. Or someone which a career outside of streaming. There are more and more people like that hitting the platforms. Many entertainers with decade-long careers came in the pandemia to twitch and youtube, searching for new playgrounds and displaying skills which leaves any big established streamer in the dust.
It absolutely is difficult. A challenge I have seen is when retries are stacked and callers time out subprocesses that are doing retries.

I just find it amusing that they describe their back-off behaviors as "well tested" and in the same sentence, say it didn't back off adequately.
> leader of the hacking group LulzSec (who by then was cooperating with the FBI)

Is this the same hacker who has gone on public record that he got paid by the FBI to lie , and as a result was later redacted from the court documents?

Paying for false witnesses is such a classic and really makes for a strong case.
If you do a lot of VPC Endpoints to clients/thirdparties, you learn the AZIDs or you go to all AZIDs in a region by default.
Yes, it's disappointing but hardly surprising to see the phrasing of management parroted by so many developers. It's their job to worry about hiring, deadlines, etc. It's yours to make sure things don't shit the bed at one in the morning, especially if you're going to be paged about it. There are some languages that make it very easy for grads to deliver features, and others that are far more likely to be correct at compile time. The "best tool" is born from these competing demands; those too meek to engage with this inherently adversarial process don't do themselves or anybody else any favors.
I kind of want to try to make a "74 series logic" RISC V CPU at some point so I can inherit the compiler.

It's rough building the larger systems though. All the early logic is still around for the most part, but most of the "medium integration" parts have disappeared. Things like register files and bitslice ALUs. (74x181, etc.)
For an eye-opening experience, explore the network of people who list themselves as recruiters for oil companies.
I tried to refinance with better.com a few months back. The quality of service was just not there. Mortgages are still very paper intensive processes with lots of middlemen and lots of procedures. You can build a slick interface but it's going to a hamster wheel behind the scenes. And if you can't have a good customer service people are just going to steer towards someone who does and can hand hold you along the way.
One of the biggest obstacles in this kind of research is 1) the human tendency to anthropomorphize in our explanations, 2) to over interpret findings from a behavioral task that is based on analogies, but can be solved in multiple ways. The latter is very dangerous in the brain sciences:For example, inhibition can happen in a microcircuit of neurons to reduce neuron firing, or inhibition can be thought of as the cognitive capacity to refrain from a behavior you are predisposed to do using cognitive control. These are not the same things.
If Omicron continues to grow at the present rate,
Omicron case numbers are projected to reach parity with Delta cases in mid-
December (this was dated 10th Dec).

Vaccination is less effective against Omicron than against Delta. But shortly after a booster dose, there is about 70% effectiveness.

I haven't got on to anything about hospitalisation rates vs Delta yet; it may still be early days for that.
I've been active in the computer industry as a professional since the mid 80's and can tell you that most of these companies screwed themselves up through complacency, idiotic business decisions and being acquired by larger players that ballsed up their products. Their products got worse, releases delayed etc etc.

I can cite one of many concrete examples which is Ashton Tate. Some young upstart with a compiler called Clipper by a company called Nantucket came and ate their lunch because dBase IV was a pile of crap. Sadly Nantuck got bought out by CA and that was the death knell. Microsoft didn't kill Clipper, CA did.

Sure in the 90's (late) Microsoft may have been a ruthless operator and stole many and various cheeses, but they were low hanging fruits (apologies for the mixed metaphors) and you can't blame Gate's and co for taking advantage of idiotic commercial choices made by people who were asleep at the wheel.

Sure Microsoft have abused their monopoly position during the browser wars but when it came to the old school productivity suites these older companies just weren't agile enough to protect their positions.

But don't let facts get in the way of a chance to bash Microsoft. Read that book, I'll even buy you a copy.
I agree, but describing the “dark ages” as a time of low technological progress is wrong for a variety of reasons. Not the least of which being that it is atrociously eurocentric, and moreover it ignores the many important inventions(for example, crop rotation) to come out of Europe at the time.
A drive-by pronouncement, one that is probably wrong because of how reductive it is, but it is visceral to me because I've been dealing with a similar situation at work: you can't trick computers. You can't intimidate them into working with groupthink, coercive meetings, aggressive talks, or vague threats of losing face, position, or job. They are binary. You either make something that produces the output you want, or you get a buggy, unworkable mess (to various levels of unworkable).

All the crunch and pain and buggy games are a result of humans trying to force the other humans who are programming the games and content, and indirectly, the computers themselves into doing a rush job.

You can't rush art. Programming is an art since whatever is being programmed has never been made before, else you could go Copy + Paste and be done.

Yes, there are millions of paintings of meadows, just as there are millions of copies of very similar but ever-so-slightly different boring line of business applications. But if you want THIS painting, this one that you have commissioned to show the meadow in YOUR back yard, you can't rush the artist, or else the painting quality will be reduced. Depending on how much rush you add, the quality can be subtly bad but close enough, or horrifically bad as if, say, this pretentious commenter were painting it.

Let the artists (programmers) take the time they need to produce the artifact. Yes, the artists can sometimes get stuck in cycles of tweaks (goldplating) and need to be told this artifact is done, ship it, but it always seems like we lean too far to the other side: feature factories, churn churn churn, crunch crunch crunch.

Let the artists paint / program in peace!
A social media with focus on moderating toxicity and hatespeech, meanwhile bringing some interactive content on the table other than just the mindless scrolling.

We're trying to build a mix of insta + twitter + Reddit, without the drawbacks of each. All these big apps have issues, Insta with its data mining, Twitter with its blatant hate speech and reddit which is very limited in terms of features.

Fingers crossed, its a bit of a stretch and tbh even I'm not sure I can pull this off but current social media has a lot of room to grow imo.
> This resulted in a large surge of connection activity that overwhelmed the networking devices between the internal network and the main AWS network, resulting in delays for communication between these networks. These delays increased latency and errors for services communicating between these networks, resulting in even more connection attempts and retries. This led to persistent congestion and performance issues on the devices connecting the two networks.

I remember my first experience realizing the client retry logic we had implemented was making our lives way worse. Not sure if it's heartening or disheartening that this was part of the issue here.

Our mistake was resetting the exponential backoff delay whenever a client successfully connected and received a response. At the time a percentage but not all responses were degraded and extremely slow, and the request that checked the connection was not. So a client would time out, retry for a while, backing off exponentially, eventually successfully reconnect and then after a subsequent failure start aggressively trying again. System dynamics are hard.
As far as assisting with pure math problems, it is in its infancy.

Yet ML in general has had numerous practical successes that most people use daily (speech recognition, reverse image search, recommendation systems, etc.).

Yesterday, Yann LeCun wrote on his Facebook page: "I didn't know that Facebook, and now Meta, would be built around AI. If you extirpated deep learning out of Meta today, the company would literally crumble." [Source: https://www.facebook.com/yann.lecun/posts/10158029031237143?...]
In the US, they can and do create any quantum theory of your potential actions as legal justification for any preemptive action in their local department’s catalogue of actions, which you will never be privy to at the time. You are also not privy to the exact way in which you cease being an eliminable quantum threat, which may be nonexistent.

In some departments, officers have been fired for not eliminating a threat that the officer felt didn’t need to be “eliminated”.

So extrajudicial capital punishment for basically anything is legal in every state and territory in the US.

“Justified” only means that the action the officer chose was one of the equally weighted choices in the department’s current catalogue. It is not a tiered response, it is only an available response.
Got my family on a family account for Apple Music a while back, then at some point picked up a personal Spotify account to test the waters for their generated playlists, support for networked devices (chromecast/smart tv's), and API's (jkbx.fm). I can't migrate my family away from Apple Music and I don't want to give up Spotify's feature set, so I keep both.
>At 7:30 AM PST, an automated activity to scale capacity of one of the AWS services hosted in the main AWS network triggered an unexpected behavior from a large number of clients inside the internal network.

Just curious, is this scaling an AWS job or a client job? Looks like an AWS one from the context. I'm wondering if they are deploying additional data centers or something else?
And Cloudflare's lava lamps are an homage to SGI's 1996 Lavarand:

https://en.wikipedia.org/wiki/Lavarand
I think we are dealing with multiple meanings of word "communism" here.

Anarchists are opposed to communism in the commonly understood sense: a centralized state ruled by the communist party. Kropotkin was friendly with the Bolsheviks, who had not become communists in that sense yet. He supported the October Revolution, but he quickly became critical of Bolshevik rule afterwards. He believed it would not lead into communism in the sense the word was understood at that time: a society based on common ownership of the means of production without state or social classes.
> believe vaccines are hurting/killing people who take them

Yes, that's a false belief of this tribe that is directly contributing to their mortality

> and thus being in the vaxx-all-the-time camp could also literally kill people

No, because that belief does not conform with reality.

> Now, you may feel that's a ridiculous belief.

It is.

> It's not something that can be portably summed up in a neat box labelled "facts".

It can be. For reasonable definitions of a word 'fact'.
This page on Androidpolice.com crashes my mobile chrome browser. Won't be going to that site again.
Sure I would love a truth-telling candidate. But no existing party machine will accept such a candidate and even if elected no existing party will work with such a candidate.

And in the unlikely event you create a genuine third party, the current two parties will drop all their differences to destroy that party.
Yes, but PoS will not solve the problem of gas fees. Gas fees only come down when network capacity is higher than its demand.

Layer-2 systems (which allow some of the operations to happen off-chain) is how Ethereum developers are trying to scale the network capacity.
Jeez, you're slagging the entire value of VR because your specific setup is finicky?

Your complaints # 1-3 are a software issue that, while mildly annoying, will ultimately be resolved in an update. Creating a new guardian is literally a 15 second process.

Numbers 4-8 are because you choose to use a wireless headset from Oculus as a wired headset through Steam. Of course that's your choice, but the optimized workflow - that the vast majority of buyers use and is the primary product design - is to use on-headset apps without a PC or cable entirely.

It's also highly unfair to say "very very few things work well in VR" based on your experience. The vast majority of consumers don't care about Facebook IDs, or PCVR, or Steam libraries, or future compatibility concerns, or the other reasons you probably choose the setup you do.

If you want to judge the current state of VR for the mass market, go to the on-headset Quest store and try Walking Dead, Resident Evil 4, Walkabout Mini Golf, Contractors, Eleven Table Tennis, I Expect You to Die, Thrill of the Fight, In Death: Unchained, Fisherman's Tale, RealVR Fishing, Golf+, Moss, Tetris Effect, Pistol Whip, Red Matter, Shadow Point, or any of the other highly rated games that work out of the box.
> edit: if you consider buying, i'd definitely recommend getting a used one

Where's a good place to look for one?
It's a new language named Vale (https://vale.dev/). The TL;DR from a Rust perspective might be "A Rust that embraces shared mutability by default, automatically borrows things, and then adds an opt-in region borrow checker."

The core insight is that Rust's memory safety and speed mostly don't really come from the borrow checker, the borrow checker just showed us the way. We can combine the resulting patterns in different ways now.
I love LinkedIn because it helps me stay in touch with people who I went to school with and old co-workers as I deleted my Facebook account years ago. If I didn't have LinkedIn, it would have been much harder to stay in touch with those people.

I do think that LinkedIn has a lot of low quality content so I entirely avoid the feed and use it more so as a rolodex and that alone makes it worth it for me.
Completely reckless. Teams is terrible on Windows and Android. I'm not surprised. I only use it because my company has consumed the Kool aid. Otherwise I would never touch it. Slack forever!
TIOBE ranks Delphi/Object Pascal above Go and Rust.

I don't quite get this odd behavior of so quickly labeling a language as "dead" and devoid of any evidence to back up the claim. In the case of Pascal and Ada, various commercial interests want them to be "dead", because both represent a threat to their financial interests.

Pascal became Object Pascal, which is very much around in the form of Delphi/Embarcadero, Free Pascal/Lazarus, Oxygene/Rem Objects, PascalABC, etc...

Ada for sure is not going anywhere for many years to come because of its use in the military and aerospace industries.
The smallest US state has a larger economy than some countries. Fixing it doesn't require dissolution of shared citizenship, what we need to do is stop doing so many things at the federal level.

Why do we need a huge federal military in peacetime when we have the state national guard? Why do we need federal welfare programs instead of state welfare programs? It's not an argument against having a military or having welfare programs, it's a question of where to do it. And the US federal government is the wrong place, because it's too big.

"Laboratories of democracy" are a public good, but you can't have them if Uncle Sam is sucking up the public's money and giving it to Raytheon and drug companies and whoever instead of letting the states and the people have that money to implement a diverse set of independent programs and allowing citizens to decide which they want to live under.

Most of which was caused by 20th century screwing up of the original design. US Senators were originally elected by the state legislatures, to represent the states and temper federal power. The 16th amendment, federal taxation without apportionment, provides the perverse incentive for federal spending to increase without bound because you then have the large majority of states as net recipients of federal spending which is coming from a handful of states who are outnumbered. And guess which ones they are -- you wouldn't know it by asking their representatives because given the setup, they have no incentive not to feed from the same trough even while their residents are getting fleeced.

The good news is most of the taker states are still around breakeven and many of those (like Texas) would likely support fixing this if the likes of New York and Massachusetts would take notice that doing so is strongly in their own interest. (The biggest takers are the swing states, for reasons that should be obvious, but the red and blue states outnumber the purple states -- if they'd work together.)
Maybe, but I really doubt it. "Our developers are cheaper" is rarely a winning strategy.

JetBrains did - and still does - execute well. They expanded their IDE to many languages and caught the Ruby, Node, and Typescript waves. Borland did JBuilder, yes, but it wasn't category-winning. Maybe Delphi could have dominated with more investment and more imagination, but it seems to have risen and fallen with Win32.