It's beyond contest that the g factor is real in part because it's a statistical inevitability in any series of related tests, be they for intelligence or product/market fit in automobiles. It's an exploratory statistic, a hint at underlying causality; it is not a dispositive revelation about the structure of human thought.
Sure: there's a battery of general cognitive tests, and if you smush data sets together a dominant factor will emerge. And?
This is exactly my point. It's tautological to argue that IQ isn't correlated with intelligence. It is, definitionally. You seem to acknowledge this so perhaps I don't understand your original comment.
Just to point out that this whole subthread wildly misses the point. We get that you can quickly install an app from the app store. The culture we're talking about is Emacs. You can quickly package-install something from Emacs, too, but the odds that you'll have it working the way you want it to be working within an hour are... not the same as that of the app store.
In Emacs-land. Obviously clicking a button on the app store is easier than describing to an agent precisely the application that will solve your problem. But Emacs doesn't work this way. There's a whole subthread next to you that got all confused about this and started challenging Dan to like a WhatsApp duel or something; they've all missed this point completely.
Whoah, whoah, whoah, you two, this is a happy post, not an angry post. Nothing to get wound up over! Part of the point is that you can both just go and do you!
We're not fighting, we're just "emotionally explaining things to one another". That's what my wife says to calm our dog, when he makes a concerned and scared face over a regular, non-confrontational conversation. Just to be clear, I'm not comparing you to our dog, I just thought it's a funny anecdote.
Software that today is overwhelmingly prepackaged and usually professional, which I think at this point the nerds should reclaim:
* Podcast apps
* Music listening apps
* Feed readers
* Bluesky clients
* Note-taking apps
* Desktop bookmarking/read-later apps
* Chat and instant messaging
* Time trackers
* Recipe managers
These are all things that you can get better-than-replacement-grade results from Claude on --- not necessarily the best, not necessarily the most globally competitive, but certainly an application more closely tailored to exactly what you want it to do for your own idiosyncratic work style.
Music.app is a miserable experience, and I can just tell as I use it that it's miserable trying to serve me. But Apple long ago factored all the meaningful bits out of Music.app into MusicKit. Why am I still using Music.app? MusicKit is the real product now. This is new.
The common denominator: the data needs to be owned by you, or at least made accessible. Companies love to create walled gardens where they own the content and control how you access it, making this kind of personalized interface impossible. Hopefully we can push back more now.
The ability to quickly make an API connection + custom UX means that companies with a sub par website / app but a good data API are more valuable to me than the world class fancy website with a locked down API.
At work I have a great brain dump + TODO list tracker via custom API + MCP into confluence, using confluence pages as the app state. The website is so bloated it takes like 20 seconds to go from "idea" to getting it written down. Im now able to avoid all of that and make ~ MY ~ perfect UX while still being a good corporate employee.
I mean, hold up, if that thought lights you up I'm happy, but I don't actually think that's the common denominator. I used Things.app to track projects for a long time and ultimately fell out of love with it. Things.app didn't own my data; it's a pure UI app.
But now it occurs to me: I know precisely how I work, I know what patterns are valuable to me, I know when and how I need to remind myself of things. I don't know why I haven't already started building my Things.app replacement. But I'd guess I have it to a place where I'm happy by this time Saturday.
Honestly, it's harder for me to think of daily-driver apps where this wouldn't be the case. I guess vector graphics editing? I'm not going to vibe up a vector editor. But I'll bet all the money in my pocket that 5 years from now, the real value in vector graphics tools will be their API/SDK, not the packaged application experience.
I'm not following your reasoning about the common denominator, not sure we're on the same wavelength about what I meant. I'm claiming that in order for an application to be "reclaimable", you have to be able to access and manipulate the data under the app. Some applications currently work that way now, lots of them don't.
For example, we can "reclaim" non-DRM ebook readers, audiobooks, and music players that play local files or use an open API. But a company-specific walled garden streaming DRM'd ecosystem will be almost impossible to build around.
You're talking about entire systems. That's something to be optimistic about too. But it's actually not the thing the comment you responded to was about. I'm not saying I'm excited to get out of the Apple Music ecosystem (I like Apple Music, the service, quite a lot). I'm excited to get out of Music.app, and into my own custom Apple Music player; one where playlists and play history are simple, sanely-schemaed sqlite databases.
I gotta be careful, I'm going to talk myself into staying up late tonight building that.
Ownership can have different forms. Slack.app that doesn't let me easily extract code snippets from a thread - owns me. Jira that forces me to use their imbecilic, quirky wysiwyg owns me. Note taking app that keeps the data in their db and not my files - ain't my friend. The friction is the ownership. When extraction requires effort, the tool has leverage over you. It's a subtler form than data lock-in - behavioral lock-in. You adapt your workflow to what the tool makes easy, and gradually the tool's affordances shape what you even think to do. information gets buried in threads, search is mediocre, export is hostile. The "solution" they offer is to stay in Slack/Jira/Dropbox/Evernote/Notion/etc. longer, search in Slack, link to Slack, screenshare in Slack, summarize with AI in Slack, don't ever leave Slack. The tool becomes the answer to the problems the tool creates.
Plain text, local files, standard formats - they don't fight you on extraction because there's nothing to protect. That's why investing in FOSS tools is almost always paying for your own liberation rather than your own imprisonment. Even when there isn't feature parity, even when the FOSS tool doesn't have a "polished UI" and it's "maintained by a teenager in Nebraska" - still a better choice.
Something like old school Facebook in UI, but functions more like MSN Messenger. You connect to your contacts via P2P, and download/upload updates to your social media network.
An unfinished spreadsheet-based interface for entering time. Meant for consulting, but never got around to persisting the data. Mostly created it because I couldn't stand all the ways that time trackers force users to enter structured time when there's a cute algorithm to handle just about every way a human might naturally enter time.
In the days of LLMs, it would be far easier to categorize ingredients and format them into TeX for publishing as a PDF file. The idea behind this project was to let people essentially copy/paste recipes off the web or scans of handwritten content and autoformat it.
What would be amazing now would be a way to deploy my own Claude-built utility applications to my phone without having to go through the effort of securing a Mac developer account and going through that whole rigamarole.
I just made a one-shot Android music player because I need a very simple one to listen to tracks to practice drums, and I need to go back from the beginning a lot of time, reduce speed, open them from Whatsapp when my teacher sends them to me and access easily the last 4-5 played.
There was nothing in F-Droid that ticked all the box so I just made my APK.
> but certainly an application more closely tailored to exactly what you want it to do for your own idiosyncratic work style.
Yep, I'm doing this all the time. I've been doing it for a year. The silliest on is an IG post previewer. My app is better suited to me than the preview function that Instagram provide itself.
Many of them have been reclaimed. Check out the "awesome self hosting" GitHub repo.
Podcasts: audiobookshelf
Music: 500 different subsonic clients, many of which are good. Or some fun tuis
Feed readers: lol, more than there are grains of sand in Torvalds' flippers
Note taking: again innumerable, also, just use nvim or emacs of course
Chat: tons of very good self hosted options that can save orgs thousands a month.
Rather than build your own from scratch, rediscovering already solved issues, why not contribute to or fork a FOSS project? LLMs make it easy easier to get up to speed on large projects
Audiobookshelf is a web app! Like, if you had a good TUI music player, I don't think you'd be rebutting my thesis here. I don't doubt anybody's ability to build TUIs.
The point of the post is the emacsification of the native macOS (and Windows, I assume) environment. Totally reasonable not to care that it's occurring, that's not really responsive to the post, is it?
I was responding to your comment that nerds should reclaim software that's overwhelmingly professional and pre packaged by sharing that there already is FOSS software for the categories you listed, which imo represents nerd reclamation.
Audiobookshelf has a native android app, not sure about desktop, I only use it on Android.
Anyone can build a TUI sure but why try to rebuild the whole mpd client/server stack that lets anyone on your network play music from the several TB collection of FLACs on your NAS? Same for subsonic, why reinvent the client server protocol there when it's already solved? And for subsonic clients, why reimplement streaming, offline downloads with de-duping, stream bitrate, album / artist handling... If there's something a subsonic client doesn't have that you want, fork it, point claude at it, done! That probably falls within the emacsification thing, right?
Music apps especially went downhill, spotify and tidal etc need to offer apis so we can integrate several sources in one app. They used to offer much more. I was able to import my library into spotify once (thoigh it could only hold 10k item back then). I want all my music in one place, not 4 apps
I have Gonic (a subsonic server) on my home server and my client is a perl script. It basically allows me to search for an album, present a prompt for me to select the best match, and then builds up a playlist for the tracks to pass to MPV. That’s pretty much all I ever need. I would gladly dump the whole spotify client if they had an API to do the same (even if the queue is a long stream of data instead of tracks).
There's something about this whole situation that rhymes with the issue of LLM-generated prose. It's not that GPT 5.5 writes bad prose (I mean, it doesn't write good prose, but it's not awful). It's that once I pick up on the text being GPT 5.5's, my brain switches into a mode where it starts reminding me "this is just GPT output, you could just ask GPT 5.5 these questions yourself, and get answers better tailored to what you want to know". Why am I reading this one particular artifact of a conversation with the LLM? Once I know what the conversation is about, I can just have a better one myself.
Same deal with a lot of this software. I guess there's some "taste" to it, but mostly what you care about are the ideas and the "recipe".
Also, you should just do a monthly "Vibe HN" thread.
Those are great points and it leads right back to the solipsism thing. Also, you snuck a "It's not that X, it's that Y." in there. Nice.
> you should just do a monthly "Vibe HN" thread
It wouldn't stop people from feeding them into the Show HN stream, which is the problem. If we had a good enough way to tell them apart, we could factor them into two streams, but we don't yet.
> It wouldn't stop people from feeding them into the Show HN stream, which is the problem. If we had a good enough way to tell them apart, we could factor them into two streams, but we don't yet.
But it would allow for a culture to grow where the posters would self-contain their submissions into those threads.
I don't want to make this about people's faith or whatever, but to put it frankly, I've heard a lot of contemporary Christian music, I don't care for it, and [I like to think] I can reliably recognize it in three notes or fewer,¹ which may or may not bear out in rigorous testing, but saves me a lot of time either way. This feels like it parallels strongly with the topic at hand
No one mentioned vi, I like neovim just fine, and I'm using pi daily. Nice try though. My only point is that if you want to talk about rewriting everything yourself, NIH, churn, whatever you want to call it, Emacs is absolutely not a great example.
It's going to the administration overhead. If you have to document everything and argue for every medical procedure and deal with 20+ different processes for filing claims then it takes time. And, as a provider, you have to pay someone to spend that time if you want to get paid.
It doesn't help that our healthcare billing systems are so outdated and broken. I once had a doctor visit denied with the reason code that it should charge the other insurance (for people on multiple plans). I was only on one plan, but my wife was on two. The doctor and I went through all the paperwork - my name was right, my birthday was right, my policy number was right and when I got notice of the rejection it had my name on it. Eventually we traced it to an error - not in my insurance company, not in the company that handles claims in this areas for my insurance, but instead in some middle-man company that was responsible for transferring claims between the two. Nevermind that all three companies claimed to be BlueCross BlueShield. This took over a year to resolve.
No it's not. There is absolutely no way to get from $360B of insurer admin and net cost of insurance to $2.5T --- two point five trillion --- in practitioner costs on paperwork overhead. That is not a plausible argument.
> A new study finds that the extra time and labor physician practices spend on interacting with insurance companies and government entities cost U.S. physicians $82,975 each per year, while doctors in Ontario spent $22,205.
> Canadian physicians follow a single set of rules, but U.S. doctors grapple with different sets of regulations, procedures, requirements, formularies and forms mandated by each health insurance plan or payer. The average U.S. doctor spent 3.4 hours per week interacting with health plans; Ontario doctors spent 2.2 hours. The bureaucratic burden falls heavily on U.S. nurses and medical practice staff, who spent 20.6 hours per physician per week on administrative duties; their Canadian counterparts spent only 2.5 hours on paperwork.
All that falls in your $2.5T bucket. And their cleaners, HR, etc. And insurers have had 15 years of innovation since that study.
You haven't done the math here. Multiply the numbers out. This is what I'm talking about. How are you supposed to engage with these topics if you're literally recoiling from 7th grade arithmetic? Congratulations, taken on your own terms, you just found 3.6% worth of savings from practitioner costs.
My local grocery store wouldn't even bother issuing a coupon for that small a discount.
Yes, as I said, if we accept your claim at face value, that every dollar of American practitioner-side insurance overhead --- not the delta from Canada, but every single dollar of it --- is mis-spent, you managed to identify 3.6% of the waste in the system. Congratulations.
I said earlier we'd gone round-and-round on this topic before, and I was a little burned out on it, but I didn't expect you to refute your own argument like this. I'm glad we gave it another run this time! This is a great statistic; I'll be using it elsewhere. Thank you.
Insurance has more than one way to run the costs up; this is but one of them. Weird rebate deals with drug manufacturers. Vertical integration. Buying practices and paying them higher rates.
> I was a little burned out on it
I just did my taxes and am a little burned out by the $49k in healthcare expenses I got to deduct on them.
The reason it's going to providers is because US healthcare is extraordinarily inefficient. Providers spend too much time doing, well, everything. From admin, to medical records, to documentation. Very little of their time goes to actual, direct care and decisions around care. You can talk to a doctor about this if you want, they'll all tell you the same thing.
Even surgeons. Ask a surgeon how much time they spend in the OR. It's less than you think.
> Today, many of those practices have been bought up by large corporations, including hospitals, private-equity firms and even health-insurance companies. It’s a shift that not only has changed how money moves through the health care system, but may also be helping some insurers boost their profits, according to new research published in Health Affairs.
> A study from researchers at Brown University’s Center for Advancing Health Policy through Research and the University of California Berkeley found that UnitedHealthcare, the nation’s largest health insurer, pays doctors who work for its own physician network, Optum, more than it pays independent practices for the same care.
This isn't a response to anything I just said. I really don't understand why people collapse into all this handwaving when people point out the obvious: the money in our system is going to providers, and, in particular, it's going to practitioners.
What difference is that supposed to make? The money is still going into the pockets of practitioners. And: no, the claim you're making here about practitioners fighting insurers: closer to the opposite thing is true.
The idea that the problem with our system is health insurers is just slopulism. We have grave problems with our system! But they start with the providers, where the majority of all the funding in our system goes, not to the scapegoats they've stoop up in our insurers. The distinction is vitally important, because the most popular answer to this problem is to extend Medicare to everybody, and Medicare is just as victimized by this as everything else is!
We pay doctors too much, and we artificially restrict the supply of practitioners. Those doctors routinely overprescribe. Every other problem in the system is marginal.
"The money is still going into the pockets of practitioners."
And by inflating that amount...
> Using newly available federal price transparency data, the researchers found that UnitedHealthcare pays Optum physician practices about 17% more than non-Optum practices in the same region. In markets where UnitedHealthcare holds a large share of the insurance business, that difference was even larger, up to 61%.
their capped-by-law 20% cut of premiums goes up, too. "Oh, those mean old providers we own charge so much! We have to raise premiums again!"
Show me the more recent NHE table where this effect shows up and I'll be ready to have the conversation, but right now this seems like a dodge. Whatever effect you're describing, if it's material, has to have started after the NHE data I just posted, from 2023. I don't remember thinking that the health system in 2022 was good.
Fun thing about the NHE: you can project it as far back as you want. The data is there.
I feel like we've been in this argument before, and I like you just fine as a commenter, but do feel like you're tying yourself into knots to avoid a simple conclusion plainly supported by the data. I didn't post a trend story about what companies are doing or who they're acquiring; I posted the macro NHE table from last year. It simply refutes the argument you're trying to make.
> It literally breaks practice and net cost of insurance out!
But it's not a "Cost of Health Insurance" item. It's an expense at the practicioner level! They have to factor that non-billable time into what they charge for the procedure!
If an insurer manages to double a doctor's administrative costs for billing/appeals/etc., where does it show up in your tables, per your link's PDF of definitions?
You have no evidence for this argument. It's just vibes. The numbers here are stark. It's not like it's close, between providers and insurers. Insurers are almost literally a rounding error.
You asserted "the macro NHE table from last year… simply refutes the argument you're trying to make", but that claim is false. You are welcome to answer the question about where "doc spends two hours on phone arguing with UHC" falls in the expenditure list; it's not insurance, but it's caused by it.
> Insurers are almost literally a rounding error.
Again, the argument is that the raw cost of health insurance does not reflect its externalities imposed on the other items in your list; that insurers drive up hospital and practice costs, as they have to staff up enormous amounts of staff and expensive physician time to deal with the insurer.
You stated this claim upthread, for the record, and tracked down an actual Canada vs. US statistic on this, which turned out to account for roughly 3.6% of total provider inpatient/outpatient expense.
Sure: there's a battery of general cognitive tests, and if you smush data sets together a dominant factor will emerge. And?
reply