skysight-inc/HackerNews huggingface dataset:
Yeah, it is. For reference, I have a biological sister in VA, and a sister-in-law out here, both of whom can't drive. Both live a similar driving distance from the main city (DC vs Seattle).

My SIL can bus basically anywhere with enough patience. She goes to board game nights, college (pre-covid), etc.

My sister in VA can't go anywhere without getting a ride from my mom. She's actually only a few miles away from the one DC subway line that comes out in her direction, but despite having a disability that qualifies her for the public transport door-to-door vans, she's ever-so-slightly out of their service radius. Even if she could use that, that line is a commuter line that goes straight into DC, it's useless for anything else, and they heavily cut service due to covid + derailment incidents (inspectors were falsifying inspection reports) + car fires. She could use Uber or Lyft, but that's expensive and she's read about people getting assaulted and is scared to use it (I know it's rare, I've tried...)

So, yeah. I complain about Seattle PT too don't get me wrong, but thinking about other states does put it into perspective (even if thinking about Europe puts it into a different perspective...)
But you do get stronger by lifting weights. The fact that a comparison can be uttered doesn't automatically mean it's also applicable.
The way that public transit scales to meet higher demand is different than roads. Whereas roads require more lanes, public transit such as trains can scale by either adding more train cars to existing trains or adding more frequent service. More frequent service, in addition to improving throughput, also helps everyone else using the system by making it more convenient. And, if it "induces" people to move from roads to trains, that also reduces congestion on the roads. So induced demand for rail lines is a good thing.

If induced demand is high enough even that, too, may not be enough - but then building a new rail line is at least no harder than adding a new highway lane (in most cases), and can support substantially more throughput with equal or lower travel times.
OpenSea is a great example of break the law until you get caught and then pay a small fine. They just haven't reached the "get caught" part yet. Putting utter ridiculousness of NFTs aside, a lot of the art on the site is straight up stolen and artist have very little recourse in what they can do. Here is a good Twitter thread from Loish summarizing the state of affairs for artist https://nitter.net/loishh/status/1470340143970230277
It's not just in the US. Denmark had a snowstorm about a month ago and it was chaos because people take stupid risks. Large numbers of people drive around on summer tires as well as the majority of both trucks and busses.

If people only put themselves at risk, fine. The issue is when trucks and people who felt compelled to drive on summer tires, in a snowstorm, during covid, block the roads and prevent the remaining population from getting home safely.
Good luck getting any sort of security certification without reviews. This works fine for small companies, but once you start getting customers at a certain scale it will be a dealbreaker. Run without reviews as long as you can, it feels great!
Selling shovels during a gold rush is always a great business. Coinbase is worth $50B+, so I don't see why this is too surprising.
do you want to deal with SEC after your ICO? im pretty sure they dont
mentor: a trusted counselor or guide [1]

coach: one who instructs or trains [2]

When there's some doubt about meaning, I find it useful to wonder how other people might interpret the words I say, and I have found that a dictionary is a good way for communities and societies to agree on what those words mean. I do not say this to be snarky. I used to be surprised to learn that some words I thought I knew had a different, if related, meaning. Now, if say I was presented with an article that I wanted to comment on its use of words, I will look up those words first to see if perhaps I am the one that is out of touch with my peers.

I am a mentor, a mentee, and have had life coaches and sports coaches. While I have paid life coaches, i.e I am setting goals, that's very different than a coach within a corporation: perhaps the distinction for coach is "Who is paying the coach?" A mentor, however, is very much a counselor / guide, even though they are paid by the company. Another distinction is that coaches are, to some extent, accountable. They are paid to achieve a result. Mentors just don't have the responsibility.

[1] https://www.merriam-webster.com/dictionary/mentor

[2] https://www.merriam-webster.com/dictionary/coach
that's why you should use guesstimate! https://www.getguesstimate.com/
Custom notifications triggered via time and space
Vybit (https://www.vybit.net), an app which sends push notifications with personalized sounds, just released a new version where you can send notifications at set times (like a cron job) or by entering/exiting specified geofenced areas.
I can see this being helpful to people who are unfamiliar with a language's syntax/language learners.

For someone who already understands the syntax of a language (or at least the syntax of a related language), there's little to be gained from seeing what the code is doing. Take part of the Python example from the linked page: "The code defines a function called isPerfectSquare. This function takes an input of x, and calculates the square root of x. The function then returns whether or not x * x is equal to x.". This guides me through the code, line-by-line.

A more valuable description is "The function returns true if the input is the square of an integer". In other words, the more useful question is why the code exists. Good comments, explanations of code, function/variable names etc... focus on the overall objective of the code. For example:
- What is the abstraction that the code is trying to capture?
- What makes the problem that the algorithm is solving difficult/non-obvious?
- What are the pre-conditions that a given segment of code assumes?
- What post-conditions does the segment of code ensure?
These days you need to have your kernel driver signed by Microsoft or edit your boot config options to put the machine in an insecure state mostly useful for testing. To get it signed you need to pass a basic test suite which MS provides (and can be gamed).
https://docs.microsoft.com/en-us/windows-hardware/drivers/in...
Show HN: FancyWM – Dynamic Tiling WM for Windows, Inspired by I3wm, FancyZones
Just want to say, I'm so sorry you're going through this, and best of luck to you and your daughter. You're a great parent for actually taking the time and effort (and money) to help her to the best of your ability.
The V Programming Language Simple, fast, safe, compiled
Why can't this be done with existing public key cryptography?
This is a USA only problem. In the rest of the world, a gas (petrol) pump will happily dispense into a bathtub if you want it to...
I mean, I don't see how that's really a fair response to saying what people care about is traffic. Yeah, ability to use the road, sure. I don't think people want a new highway to be built and then told they can't use it because they don't have a new car or something.

I as a motorist could not give less of a shit if I'm stuck in traffic for 3 hours a day but the road is able to move hundreds of thousands of cars a day. I'd prefer a road that could only move 20 people a day with 0 traffic. It's the only thing I care about.
I think that refactoring is often used as a means to better understand code. This might be your own code that you wrote yesterday or it might be someone else's code from 3 years ago. In order to really understand a piece of code, some of us need to put their hands on it.

But I think throwing away the changes should be an option if there's no objective improvement. Very often those changes end up on the main branch but they only cause changes, not improvements.

The real outcome is in someone's head.
We (at least should) also do code reviews in order to make sure everyone understands the code.

On my team, the majority of code review comments are not discussing potential bugs, they're making sure everybody knows how the new thing works, why it was designed that way, implementation tradeoffs, etc. All that discussion is extremely valuable over the long run. For example, it means that nobody has to pay attention to email while they're on vacation in case something goes pear-shaped with a module they implemented.

That said, I 100% agree with the article's concluding paragraph about YMMV. Raycast is operating in an entirely different business domain from the one I'm in. It sounds like the reasons why Raycast likes their way of doing things don't really apply to us, and I don't think the reasons why we like our way of doing things don't really apply to Raycast.
detrimental to crushing it!
The 221B Baker Street Illustration
Meh. If 90% of the time it's a mindless ritual there is probably a better way to achieve the same goal. Code reviews are a huge time sink, especially for unimportant style- and naming nits.

Code review as mentoring can be great, if it's a directed 1:1 effort. Usually, it is not.
The new Matrix seems like a spiritual successor to the Animatrix more so than the movies
All I’m saying is that claims should have proof
Apple already provides something like that that’s WAY more popular and doesn’t require the waste of resources a public blockchain would.

I know some people (especially us techies) like to control the whole stack but who do you think the majority of normal users would prefer?
Hi, the author here. I'm excited to share FancyWM. It started as a passion project, I made it for myself after using tiling window managers on Linux for a while. It has recently acquired some of the final must-have features in my book, so I thought I would share it here.

Some of the criteria that I set for myself and couldn't find implemented elsewhere (together and the way I wanted them):
- Basic and unintrusive UI
- Dynamic layouts (no editing mode, no predefined finite set of layouts)
- Stack panels (tabs)
- Smooth window resizing and animations
- Simple to configure
- Efficient to use with mouse or keyboard
- Support for the Windows virtual desktop feature
- Doesn't interfere with other apps' keyboard shortcuts

The tiling idiom is based around "panels", of which there are 3 types: horizontal (default for a 16:9 workspace), vertical, and stack panel (tabs).
1. You create a vertical panel, and the focused window is automatically put into it.
2. You open a new window, and the new window is put in the focused panel.
You now have two windows stacked one above the other

There are hotkeys to move windows around, swap windows, resize windows, etc. But if you are a mouse user, you can also do that efficiently. If any hotkeys are missing, please open a feature request.

Some smaller notable UX features:
- The mouse-based controls for windows have a trigger condition that requires you to move just past the top border of the window. I don't ever see the overlay show up when I didn't intend to open it.
- Context-sensitive hints appear shortly after triggering the activation hotkey, and remind you which keybindings you have set up and which you can use currently.
- A focus highlight option briefly blinks the focused window.

A burning question I've been asked on Reddit several times is "is it free and open-source?". The answer is no (and I have no plans to do that). Parts of the projects have been split off and published on GitHub and NuGet (WinMan - an event-based windowing library; you can build a WM with it). There is also a public issue and feature tracker on GitHub.

FancyWM is a commercial product with an unlimited evaluation period. You must buy a lifetime license for continuous use. I understand that not everyone can afford to buy a license, which is why FancyWM aims to be perfectly usable without one -- but you will get the occasional pop-up asking you to buy it (like WinRAR or Sublime Text). I know what is affordable also varies with markets, so I'm hoping that the Microsoft Store dynamic pricing can handle that somewhat reasonably. As a student, I am super happy and grateful for every single purchase.

I am happy to answer any questions you have.
Issues and feature requests: https://github.com/fancywm/fancywm-issues
All three of them being pointless and wasteful.
I had a friend in high school who took mushrooms and said they never felt like the same person since then. That statement was made in high school and reiterated in their late 20s. I don't know what dosage they took. I don't know if they had other mental health conditions, though it seemed like they had some degree of alcoholism.

I have dealt with depression and have my eye on some form of Psilocybin treatment as a future option. But am weary due to my friend's experience. So I'm waiting for more expertise to be developed and the treatment to be validated and consequences quantified.
I had the same thought. Imagine listing all blockchains in tiny icons you scroll sideways. I suppose that can be done a lot better, but still, who decides which blockchains are included and which are not?
Except the ones that go on murder sprees. I guess they converge somewhere else.

https://en.wikipedia.org/wiki/Jared_Lee_Loughner
Isn’t this what hostels are for? Not shitposting at all; the organic aspect of it is why I stay at hostels well into my 30s.
203 pages PDF
I've implemented this a few times in a few languages based on exactly what nginx does. It works well, and it is pretty straight forward if you are comfortable with posix style signals, sockets, and daemons.

I'm not sure it is super critical in the age of containerized workloads with rolling deploys but at the very least the connection draining is a good pattern to implement to prevent deploy/scaling related error spikes.
Yes thank you. The point about not being able to create new land is a very good one.
Funny how intolerable are those "latent" diagnostics for illegal drugs, and meanwhile the totally legal and widely prescribed trazodone (an antidepresant) is known to cause, among others 1) suicidal thoughts, 2) insomnia, 3) hallucinations, 4) and paranoia. Other common drug, bromazepan, turns you into a half zombi, loss of ability to remember and amnesia, hallucinations... And it has a bad widthdrawal.

Of course you have to be careful when taking LSD, psilocybin or whatever. But don't replace info with FUD: just study, legalize and put the info in the box when sold. They are not worse than 95% of widely prescribed drugs. They are illegal just because they are also enjoyable.
Or that the culture surrounding them pushes people in that direction?

I do shrooms with people who work in tech (just did them last Wednesday). We talked about the intersection of "intelligence" and "emotional vulnerability", and why are group of friends gravitates toward and attracts people who have a healthy dose of both. No woo-woo love chants...just some deeper conversations, below surface level that provided insight into who we are.
If we need GET requests with bodies, why not simply add a body to GET?
Silicon Valley Can’t Escape Elizabeth Holmes
> It's like when people claimed that marijuana was not addictive.

I quit both weed and nicotine and only the nicotine was the problem to shift. Weed can be habitual, sure but there's a huge difference in physical and habitual addiction.
... why would I want to share my wallet to something I trust less than a strange dog? Or part of my identity? No thanks.

One of the great things about usernames/passwords is it didn't demand that vulnerability - you could come up with whatever and it was your responsibility to keep up with your shit. Systems that mimic real world systems on average feel less prone to this silliness.
yeah, though, it seems they want to go legit through the eyes of regulators.

personally, I would've preferred an ICO. It's the new-world fundraising model that should be normalized.
Imagine you evaluated the performance of all a human's muscles, and gave an overall 's' score to individuals based on the aggregate.

It would be a vast simplification, it would be combining slow and fast twitch muscle fibers, it would be combining heart and legs and torso muscles... you would want to be far more precise when dealing with an individual and evaluating how to benefit or correct their musculature.

But still, you could probably take any group of ten people and quickly arrange them in a line from lowest to highest 's' score. You would find a huge correlation between 's' and various professions.

Equating it with astrology is silly, a rhetorical flourish that nobody sensible could believe.
Find a gym with classes like Zumba, Crossfit, Spin, whatever. If you go to a few classes you will find one you like.

The instructors design the class so that you get a reasonable work volume with low risk of injury. For me the instructor always gets me to do more work volume then I would do on my own.

A class is good because you can compare your performance to others that are doing the same thing.
Sorry, I realized you're talking about build dependencies, not eg. individual programs that are written in Rust. I agree rustup should probably be the only Rust build dependency.
Trusted News Initiative
What an incredible post.

Whether you agree or disagree with the guidance here, you have to respect the effort that has gone in to put this together. Especially good in understanding the role of the corporate recruiter - not a friend, not an enemy - though I would add nuance such that they are not a friend but become a friend once you secure the endorsement of A N other assessor.
> General intelligence is a very mainstream concept.

Yes, psychometrics researchers believe in psychometrics.
This is an interesting read and I'm glad to see that the closing paragraphs emphasize the need for each team to evaluate their own needs. That said, for me it all comes down to the definition of "best product" in this statement:

"They all want to build the best product in the shortest time possible"

From my perspective, the "product" is not limited to what customers see or the code itself. It's the set of outcomes from the code being written and executed. For example... Do other engineers understand the code? Can they support it efficiently? Does it fail gracefully? What is the impact of failures? Are failures automatically detected? Does it lead to security breaches? Did the code author learn things they could do better that they didn't know to ask about? Did other engineers learn from reading the code or asking questions? Are customer requirements satisfied? How much is customers' trust impacted by failures, bugs, and feature that don't meet requirements? How big is your cloud provider bill? Etc...

If the priority is quickly delivering and iterating on features that satisfy customers' needs AND engineers will be supporting their own code, then the "No Code Review by Default" approach has its merits. In fact, I have personally found this approach to work well on constrained, isolated pilot projects where the priority is to unblock key scenarios for a limited set of customers and/or learn about customer needs before building a the "real" solution.

For anything else, I would suggest following the author's own advice: "ask yourself if the circumstances of others apply to you".
I'm a dog...
"Norton is installing a Cryptocurrency miner" sounds like when 10-15 years back it made the news when one app or one OS installed adware or spyware. We did nothing, and now it is becoming the norm.
If that's the trend, then, ladies and gentlemen, we're screwed: every piece of software will attempt to monetize from user's hardware, no matter the cost, particularly when cost is on the users. Name one reason why they shouldn't do that, there's no law forbidding it except common sense.

Cryptocurrency is cancer. It doesn't scale, it can't scale, it's becoming a huge unsustainable environmental disgrace, and it's the #1 reason why certain hardware is harder to find and overpriced, followed by energy, of which we have plenty but decided to waste it in mining farms.

Here are some numbers, just look at the trend: from 77 TWh to 204 TWh in one single year.

https://digiconomist.net/bitcoin-energy-consumption/

https://www.businessinsider.com/bitcoin-mining-electricity-u...

Now just picture what will be like 5 years from now with possibly one PWh of miners worldwide pumping heat in the atmosphere 24/7, and energy prices skyrocketing because it will always be allocated to this task, therefore demand will always be higher than offer. Seriously, WTF!

Of course I expect downvotes from users with vested interest in cryptocurrencies, however I politely ask others to reply with "You're wrong because ..." followed by a believable explanation. I want to be proven wrong on this.
> How many Stanford graduates marry burger flippers?

That isn't necessarily Eugenics. If they think that "burger flippers" will produce inferior offspring, it's eugenics. But I suspect that if there is a low incidence of Stanford grads and "burger flippers" coupling it's due to other factors, for one thing the fact that they are two relatively small populations that likely have minimal interaction in a dating environment.
Yeah, IMO this is like a publisher saying "we don't have editors: we trust our authors". The intended ethos of editors and code review is that mistakes and imperfections are the norm, and you need a second pair of eyes to iron them out.

That said, I do sometimes encounter individuals or cultures that seem to view code review more as a mechanism for catching abnormal/unexpected mistakes than as a normal part of the process of writing code.
Jus another reminder that the modern browser is an awful platform with basically no unique purpose but user exploitation - which is why it happens to be ubiquitous.
The cam-tightening metal caps on these are so satisfying to open and close. Fond memories of mowing the lawn / nearly burning myself to pieces playing with gasoline.
Sounds nice but perhaps a best fit if you are 1) a small team 2) people know and trust each other already 3) people are all and equally
comfortable asking for reviews (disturbing others, essentially).
4) the code has a priority on feature progress rather than stability and correctness.

The situation can be very different in any of those aspects and mandatory review can still be a good idea. Are you building code that runs on surgery equipment together with 4 people you just met? I think you should probably have a formal review process. Or are you iterating towards an MVP for some webapp with a few people you consider friends? Lgtm just deploy to prod.
NY makes major adjustment to Covid hospitalization reporting during surge
Did you ever notice how the shroomers have a different look in their eyes than the acid heads? There's a lot more warmth to the former as you noted, but there's a tendency to believe really far out things. One friend of mine was convinced she was immortal so she worried a lot about how she was going to replenish the sun with hydrogen so it didn't burn out. The acid heads have a look in their eyes like they are lost in a void and are struggling to get back.

Edit: I should note I'm talking about people who do a lot of mushrooms. For example, my friend lived on a commune in England for several years that did high doses of mushrooms on a weekly basis as a community bonding thing (like a Sunday church ritual)