skysight-inc/HackerNews huggingface dataset:
Okay, thanks for the info. How does job stability compare to having a full-time job? Do you get benefits?
At least of the 3 examples on that webpage it seems like you made remakes of existing simple games (tetris, sokoban, pong) - did you try making new designs of your own and if not, why not?
I think it's a case of a million people trying, and 99% being reverted. Which sounds great, until you realise that it means ten thousand bits of nonsense aren't spotted. Case in point:

https://www.dailydot.com/unclick/amelia-bedelia-wikipedia-ho...
I wonder, aren't there other vendors with more basic equipment? maybe chinese?
I agree.

I can understand the annoyance for there being so many verbs, but at the very least, there must be two: One that is guaranteed to be idempotent, and one that isn't.

Someone I know was trying to make a message board that was compatible with every browser. EVERY browser. Including Mosaic and Netscape 1.0. Which meant that everything was done using GET requests, including posting messages.

He changed his tune when some spidering engine found his site and issued tons of GET requests that ended up flooding the board with comments and posts that looked like web search queries.
The US doesn’t know where its critical minerals are. AI could help find them
Registration for the DARPA AI for Critical Mineral Competition is open now thru Sept. 23.
Summarizing up-front is hard because it works the opposite of how many peoples’ brain works; if you don’t have a summary drafted, one good way is to run through everything verbally and then summarize at the end. This also plays into the natural narrative-creating tendencies.

So it’s good to recognize that this is a cognitive habit and it might require practicing a different approach, or preparation.

Another military term I’ve heard for written comms is “Bottom Line Up Front” (BLUF) which translates to a proactive TLDR. Similarly, this is a very useful tool for helping people consume your written comms; it allows readers to figure out if the content is something they need to deeply engage with or skim, rather than forcing them to skim the whole thing to figure that out for themselves.

The common theme here is that there is lots of value in providing a concise summary, so that recipients have to do the minimum amount of work to extract the first level of detail of information. This allows the first level of detail to travel further in the org and means the org is going to be better equipped to make good decisions.
> She spent most of the time trying to dictate things she'd already written over the phone

Falling back to ingrained habits is quite a normal response to stress. It also is part of why after an emergency landing aircraft passengers may pick up their luggage before getting out of the plane.

I think that also could explain the martini drinking in the limo. That might be the ‘program’ fashion journalists always run when in long limo rides.

As to the entire article: It’s not brilliant writing, but she mentions what she did, show some compassion with the victims, realizes that he drinking wasn’t very appropriate, and concludes that fashion may never be the same.

I don’t see that as being reason to vilify her.

That may even have been the brief she got from her editor.
Right, that's the big question. In a perfect world, people won't sell if they don't have to. And so we'll have to see how everything else plays out.

With 2.5% interest rates, people have maxed out what they can afford for their mortgage and bought at the peak. Any disruption in peoples lives going forward is going to bring a lot of pain.

I'm thinking about all the techies who get most of their TC from RSUs. When the recession starts hitting employment and the stock market, they are going to lose that income they accounted for when the mass home buying spree of the last two years happened.
> It's impossible to create a production-like test environment for a product like Twitter.

What makes you think that?

I mean, I know it costs money and needs people who understand how the product works and how customers behave - but why on earth would it be impossible?
The real 10x engineer right here!
Well obviously they have to pretend it's for something else. If they faced it head on with the actual law protecting the monarchy, you could argue directly against it.
I mean you are moving the goal posts into the parking lot right now. The initial question was whether or not there was value in taking incremental steps to combat racism and you're saying we shouldn't build statues to the keyboard warriors of Twitter. Nobody ever suggested that. And while we can absolutely evaluate historical figures on their cultural context that doesn't mean we should lionize them on public property. Forrest was the Confederate general who founded the KKK and was honored with a ridiculous statue on public property in Nashville.
If you developed your services right. You’d have a notification service that does SMS,email,smokesignals…

It’s up to principal/staff engineers to make sure that the components of the system stay lean to its purpose. They should be able to say “oh, we need to send an email when this happens? Here’s an email service we can use” that doesn’t introduce feature creep into AuthTokenValidator.

I get what you’re saying but these little shortcuts (adding email sending in AuthTokenValidator) cause enormous tech debt later on when you scale.
> The only one that actually sounds useful to me is HELP.

And we already have OPTIONS for that.
https://www.forbes.com/sites/augustinefou/2021/06/07/the-cur...
I got the attention of an exec at a meeting a few years ago when I asked about opportunities intra-office and wanted to apply to some positions at headquarters (I worked from a satellite office). This was pre-COVID and aside from the public conversation with the exec in the meeting with 200+ people, I’d only hear from him via the chain of command.

I got encouraged to apply to a few jobs at the main office and when I talked to managers there, everyone acted strange and uncomfortable about it and it was obvious nobody wanted someone working “remote” on their team. Eventually they said “oh we’re not hiring for that position this year”. Drastic way to keep remote people out.

But the exec never heard from me or solicited feedback so he wouldn’t have ever known this. So his initiative was dead in the water.

This was when I was more junior. Today I’d just have shot him an email giving him a status report on my experience but in my experience a lot of “ground level” folks are terrified of interacting with execs 5 levels above them in the org.

A follow up meeting with me would have definitely revealed what was going on and he could have taken some action.
It's obviously a mix of both, and it's up to us to make the system tilt more towards the former.
Link to the article: https://journals.plos.org/plospathogens/article?id=10.1371/j...
Temperature impacts on hate speech online: evidence from 4B tweets
I'm not so sure. The problem is that the world is moving, including hardware, software, interfaces but also people and process. Languages have to optimize against a moving target. So naturally it's a good idea to optimize for something moving and not something static.

This is what makes Scala good. The language itself is not very complex actually, but it enables complex and powerful libraries.
non sequitur?
It’s not “innovative” to double-down on mistakes.
I meant "flatter" as in "linearly increasing" competence. Once one knows the basics, it's easy to write "correct" programs in Rust that will not exhibit unexpected behavior. Of course, learning more of the language, one will write more expressive and performant constructs. The progression is made easier by the language and lib having relatively few pitfalls. Also, much care has been given to the developer's cognitive load through proper tooling (cargo) and informative error messages from the compiler.

"Fighting the borrow checker" has become a Rust meme but it's actually a good part of the Rust experience to have a "conversation" with the compiler. One is forced to reflect upon the implications of the app or lib's model, often leading to a better design or at least an understanding of the limits of the code. This is possibly similar to what LISP people describe when talking about their REPL-based workflow.
Saw a company fail because all developers were expected to master k8/helm etc. A couple of us got the hang of it well enough to get by. But almost everyone failed too.

Even those of that had it working, it was a huge time sink.
drop out and be a criminal. it's really the most fulfilling option
JDK 19 and JDK 20: What We Know So Far
I find that egos can be really fragile when people are just starting to learn things. Pointing out the mistakes so quickly can seem like a great help (and it is!) but some people react like they're staring at the sun.

Instead, I find it better (except for how long it takes) to walk them through finding the problem as if it's really hard and just nudging them to the steps they'd need to take to find it themselves. They learn even more, and it doesn't immediately show the difference in skill between you and them.

At the very beginning, even a small difference in skill can seem like a lot to the lower-skilled person.
Autoplay is as at least as old as Windows 3.1. A file called "autoexec.bat" would be executed on mounting, IIRC (not a Windows-person myself).
You haven't lived until you installed an operating system from 38 floppy disks.

Slackware and OS/2 for example

My lord those were fun days. Especially fun when you got to OS/2 Disk 21 and it died, or Slackware Xwindows Floppy 4 and you started hearing that disk drive kurchunking and you just knew you were dead in the water.
It translates as "The The Tar Tar Pits".
"It isn't rocket science!!"

I remember my first management job. I managed a helpdesk. I had to try and explain to the owners that I needed time to meet with employees, and a very small budget (few $100 a month) to reward them on the most basic level for meeting or exceeding goals (tickets, SLAs).

The owners looked at me like I was from outer space.
> The wisdom of 1990s was that if you have one copy of data on your disk, you may as well have zero copies.

Still true.
> and many bikers aren't actually stopping at traffic lights.

It is not because of this, but because Amsterdam created entirely separate bicycle routes that have grease separated intersections with main roads for cars. So they simply don't have as many traffic lights for bikes because of that. Also, even if the are traffic lights they're much smarter at adapting to traffic and have much faster phases than in America.

> avoid any intersections with other users and flow interruptions: people should not cross streets, they should pass over them on bridges.

No, the cars should be the ones going over bridges or through tunnels. Doing it the other way around is prioritizing cars and dehumanizing pedestrians and cyclists.
Nothing citeable, just anecdata and murmurs from being active in that scene for a long time

I did find https://linustechtips.com/topic/1238719-low-latency-cpu-for-...

edit - Sound on Sound with a bit more detail https://www.soundonsound.com/sound-advice/core-wars-amd-inte...
It kind of does already: https://youtu.be/vmbzKsqKQoI#t=30s
In other words you're inventing some silly criteria that I'd guess you'd pass that others wouldn't. What I would say to that is that if you dismiss someone else's experience because they can't do some task you think they should be able to do rather than understanding that their experience probably brings something else to the team then that's your failing, not theirs.

For a little annecdata - I've been a dev for 25 years, with a senior level (and above) title for about 80% of that, and I reckon I'd take at least a couple of months to get to a point where I was happy with golang. I guess that makes me a junior in your opinion. However, instead of being able to get up to speed with a language quickly I bring a fantastic level of respect for users, a talent for technical writing, a belief that documentation is actually important, a sense of fun and joy in making high quality software, and a deep understanding of browser-based software. If I was looking for a new team member I'd seek out someone a bit like myself rather than someone who can learn a new language faster.
Mhm. Agreed. But the specific implementation, and especially the term "JIT" in the CSS space, is from Tailwind, right?
There hasn't been a court case yet. Not even a judicial hearing. The article we're commenting on is about how there's a very good chance that courts will disagree. This SCOTUS has repeatedly shown a willingness to restrict executive overreach in the Biden administration.
The Delaware chancellor, Kathaleen McCormick, has several cases involving Musk's bad behavior on her docket, and is aware of how he plays it very fast-and-loose with rules and laws. She might not let him get away with this one, particularly because it would cut at the main value proposition of the Delaware chancery court (adjudicating acquisitions) if he does. His best chance is to give her enough cover to plausibly find a material adverse effect, but that is a VERY high bar, and I doubt they are anywhere near that level.
Pre-built Framework laptops only ship with Windows. Last year's model has Windows 10. This year's model has Windows 11. The DIY model ships with either Windows 11 or "None (bring your own).
Nice double-entendre. Kudos.
Eh—I don't know. Code a test or two and something basic with just the lang? Sure.

The whole stack? Takes about a month to get productive and about three months to really internalize. Think interned strings in Python vs symbol exhaustion in Ruby. Or serializers in Django Rest Framework working as both input validators and output generators compared to stock Rails views.

Super similar languages with lots of similar frameworks and libraries, but they have these edge cases that still crop up.
Or the Lone Wolf series:

https://en.wikipedia.org/wiki/Lone_Wolf_(gamebooks)
how serious it is? how prevalent? how persistent? how big of a public health problem it is and/or going to be? can it be treated? how well?

was this known before? what other sources cause it?
I can be dismissive of webdevs myself but this comment is too bitter for my taste. It sounds like you learned the salary of your greenhorn webdev nephew recently.

The author did hit on the truth, no matter how he arrived there. Descriptive names are prone to collision, misdirection, and are much too long unless you use acronyms (in which case you may as well come up with a whimsical, pronounceable, unique name and just backronym it). This isn't a new idea. Lots of greybeards know this and name stuff accordingly.
I think the main problem with the accuracy of Wikipedia comes into play when reading about events related to politics or similar controversial topics. I have seen plenty of wrong information on Wikipedia related to recent events which I knew for a fact that were wrong because those events happened in my city and the area in which I reside in.

The information related to the field of science is accurate but can't say the same for modern events or history.
the blog says: 10 lakh crore rupees per month not INR 10 cr

10 lakh crore rupees per month = INR 10,000,000,000,000

which at the current rate of ~INR 79 to $1 comes to

$126,582,278,481.00 per month

as in $4,219,409,282.00 (over $4 Billion) per day
> no ability for Twitter (or anyone at the company) to defend themselves or refute these statements.

In declining to appear, their CEO traded the ability to refute statements in real time alongside Mudge for the ability to release carefully crafted statements after the fact that will receive public scrutiny but do not require him to tell the truth in response to any questions from congress, the content of which are out of his control. Misleading public statements can get them in hot water with regulators, but lying to congress is a crime.

It's probably a smart move, and it's certainly not unfair to Twitter.
"Use OSS" is very close to if not the same as "Build".

To adopt an OSS approach for SSO, the startup still needs to dedicate resources to researching the OSS options, deploying the OSS, integrating it, and most importantly, operating it.

Once the startup gets into the weeds of integrating SSO functionality with customer's IdPs, in the limit, the cost of the effort will start to approach "Build".
They cite this link for the 70% number, but the link itself says 52.95%: https://icannwiki.org/nTLDStats:.wiki/Parked_Domains_Percent...
Adopting beliefs that conflict with your preexisting belief system is incredibly difficult. It’s arduous and confusing. It’s not as simple as looking at one piece of evidence and saying “oh I was wrong”. This is because beliefs form a web of knowledge, and they reinforce each other.

On the other hand, adopting evidence based beliefs is very very easy when those beliefs line up with your existing belief system.

If you’ve ever tried to, say, talk an anti vaxxer into taking a COVID vaccine this becomes very obvious.

The discussion notably is not straightforward. It’s not “here’s the report saying it reduces hospitalizations and deaths” “oh I can’t refute that okay”

It’s more like “here’s the report saying it reduces hospitalizations and deaths” “that report is lying because Fauci ordered it, here’s a headline i saw that there were tons of deaths in the Israeli vaccine trial, and here’s a link that describes the evil peoples intentions with the vaccine”

Instead of convincing them with evidence you’ve forked into 3 separate arguments (trust in validity of peer review + what happened in the Israeli trial + can you trust this article that claims fauci and bill gates are satanic cultists)

And that’s without diving into the ocean of human bias that allow us to reinforce our belief system with little effort.
I was part of a team that processed really large files (hundereds of GB) in an Akka cluster. At that time Akka seemed like a clever choice to us, since we were Scala enthusiats and Akka was the framework of the day, but it took us many weeks to master (more or less) Akka. We could have done the same in a more robust and manageable way with Spring Batch in a fraction of the time.

Akka had a really steep learning curve for doing relatively boring things. Technically it was quite interesting, a from a business perspective it was a desaster.
> 2) Elon is going to get away with it. And he really shouldn’t - he already waived his right to back out based on any of this. Just because you like someone shouldn’t make them above the law, and basically the takeaway here will be that like Trump he’s above the law because a large enough section of the public likes him.

There’s no getting away with it. This was one hundred percent his plan the whole time - throw Twitter into chaos internally. Now for what reasons remain to be seen, but his extensive use of Twitter was highly unusual as a high profile CEO basically rewriting the PR game (which the SEC tried to reign in). That experience gives him unique insight into how Twitter works and what power it holds - he may very well feel a government party is influencing the platform too much and he’d rather destroy Twitter than lose control of it.
I saw a solid video a couple days ago called "Why I hate Wikipedia (and you should too!)" https://youtu.be/-vmSFO1Zfo8

I'd never given Wikipedia much thought, but it raised some very interesting points to think about.

TLDR: Despite mediocre information, Wikipedia's ubiquity has supplanted the market for better sites dedicated to specific topics.
Covid was bigger than the fed.
What happens when the automaker updates the software in your car to charge you a monthly fee in order to use those same computerized components? This is already happening, most recently with Toyota putting its remote start feature behind a monthly subscription paywall[0]. Imagine buying a car that had all the features you want, only to get an email 6 months later that you now need to pay a subscription to continue using those very same features.

0: https://www.thedrive.com/news/43329/toyota-made-its-key-fob-...
> Well, golang is a tough language.

This _could_ be true for some, but it directly conflicts with the stated goals of the language. Most people (that I've spoken to) would consider Go to be a simpler language, with fewer features, than other comparable languages.
About 200m, which is considerable but nowhere near a record, the deepest being 290m deep IIRC. It also doesn't have to be steep. 200m down in 10km is just a 2% incline.
Yes Grafana Incident is available (fully featured) in the free tier of Grafana Cloud
Back in the 80's few machines had hard drives, and often only one floppy. So if you put your disk in the drive and fired up the machine then bang, you were infected.

Also, lots of machines with hard drives were configured to boot from floppy by default. Few floppies had working boot sectors, so most people never noticed. Until they put an infected disk into A:, turned on the computer and saw chaos ensue.
Different at different times of your life. I'm mid 40's. Have done some work for myself, largely career for other people culminating in c-suite roles.

Now using all that knowledge running on my own startup (and loving it...) which I'd tried to get up and running 10 years ago. The skills gained over the last 10 years absolutely invaluable for launching the startup with much greater success than version 1 :)
You are always working for someone—whether you have one big customer, a few medium-size ones, or many tiny ones.

More customers is in some ways more sustainable, because losing a single customer is less of an impact and you are more likely to have a well-oiled up-to-date process for getting new customers.

Perhaps a bigger differentiator is not employment vs. self-employment but whether you can do something you enjoy doing while getting compensated for it and living a balanced life—which is possible in either arrangement.
uhh...yeah, i thought i was clear on that?
Vaccinated people spread viruses, what do you mean ?
Work for yourself but you won’t get work life balance until you’ve built something stable. You’ll have much higher satisfaction but you also have much higher risks.

If you are risk adverse or just want something steady so you can enjoy a work life balance, go take a job, work your 9-5, don’t quiet quit but don’t go above and beyond.
it seems to me no one wants to admit that society and the economy are set up in a way that we need people at the bottom. when the lowest classes attain even the smallest increase in purchasing power, demand for goods and services soars and inflation soon follows. it’s pretty sobering. as to what’s to be done? i wish i knew.
I enjoyed Scala, but I enjoy F# much more. .NET Core is a healthy cross-plat ecosystem, many of the VSCode/F# tooling issues have been eliminated over the past few years (IntelliJ was really one of the core reasons I preferred Scala), plus Akka.NET has F# bindings. Come on in, the water's warm:

https://fsharp.org/learn/

https://getakka.net/
Firefox passes acid2.
Twitter Whistleblower Says There Was at Least One Chinese Spy Working at the Co
It’s going to be a wild ride going forward, so buckle up passengers…
As soon as StableDiffusion landed we dropped everything to build a GENIE!

Voice UI
AI Art
AR previews
Instant purchasing
On-demand production

Will AI make every shopper’s wish come true?
Yup, but see my original comment and the PWA page for why that isn't really satisfactory on mobile.
China's Chang’E-5 samples reveal high water content in lunar minerals
Nothing beats working for yourself. That said, if you have a family or dependent people, make sure you arrange some sort of financial security before doing anything adventurous
With billions upon billions spent on Big Science, asking the government to spend just 1 billion on an AI training run with guaranteed spectacular results doesn't sound too outlandish.

Why should we pay taxes, if the government won't even train AI for us, given such opportunity?