skysight-inc/HackerNews huggingface dataset:
Because, at least in my opinion, doctors should be considering base rates carefully. If I come in with an unusual set of symptoms, then I don't want to be tested for something that is vanishingly unlikely and not tested for something that has an unusually high frequency of occurring given my specific situation (demographic, race, vaccination rates in the community I live in for diseases that can produce my symptoms, etc.)

Medicine should not be one size fits all when better relevant data are available.

Different but related: I personally use similar information to determine the risk of various behaviors. Going to a meeting in someone's house where people won't be masked? Not a big deal if the current rate of community infection is very low in my local community. Playdate for my kids with friends who I know are not vaccinated for measles or pertussis or anything else? Depends on whether those are going around—and if they are, then I'd like to know how many kids are unvaccinated whether or not they're lying about it. If there's a way to get that aggregate information.
This page got the HN hug of death it seems. Absolutely deserves all the traffic he is getting, Mr. Ciechanowski's blog is an absolute gem.
Check out this repo for a 3D version of the same idea by Vinay Bhaip: https://github.com/vbhaip/perlin-planets
Would their keyboard really be better for hand size? Seems to me that unless the keys were uncomfortably narrow, it would actually require bigger hands to play big chords than on a standard piano because they’re fitting all the notes in a single row instead of two? But I’ve never seen one in real life, let alone tried to play one.

I wouldn’t say that the standard keyboard is designed the way it is to make any one key “easier”, it’s more just the result of mapping the mapping based on how our notation works, and it’s just happens to be that one key doesn’t have sharps or flats so you don’t need the black keys, so it’s easier at first… Thinking of it in the way you said is probably unhelpful.

Eventually every scale becomes as easy with muscle memory if you practice enough, but the best thing to do is to try and do scales and chords by thinking about what the intervals should be. Getting intuition for that is a killer skill, especially for playing by ear when you can hear something and your fingers instantly know where to go to play it after finding the first note.
And ESR
This is what I was going to say. I think that the great problem of our time might be unforced errors.

I've said it before, but I take issue with just about everything that's happened in tech in the last 20 years. I've been programming since I was 12, so have about 32 years of experience. I feel that things really were the very best from about 1995-1999, but since then we've mostly had uninspired and brute-force solutions endlessly doubling down on the status quo, because that's where the money is apparently.

I just see such quick embrace of things like async, which I view as an anti-pattern. We're paying people $150/hr to build out complex solutions that nontechnical people were putting together in FileMaker and Microsoft Access in the 80s and 90s. Even our hardware has endlessly pursued DSP vector processing on GPUs, forcing us to manually convert our software to shaders or something proprietary, when scalable transputers and 1000+ core systems on a chip with local memories appearing as a single context (what we might call.. desktop computing) would have been so much simpler and better. I could go on about this stuff literally forever.

What's the solution? It's so simple that it's right under our noses: make the opposite decisions from the ones we have been making. Old school. Practice radical inclusion and hire people immediately based on their credentials and experience, rather than putting them through endless interview rounds. Bootstrap, and when you make it, pay it forward and help others make it. Get away from all this insubstantial profit-oriented disruption stuff and solve the actual problems in people's lives like how to reduce their dependency on handouts from the rich under trickle-down economics. We need automated food/clothing/shelter that's too cheap to meter, and we need it yesterday.
I worked with someone who did this. I'm glad he has moved on. He would not do basic tasks correctly. Had an attention span of a toddler. He was DBA and couldn't google simple problems. I asked him to do something he would say give me 20 minutes. 2 weeks later he would say "IT CANT BE DONE". Then, I would do it myself in a few minutes after googling the error.

Instead of applying knowledge, he would bring up all these buzzwords to meetings and not really understand what he was talking about. I get angry just thinking about it.
> They have the financial resources to build it in ~Rust but still chose electron. It’s a mind boggling decision.

Respectfully, I think you may misunderstand the company’s mission.
The deb-get tool helps Ubuntu (and derivative distro) fans grab extra apps
Yes. The "MBAs" saw cost cutting in draining worker loyalty and workers have been catching up slowly since loyalty and hard work is a cultural phenomena. When the workers catched up strategy wise there was a lobbying push for STEM crisis, "good people are hard to come by" or lazyness.

Instead of both way loyalty we see this push for "values" and cultural fit or what not. Very hallow compared to boring old 20 years of service.

My former employer a 100 yo company had these old rules for gifts to employees that had stayed 10, 20, 30 and 40 years. It was like a joke nowadays when engineers hardly stayed 3 years, including me.
That's what I have heard too.

I'm definitely not dyslexic, but I genuinely do just find Comic Sans to be easy to read. Serifs don't throw me off or anything and they look pretty, but they do kind of feel like noise when I'm actually just trying to read. Comic Sans just feels...legible? Like it was intended to be read-first, don't worry about impressing.
My main goal is to replace cloud services so I can be Google-free. I've also got LineageOS + MicroG on my phone. This is all running in docker containers on NixOS (other than OPNSense), with automated restic backups to a NAS as well as Backblaze. One of my goals is to be able to deploy all this again from scratch with minimal effort, and I think I succeeded, though haven't had to test it yet.

Nextcloud - for caldav and carddav calendar, contacts, and tasks

Xbrowsersync - sync bookmarks across device

Synchthing - backup data from my phone. I use Neo Backup to take a snapshot of all apps, so the phone should theoretically be restorable from scratch.

Jellyfin - Spotify replacement. The Finamp app is fantastic.

Home Assistant - automate my media center, as well as control outdoor lights and door locks, and check if any doors or windows are open or unlocked when I'm away.

OPNSense on a protectli box - amazing open source gateway software that does everything.

AdGuard Home (on OPNSense) - DNS based ad blocking

Wireguard (on OPNSense) - allows me to have an always on partial tunnel VPN on my phone and laptops that allows access to home services while remote, and also allows me to use my Ad Guard DNS.

HAProxy + LetsEncrypt (on OPNSense) - setup to provide subdomains for each of the services at home. Only a couple are public (contacts and calendar), but the rest become available when the VPN is on.

Smokeping - use it to collect data to rub into Spectrums face when they go down.

Pintry - Pinterest clone
From https://stripe.com/docs/financial-connections/fundamentals#h...

> With the authentication flow, your user logs into their bank either through an OAuth (bank-hosted) or non-OAuth flow to authenticate access to their accounts.

> Stripe generally defaults the authentication flow to OAuth if available at the financial institution. Your integration doesn’t need to treat OAuth accounts differently than non-OAuth accounts.
Maybe tech companies should provide their employees with pay raises so they are not forced to go to another company for that raise. New hires are often paid more than people that have been in the same role for years. You seem to argue that the employee should choose to accept a mediocre salary that does not keep up with inflation and the indignity of the new hire in the hope that just maybe in a few years a higher position will open up and that they will somehow out compete the other people vying for it. If they don't get it they should just continue to wait until the next opportunity. Or they could just go get a position doing the same thing at a new company and get a pay raise that would likely pay them the same rate as if they got the promotion. It has nothing to do with loyalty and everything to do with logic and not selling the years of your life at a discount to a corporation that does not even know you exist.

Note: I am about to start my 4th job in 6 years. My pay went from 55k to 200k in that time. Way less than many others on this board make but an unthinkable number for me and if I had stayed at the first job I would probably be making 70k maybe.
I like how the article was posted on May 4th and it has lots of Star Wars references.
GitHub seems to be going in the direction of solving the problem. Access to the repo only if you're a sponsor. But I think for people to start donating to you, you or your repo has to be known. It's a closed circle...
> No, no, no, no. You haven't really experienced the quality of IPv6 routers at home.

I've been running IPv6 at home >2 years. You're telling me that my own experience is invalid?
Plaid has left the chat.
Racket might be an easier sell, especially when it comes to tooling since it's much easier to pick up for one course.
The most encouraging signal on climate to me is that the “money” seems to finally be waking up.

ESG policies - backed by data monitoring requirements to combat greenwashing from sovereign wealth funds are real, arduous, and creating business and capital incentives with environmental alignment.

Early stage climate tech funds - of which their are many today where there were few even a few years ago - are giving a new generation of entrepreneurs something to focus on beyond monetization efforts.

And of course both company and billionaire branding is shifting to the importance of climate, carbon neutral solutions.

I take this all much less as a sign of altruism but of market efficiency - a shift towards making “saving the planet”profitable is the only model I believe will ever move the needle.

So to that end I applaud this effort - Just signaling viability of a career in the space is a great step in the right direction
That depends on how many parts you want to make and to what tolerances.

https://www.gearpatrol.com/watches/a636135/greubel-forsey-ha...
A co-worker of mine described this as 'surfing ahead of the wave of responsibility'
Lowes and plenty of other sites already forbid plus addressing.
(Render founder) I'm very sorry you ran into these issues. I'll follow up with the team and get back to you over email. We obviously have work to do, but I should note that we do use Render ourselves every day (render.com and dashboard.render.com both run on Render, and so do a bunch of our internal applications).

So why haven't we fixed everything yet? Ultimately, our bandwidth is limited (but growing!) and every day is an exercise in ruthless prioritization. We haven't ignored role based access control — we just haven't gotten to it yet (as a side note, https://feedback.render.com shows things we're working on right now).

I can't provide ETAs, but I can say with full confidence we will address everything you mentioned, and more. Give us time!
soulful post. for all the hell/chaos of twitter, it's still the equivalent of OkCupid for meaningful friendships.
As of 2022, it's now difficult anywhere in most US metropolitan areas.
> kicking the can down the road

When I was a kid, I remember my uncle introduced me to a guy he worked for who had made his initial fortune way back. It turns out that he bought a company that sold inner tubes for car tires, and when the automakers first moved to tubeless tires, the business owner wanted to sell. So, my uncle's friend bought him out cheap, and then targeted all the buyers of the new cars with tubeless tires. Apparently, the new car buyers didn't trust the tubeless tires yet, and the first place then went was to my uncle's friend to get tubes for their tubeless tires.

The lesson here is that change is hard, and as humans, we aren't very good at it. My guess is that humanity will be kicking the can down the road for quite awhile.
In San Francisco, the median household income was $120k. That’s 2 years ago mind you, and a lot of inflation has occurred since then.

https://www.census.gov/quickfacts/sanfranciscocitycalifornia
It's a bit like the Dvorak keyboard problem. It's slightly better, but too much of a hassle to bother with. You need something between 2x and 10x better to displace an entrenched incumbent.
>for experienced musicians priorities are legibility….

For novices too! Just increasing the physical size of standard notation would be a big help. 13x19 sheet music would be nice.
Why is Cleopatra constantly trending on Wikipedia?
Ohh, I see. Yeah, on rare occasions writev() is worth the hassle, but it doesn't really get around the performance loss from unbuffered I/O; if you're calling println(f.size, " ", f.date, " ", f.filename) in a loop that overwrites f 100 times, writev() reduces that from 600 syscalls to 100, but bufio reduces it to 1.

I do understand why io::file needs to be separate from io::stream. (The io documentation introduction gives an explanation of what you're explaining above; I'd additionally offer the examples of a gzip stream, a UTF-8-decoded stream on an ISO-8859-1 text file, and maybe a stream that feeds into in-process terminal emulator logic.) I was asking why io::handle does. If you're writing code that takes an io::handle, generally the code cannot rely on the fact that io::file can be used for select() or ioctl() or getpeername(); if it needed to do that, you would have written it to take an io::file, not an io::handle. So, if your code is only going to invoke io::stream-like operations on the io::handle, it would be simpler if its argument were an io::stream instead of an io::handle.

But what if you want to give it an io::file? Well, it's easy enough to wrap an io::file in an io::stream that just invokes the appropriate rt operations, and in most languages the only per-call cost of doing that is that your function call is indirect (mov 12(%ebx), %ecx; call %ecx) rather than direct (call Zn#]io31337write). In fact, most code would be more* efficient that way, because right now if someone gives you an io::handle and you want to read from it, you're usually going to call io::read on it, adding an extra level of function call around the indirect call, because that's simpler than duplicating io::read's conditional call to rt::read in your own code. But dynamically most read and write calls will probably be on a bufio::bufstream (or some other io::stream), so io::read is just going to call .reader().

Does io::handle maybe exist only as an optimization for sendfile()?

Maybe it's too late for such changes, given the amount of existing Hare code, and this qualifies as bikeshedding, and if so, I apologize.
This may vary regionally. I went through this with an account recently and did not have this option, despite looking for it (as I do have a hardware key).
Hi, how do you handle
1)articles?
2)chapters?
>> I have notes only on
ch1:Europe
ch4:Asia
I made a lot of friends on IRC and internet forums a long time ago. It is much easier when you are anonymous and be truly yourself. I miss these communities nowadays and can't really find a replacement.
Isn't the 20% time to work on whatever cool shit you want enough ? (like how googlers created that garbage angular1 because they were border, have no clue about GUIs and had some fun scewing around ) ? I know people that are fine with getting paid to maintain shit so maybe the problem is Google only hires cool developers and the cool developers only want to work on cool stuff and in 2 years the newest cool stuff of-course.
it induces the wrong idea as what is happening is a transition to usage and payment over other apps.
Good Accelerators offer this to their cohorts as a service. Techstars, which I was a part of, has a login-required site where founders post their experiences. Pretty useful to save you time with VCs that won’t participate in your round because of sector, size, competing portco
Thanks for the recommendation. I am a big fan of Weber, not familiar with Deming but his work sounds very relevant. In general I tend to agree that beyond a certain size organization these problems seem unavoidable. I've read Systemantics/The Systems Bible and it seems to come to a similar conclusion.
This, specially the pattern matching. Sequences, dominoes, there's not many ways they can be arranged. The first time people see them they will be stumped, but after knowing how they're made, the tested can figure how the testers think and answer them easily.

Another example is language and vocabulary, which are heavily influenced by culture and education. If IQ is going to measure education too, it would be valid to include number sequences that are the even digits if Euler's number, or names of famous astronomers without the vowels.
> I am not sure Stanford will do more with $1B than 10 2nd tier schools would do with $100M each

Absent data, it's difficult to say. There are economies of scale, even if just in experience administering such projects.
If Stripe can leverage their banking relationships to leapfrog Plaid by integrating directly with bank's APIs instead of doing screen scraping... that would be massive! It seems like Plaid's biggest weakness is the flakiness of their connections, which creates so much frustration/churn downstream.

Plaid's other weakness is their opaque, enterprise-style pricing, which is seems like Stripe is doing away with. Hopefully they can bring the price down, because lots of consumer-facing use cases aren't viable due to the high monthly price per connection.

I hope they add support for investment account holdings—it seems like Plaid is the only one that does this well.

—

Edit: digging deeper, it looks like Stripe proxies to Plaid-like "service providers" under the covers—at least for institutions without OAuth flows. [1][2][3] Presumably they'll build in-house connections over time, but it dents my hope that their connectivity will be better than Plaid's. Either way, transparent pricing and more competition in the space is still welcome!

[1]: https://support.stripe.com/questions/what-is-the-relationshi...

[2]: https://support.stripe.com/questions/how-does-stripe-limit-d...

[3]: https://support.stripe.com/questions/who-will-obtain-my-fina...
There is that too, but you could solve that by having engineers/teams working in new, cool, and useful products. I feel my company doesn't have a good mechanism to maintain services that aren't actively developed.

We experience it first hand when one of our services got deprecated and we moved to a new org. The solution was literally to hire a new team in a low CoL country and hand over the service to them. Needless to say it was difficult to hire for those positions.
Yeah, agreed. I'm totally on board with fixing the fact that you have to learn ledger lines / note placements separately for each clef. Besides that, none of this seems necessary, and the legitimately of sitting/hanging notes is a big problem.

I'm all for a notation system that distinguishes major/minor thirds more clear. It's a neat idea.
Someone writing an article in 2022 about Python's speed, and only citing articles from 2020 is not being honest about Python's speed. There were major speed improvements in Python 3.8, which was quite new then -- the linked article was not specific about which subversion of Python it was using, so we don't really know what the comparison was. In addition: The article that actually compared the speeds of the languages did a really bad implementation of a speed test in Python. The time library in Python includes a function for performance testing, which wasn't used, so much of the speed difference could well be due to using the wrong resolution clock. Also, if you're doing numerical calculations for speed, you should be using numpy. So, yes, if you tie Python's ankles together, and time it using an analog clock on the wall, it will not post a faster time than an NCAA Division I sprinter at a track meet. Thanks, that's helpful.
This is a most excellent writeup. Its so very clear, understandable, but also precise.

A word of warning, diving into watches and clocks can be a time/money sink.

If you're not careful you'll end up building something like this: https://www.secretbatcave.co.uk/projects/electromechanical-c...
I started with Greg Daniel's masterpiece: Watchmaking.

https://www.amazon.com/Watchmaking-George-Daniels/dp/0856677...
This is the kind of question that Rich Hickey (inventor of Clojure) dealt with here: https://www.infoq.com/presentations/Simple-Made-Easy/
> Sure, it's closed environment, but last time I felt so productive doing UI dates back to Visual Basic.

The "closed" nature seems to have made such IDE's better integrated such that you didn't need "layer specialists" for each layer: you just "did it".

And the rocket science needed to get "responsive" UI's right is crazy. If only 3% use an app on a mobile device, you bloated your UI by a complexity factor of about 10x to get that extra 3%. The labor math doesn't support it. Vulcan accountants are puking. (And mobile friendly apps tend to waste screen real-estate, increasing scrolling and back-and-forth navigating. GUI multi-panels are a productivity miracle, use 'em!)

WYSIWYG is cheap, easy, and consistent; you can save a lot by telling responsive to go to Bloat Hell. (Maybe someday a responsive UI framework will make it easy, but that will probably arrive with flying cars, hover-boards and Mr. Fusion.)

Being obsessed with "web scale" when most biz apps have only a few thousand users is also a resource drain. Stop putting phallic symbols into your stack, people! A dinky winky is sufficient for 95% of apps.

Choice of sub-parts by itself is good, but if it has a psychological side-effect of creating a layered mess, then perhaps a KISS Bouncer of some kind is needed to trim and factor the options. Otherwise, "cool" ends up trumping boring-but-productive. (I have more to say about his elsewhere around here.)
Makes me think of the Jankó keyboard which has so many benefits I would love to get one someday.

https://en.wikipedia.org/wiki/Jank%C3%B3_keyboard
We had the same experience when starting to use AWS/Azure. Our in-house team was all experienced with using VMware on-prem, with some mainframe and a few legacy physical servers. So we had a broad depth of knowledge for running our own datacenter.

So when we started using AWS, we really made a lot of mistakes by trying to replicate how we did things on-prem. And there was a lot of resistance to using cloud services; some people viewed it as a threat to job security. Others simply had a difficult time adjusting to the change in operations/procedures and philosophy.

This held us back quite a bit until we hired a few contractors who helped us better understand where we needed to change, which features worked well in the cloud (and which sucked). We brought the best contractors onboard as FTEs, and it's been a much better experience.