skysight-inc/HackerNews huggingface dataset:
One common factor in your description of what you've done already is lots of big-picture thinking and big-picture change focus.

I'm an outlier-coach here in that I see this as an opportunity for more little-picture thinking, where that applies. In results I've seen, it's a very useful model worth testing.

So even if it sounds crazy, for the time being you'd start by:

- Lowering your time scales to minutes, hours. Kind of like the beginning of the film About a Boy, where the main character describes his life.

- Lowering your product/experience focus to individual product-/experience- level differentiations

- Lowering your stimulant focus level to common sensory inputs rather than big-picture stimulant undertakings

Result examples:

- What sounds good for lunch today? I had a ham sandwich from the store yesterday, boring af. What sounds really good today is some fresh lemonade and a monte cristo made with bakery bread. Followed by maybe a new type of chocolate I haven't tried yet.

- What sounds good pre- and post-nap today? To eat, to read, to watch?

- What would be a really funny thing to do with my career today, that only takes 10 minutes?

Big-picture result: The little picture factors eventually start to re-calibrate your big-picture values over time, making you more aware of your comfort levels, and eventually they make their way into your big-picture interests.

Once this propagation cycle is more complete, you get a more tightly-calibrated feel for what you want your future to look like in the big picture. So this is not ignoring the big picture at all.

But this is really really difficult for a lot of big-picture folks to start on, since our culture is currently mainly focused on / obsessed with career-change starting with big-picture first, and we are taught that the little picture is kind of naughty, and that we already know way too much about the little picture and what that's like.

Just another crazy idea though. Lots of methods to try from here & good luck with whatever path you take.
Use the --no-folding flag to prevent stow from linking directories.
If it's so hypothetical and highly unlikely, then we've nothing to concern ourselves with over the fact that Google will comply with attempts to rescue these hypothetical and highly unlikely endangered people. After all, if it basically never happens, Google will basically never grant the extrajudicial request.
The areas you mentioned (CLI, web services, low level systems programming) are not mutually exclusive. Doing a good job on one doesn't mean something else is affected.

CLI - The folks who worked on the most popular command line argument parser (https://docs.rs/clap/latest/clap/#example) made a positive contribution that didn't detract from any other use case.

Web Services - Similarly, the folks working on improving Rust for web services will also make it better for systems programming. In a blog post published today (https://blog.rust-lang.org/inside-rust/2022/07/27/keyword-ge...), they discuss keyword generics, a feature that will be equally helpful for `async` code (helpful for web services) and `const` functions evaluated at compile time (helpful for low level performance).

Low level programming - There is already some interoperability with C++ (http://cxx.rs) and ongoing research into automating this interoperability (https://github.com/google/autocxx, https://github.com/google/crubit).

Feels like there's enough effort in all areas.

I don't understand a request that says "drop everything else, focus on what I think is important". That's not how open source efforts work. People work on what they think is most impactful, what they enjoy working on. As long as they're not hurting any other use case, why stop them?
> isn’t a shortage of many items that have had large price increases like oreos

The wheat, the trucks, the oil and the labour that make every Oreo have increased in price. (We have amply-documented wheat, energy and logistics shortages worldwide.)

Also, nobody needs Oreos. The concept of “price gouging” is economically illiterate, but the nonsensicality squares when applied to literal candy.
Or maybe you just haven’t noticed missing incoming emails?
https://ozones.com/ is a good example that is still up!
Wikipedia's notability guideline does not pass judgement on the importance of Oscars or "CLIOs," both of which are notable and have their own pages.

Wikipedia's guideline for the notability of voice actors is:[1]

> 1. Has had significant roles in multiple notable films, television shows, stage performances, or other productions; or

> 2. Has made unique, prolific or innovative contributions to a field of entertainment.

This can be difficult to define. I'd suggest you instead follow the guideline of notability for people generally, which is:[2]

> A person is presumed to be notable if they have received significant coverage in reliable secondary sources that are independent of the subject.

I'm always sorry to hear about someone that has gotten frustrated editing Wikipedia. Even though I'd discourage it as a conflict of interest, editors have successfully created articles for friends by simply citing reliable secondary sources that cover them. I'd suggest you give it another try if such sources exist and reach out in the Teahouse[3] if you need help.

[1] https://en.wikipedia.org/wiki/Wikipedia:Notability_(people)#...

[2] https://en.wikipedia.org/wiki/Wikipedia:Notability_(people)

[3] https://en.wikipedia.org/wiki/Wikipedia:Teahouse
>Volunteer editors are spread thinly over millions of articles

I would like to point out that this is, effectively, a very clever way of saying that Wikipedia is controlled by a tiny group of people whose goals for Wikipedia do not match the expectations of the general public.
You could say the market was pricing in expectations of worse interest rates (1%)
That's sad. I would love to tinker with UI programming on Linux, but it seems like to get anything decent you will have to use QT, which brings C++ as a requirement.
"Oh no, it looks like that dog is being abused, we need to get Police and Animal Services to arrest and charge the owner and take the animal to a shelter [where it can be euthanized]" is what would likely happen in a municipality where guard dogs are put down when they bite thieves on private property with all of the mitigating factors for the dog (the dog was chained up, and could not escape, and it was in the middle of the night) and all of the aggravating factors for the thief (the area was well-secured, signed and alarmed, they could not have entered by mistake, and it was in the middle of the night).
Back in my days, systems programming evolved writing compilers, linkers, os drivers and kernels.

Given that the whole Go toolchain is bootstraped, it fulfills that role quite alright.

Maybe we need drivers and such to strenght the argument, well given the role of gVisor and Android GPU debugger, that seems a case for systems programming.

Maybe still not good enough, then I refer to the F-Secure TamaGo unkernel being shipped as firmware for the USB Armory security keys, or the TinyGo runtime which even ARM refers to on their IoT page.
> I have never understood what the central point of the Gaia hypothesis is.

Daisyworld is a very simple thought example, but also a computer simulation, of emergent planetary homeostasis: https://en.wikipedia.org/wiki/Daisyworld

Organisms modify their immediate microenvironment to their benefit. Lovelock points out that these modification mechanisms can regulate the planet-scale macroenvironment, as well.
Student loan forgiveness is a regressive tax.
Yes definitely he made waves and did interviews when it came out in 2019 and was very interested in how Artificial Intelligence could end up solving so many of the worlds problems -- forget the Anthropocene already here comes the Novacene and it's going to be amazing!
I've been on logseq for a while now and while I do genuinely recommend it, it is not without its issues. On recent versions I've faced issues where the page I'm typing on gets completely deleted. I end up having to go into Dropbox's web interface to restore that page. I'm fairly certain this issue is due to Dropbox and Logseq interacting with each other in a weird way, but regardless it has brought me a lot of headaches. Looking forward to them finally releasing their own syncing solution.

Other than that, the main issue I struggle with in these PKM/Zettelkasten style note taking apps is discoverability. I write down a lot of notes, but it is hard for me to find my way back to them. The benefit of hierarchy-based notetaking systems, where things get placed in folders and subfolders, is that at least I can get a big picture of my database at a glance. I've yet to find a nice way of doing this in logseq and its cousins.
Also, the difficulty of bringing a gun back into the US if you take it out of the US.
A subpoena is based on merely somebody's claim that there's reasonable suspicion of a crime. All this policy by Google does is shift the set of people who are making the decision of what "reasonable suspicion" looks like; one's reaction to that depends on one's relative threat models of judges (and time delay of interacting with judges) vs. Google employees.

FWIW, anyone still doing business with Google probably has a relatively high trust of Google, so that comparison is probably closer to equivalent than many might imagine for Google's users.
With the exception of a few of the mass murderers of the 01970s, the people who have caused our currency to be so volatile over the last 50 years have all retired to enjoy their wealth. Some of them died at a ripe old age. The people currently running the government definitely did learn a lesson from that: they learned that they, too, will retire to enjoy their wealth, even if they impoverish the country in the process.

However, a number of presidents and finance ministers have had to resign in disgrace when their policies (or those of their predecessors) provoked immediate crises. Printing money is a common way to postpone an immediate crisis.
Wikipedia's notability requirements are enforced very haphazardly. Broadly, editors and admins can be split into two camps: inclusionists who want to add everything and exclusionists who want to delete everything. The life of your new article entirely depends on who happens to stumble upon it.

I've had success appealing notability deletions in the past, but it was a pain in the ass, especially after I just spent hours researching, sourcing, writing, referencing, and proofing the article. I never made a new article again after that.

Sadly, some of the admins there are power tripping idiots who will also use random loopholes to forbid edits that don't reflect their own ideologies, often in direct contrast to Wikipedia's own guidelines.

Like any bureaucracy, it has become a cabal of aristocrats who are in it for the power and control. Regular lowly editors generally don't have much recourse. It made me gave up on editing Wikipedia. Became an editor in 2004 and the climate has changed dramatically since then, from "newbies welcome, please edit" to "this is my private library, don't touch anything!"
Probably they're more interested in selling you new flash.
If you like wordpress, I had an excellent experience with wpengine. They handle large chunks of security (nontrivial for the junk show that is WP and plugins), backups, came with a staging environment (maybe not all accounts? But ours did), etc. It was as good a time as you can have with wordpress, imo.

Oh, and I got good support who quickly figured out a db issue that a custom plugin was having and got us a solution. Turned around in 1.5 business days. And we weren't on a super expensive plan.
I think option 1 is the most elegant, but I also realize that as a user of Less and Sass it is the most natural choice for me. The `@nest` having to appear when the ampersand exists after any other character in the line is an okay inconsistency for me, since I rarely come across that form and when I do it it's in short bursts with tightly coupled selectors. You can also think of it as a warning sign for yourself that you have an ampersand in a not-so-conventional spot in the line. If option 2 happens I wouldn't be disappointed, either. The brackets example, however, just looks wrong to me.
As mentioned elsewhere, solves none of my list. This mostly moves stuff around and hides certain UI elements.
I think the point is, the specific wording "we don't do that here" is patronizing and othering. If you want to tell someone "don't say that," just say it. "Don't say that, I prefer to be called 'homosexual'" is even better (using the "gay" example).

Also, the idea of "reconsidering the finer points of the rules" is really interesting - it suggests that the comfort of the first 5 matters more than the comfort of everyone else. What if the first 5 people were hyper-religious conservatives who hired 10 progressives and want to keep hiring progressives? Should it still only be the finer points of the rules that get discussed? Or should it be understood that their culture of prayers every day doesn't scale up, and that a lot of things need to be re-worked? This can also be true of hyper-progressive people. A culture of offense-taking at little things, language policing, and social justice book clubs is as non-inclusive as a culture of daily prayers.

"We don't do that here" is exclusionary language, and so are the other two comments you suggested. Both use "we" to fabricate consensus (has the company really decided as a group that this particular speech pattern is banned?) and shame the other party as an outsider. That is not the right way to create respect.
How (over)subscribed are their servers is an information I'd like to know
It's gotta be embedded stuff. The Space Shuttle GPC was constantly reprogrammed, including on the pad. They've sent patches to the Voyager spacecraft as recently as a few years ago [1]. 45 years, not too bad!

1 - https://www.livescience.com/nasa-makes-contact-voyager-2-lon...
Having recently worked to implement a large, well-known authorization provider's services into a large ecommerce app let me share some tips from the developers perspective:

1.) It's likely your surface area and integration-points are better designed for DX but the provider I've worked with had a large surface area, many integration patterns to choose from (likely to accommodate the plethora of customer needs over time) and because of this their documentation was often inadequate or misleading. Then you rely on support and I'll just say- please put priority on quality, experienced dev-support especially during early integration for paying customers. Also example project repos go a LONG way. I'm sure this is all stuff you're on top of but that early integration phase (especially for larger orgs) is sometimes a high-visibility, high-risk phase for the internal teams where setting them up for success and exiting that phase with a good impression would likely pay-off for the resources you invest on your side (especially if those devs, PMS, EMs, etc. then evangelize your service later at other orgs- you can imagine the inverse scenario, lol).

2.) A lot of the time, especially in larger orgs, your biggest skeptics will be deeply experienced in rolling their own auth even at decent scale. Having a healthy, substantive youtube (talks) or blog presence where you deep dive on best practices would go a long way here to alleviate their uncertainty.

3.) Supporting staging/local dev environments with as little additional dev work would be awesome. You may already accomplish this, didn't go deep into the docs.

4.) Plug-n-play logging to popular services like Datadog. Again, if orgs are coming from internal solutions to yours they'll already expect and have comprehensive logs around various auth events so making this easy would be a win.

Hope this helps! Warrant looks awesome and I'll definitely keep an eye on it for future projects!
No. They were fined for doing things like recommending off-label use for their drugs, and they provided no data to support that off-label use. That isn't falsifying data, but that isn't acting trustworthy either.
>Critics accuse the Russian government of using gas as a political weapon.

Seriously? The US and EU are trying to financially destroy the Russian economy. But have the brass neck to call foul, when Russia retaliates in similar vein.
Putting aside the fact the HN title is completely different from the article title, I don't even see where $280B (in the HN title) comes from... There's a $250B mentioned in the article body, not a $280B.
I recognized the name immediately.
IMNSHO query planning is pretty hard. I recently found exponential behavior in SELECT query processing that depends on the depth of subselects. This happened with pretty seasoned database system, let me say.

To have good query optimization, you need to implement, at the very least, some form of dynamic programming, otherwise you will not be able to optimize queries that have more than half a dozen tables in selects. Then you have to implement selection of the best plan or approximation to it, which would make you implement beam search through space of all solutions you generated, and that's simplest case. For guaranteed optimization, you need to implement or utilize pseudoboolean optimization engine.

I am a database engine developer right now. ;)
I'm glad you have had a good experience with them.

For me, in 2006, my email services was the most important thing I had. I ran a family email server that was used by a small group of us. Any outages were hard to accept. We had a lot.

It may have been the host I got put onto, the ip address of the host may have had a shared-account-bad-actor causing an RBL, or any number of reasons.

Just goes to show you that one experience is not all. Thanks!
For those on the "it's-fine-to-print-money-at-will" bandwagon, please meditate on at least this part:

> “everything starts with a large fiscal imbalance, which becomes a monetary imbalance due to printing [money] to finance the deficit.”

Says the chief economist of the Agricultural Foundation for the Development of Argentina.

A.k.a. someone in one of the best places in the world today to really know this stuff.
What stocks? Intel & AMD dont seem to have moved much. Asking for a friend.
As much as I hate it one company I work with has not just a functional info@ adress, but it is the main adress they interact with everyone.

Just works.
> It's also difficult (impossible) to curb demand for housing if housing is far and away the best investment you can possibly make, both in the short, medium, and long-term.

With the population numbers in decline in the west (especially Europe), will there be enough demand in the medium and long-term for housing?
The other great feature were 'nodeshells' (that is, links to pages that did not yet exist). These could act as writing prompts, or just as a way to 'comment' on other nodes (pages).

Weirdly, one of the ones I liked (by adding it to my homepage) was 'AT fields cannot be penetrated spiritually fallacy' was around 20 years ago. Just this year I finally watched Neon Genesis Evangelion, and finally understood what it meant :)
The old UWP "sandboxed" app lifecycle model had permission/capability settings for background tasks and was good for users. Developers of course hated programming against it.
Dupe: https://news.ycombinator.com/item?id=32247493
It still exists, but it is rarely taught. When it is time for you to learn it, you will learn The Way of the Capital Letter, and anyone paying even the smallest amount of Attention to your words will Hear them in your speech.
Finland, Denmark, Iceland are the Happiest Countries in the World 2022
Point me to a specific fine for data falsification. Unlike you, I have made no false claims here.
My first job was at a tiny ISP during the dialup->DSL/cable transition, and I got put in charge of setting up the very first RAID array they had, which was a RAID-5 hardware array (SCSI, natch). It was a 4 drive array, we moved most of our fileserving over to it, next project was to set up a hot standby for the server.

Of course, that was when DSL started to become a lot more common, and business started to suffer. Money got a little tighter, and after a month or two we lost a hard drive in the array - no problem, grabbed the spare, swapped the drive. Then I asked for a replacement spare - "sorry no, can't afford a spare drive, let's wait a few weeks"

Two weeks later, another drive fails - and now we have no spare. I go to the CEO and ask for his amex to overnight a replacement drive, and he says, "Ehhh, no", and I said, "well, you know, if we lose another drive, we'll lose the whole array", and he said, "Yeah, but what are the odds we lose another drive in the next few months?"

I left that job two months later, constant nightmares in the meantime. A month and a half after that I heard from a former colleague that indeed, another drive had failed, and turned into a four day downtime for the entire ISP.
Talk to anybody in advertising, marketing, radio and television ... believe me they know what a CLIO is (and get paid accordingly). There are so many industry specialties now, that to be a dominant player in one may render you virtually unknown in all others.
I'm not really disagreeing, but isn't comparing Ebola and Marburg to SARSes a bit apples-to-bananas?

Ebola and Marburg for decades were quite rare. Incredibly deadly, but an outbreak would affect a few tens of people, and invariably in remote locations. By the time the epidemiologists arrived, the outbreak was waning.

Clearly the Ebola outbreak in 2010s was much bigger, but that was the first such large outbreak.

Also, with outbreaks in the rainforest, and perhaps with poor sanitation, there are thousands of possible animal hosts, whereas hyper-urbanised China hives far less opportunity for wildlife contact.
mentat was archived by mozilla back in 2017, but there are a bunch of forks. Because github is dumb and has a terrible interface for exploring forks [0], I used the Active GitHub Forks tool [1] that helped to find:

qpdb/mentat [2] seems to be the largest (+131 commits) and most recently modified (May this year) fork of mozilla/mentat.

[0]: https://github.com/mozilla/mentat/network/members - Seriously, how am I supposed to use this? Hundreds of entries, but no counts for stars, contributors, or commits, no details about recent commits. Just click every one?

[1]: https://techgaun.github.io/active-forks/index.html

[2]: https://github.com/qpdb/mentat
Two different objections.

First, while the most written-about musicians are also generally the most popular, there isn't a strict correlation.

Second, there is a vast difference between a decision-process of "if the sources provided show that this person is popular, they are notable" and "if three of the four Wikipedia editors surveyed like this person's music, they are notable".
Siteground is a decent option for cheap-ish WordPress hosting. Even GoDaddy is actually good these days.
Innovation Through Exaptation (2010)
Maybe I was hoping to find someone who has already made such a transition.
There was a funny incident in 2011 when a Fed president claimed inflation was low because drops in the latter category canceled increases in the former, prompting heckles of "I can't eat an iPad":

https://news.yahoo.com/news/blogs/lookout/fed-official-heckl...