t-writescode

This matches historical precedent in other nations where copyright was not extended to a photographer when a primate took a photo of themselves.

https://en.wikipedia.org/wiki/Monkey_selfie_copyright_disput...

Eeeh, Leetcode is older. I’m a millenial and it was popular when I was going through - 10ish years earlier.

I haven’t read the study, but I’ve read the comments so far.

I wonder if this mechanism is the same mechanism that impacts, say, swipe-focused dating websites, as well? And Twitter feeds with super-short messages. A lot of the most viral modern tech has been bite-sized content feeds of various types.

Healthcare being tired to employment and related lacks of safety net are the only reason the most abusive companies (call centers, common retail experiences) have employees.

We would do well to improve safety nets so that everyone benefits.

I’m glad that’s worked out for you. Not everyone has good plans.

Profitably-for-the-fabs*

Then perhaps we’re seeing one of the downsides of that. When 0->1 is prohibitively expensive, existing players can continue to raise prices *very* high because cost-of-entry is extreme, until it’s not sufficiently extreme.

And then we have bubble issues because the introduction of a new, cheaper player, causes the bottom to fall out and for the circumstances that allowed the new manufacturer to exist to completely go away.

When I’m having a heart attack, or when I’m in anaphylactic shock - you know, some of the most expensive procedures that happen - I’ll make sure to confirm the ambulance is in network, the hospital, the specific first ER doctor, the specialist, the surgeon, the lab, the lab techs, the anesthesiologists and so on, while I’m either unconscious or actively dying.

Citation needed (per capita please).

Given that people constantly, literally AVOID care because they can’t pay for it until it’s such an absurd problem that it’s very, very expensive, I struggle to believe this, at all.

And money amount doesn’t matter in this evidence because, again, Americans regularly avoid care until it’s catastrophic because they literally can’t afford it and/or have to wait for insurance to meet a certain harm level threshold where it literally can no longer be argued (emergency care)

No.

For a lot of people it very much doesn’t. And the cost is very prohibitive for people getting any care at all when insurance doesn’t cover it, so they end up not getting necessary care and then ending up on disability for life.

A healthy population *makes money for taxes and buying things*, too.

The last time we got similar results in the data (but not the text) was a Koch-backed study that a bunch of economists reviewed and went “so you’re saying we’d save 2 Trillion over 10 years relative the alternative?”

https://pnhp.org/news/the-mercatus-analysis-of-bernie-sander...

Is this quality improvements including or ignoring the 30-ish percent rejection rate of the most popular healthcare system, including such gems as insulin and pre-authorizations refusing surgery for necrotic tissue when “maybe they could PT it, have you tried?”

Honestly. They’re already performing miracles with RoR.

How many non Ruby apps and all the databases and systems behind could climb their traffic 14x when they probably only perf-tested for a sustained 2-3x and, and paid for a profitable amount of rack space rather than a “lol, VC money, we’ll 10x later” amount of infra.

Indeed. If you’re going to have an essay on top of a function or anywhere in code, earn the essay. That code better be operating on a ton of assumptions or using some creative logic to get to how it is that a simple reading doesn’t make sense.

I’ve done it myself on:

* engine definitions for complex workflows and DSLs

* heavy graph theory sections that included ASCII diagrams to clarify flow.

But those functions are probably 1 in 100 or rarer. Basically everything else is good enough with basic IDE-helping javadoc style comments at best, maybe with some input parameter clarification and business logic-clarifying 1-2 line comments sprinkled throughout.

I mean, sometimes I don’t know how I want to write something until I’m finished. Huge refactors are often like this.

So, just like you said, rewrite the whole thing, THEN break it apart into bite size chunks that tell the story and feed it to others with acceptable and reasonable context.

It’s a skill that engineers need, and it pays dividends to all on the team, including you, when your coworkers ALSO start doing this back to you and you’re asked to review it.

How? If one PR builds off another, won’t either:

  PR 1 is size 400
  PR 2 is size 400 + 400 new
  PR 3 is size 800 + 400 new

If they’re truly disjoint, would it be so bad to get them as unique? Because otherwise, when PRs depend on each other, you tend to get “one and then one and then one”.

At least that’s how it’s worked on teams I’ve worked on that have soft size limits.

AI passed the Turing Test empirically long ago. Further and more practically, they consistently convince millions of people that they are a real person with real intentions all the time, every day.

They are so convincing that an emergent property of the Turing Test is also being shown: that real humans are called bots by people that genuinely believe the other is a bot.

The standard 3-person Turing test with 2 people talking and a third observing and trying to decide which is a computer, if any, has been summarily defeated.

Good point, I suppose conservative is the right word there. Its broader meaning has been a bit louder lately, so I didn’t think of it the right way there.

Why? They went to medical school and passed all the exams. Maybe they just like art.

Cringe is too powerful of an anti-motivator.

Reminds me of when people wouldn’t listen to others because they had tattoos.

Is it obvious? Those existing APIs have known performance characteristics and deep integration into several other libraries. The moment you custom-roll your own root library, you break integration with all existing other libraries that depend on the defaults. To add, your LLM has to think about your new custom version rather than looking at the billions of lines of examples using the one it already knows works from decades of historical data.

If you really, really need some ultra-micro-optimization, you’re obviously not the target of this; but unless you’re doing HFT or the most inner loop of a game engine, the standard library and all its deep integration and battle-testedness is worth the 1% perf hit.

How many times have existing APIs made by experts in their fields had bugs.

How many of those are you willing to let your own services and your customers’ data be hit by whole classes of bugs that battle-hardened APIs have already fixed?

You sure you can get an LLM to handle every single one of them on first pass? Would you stake your company reputation and the PII of all your customers on it?

That’s definitely not true, and I’ll give two incredibly common examples:

1: arraylist. A library will probably do better than you. It’s already written and common.

2: webservers. Sure, you can write one yourself with sockets and a bunch of buffers and string management… or, you could use one of the 100s of existing ones. Which one? Probably a stable and established one.

It’s not about conservative vs progressive but about “safe, battle-tested, stable” vs “could be amazing future-tech”; and the idea of having a small number of innovative technologies, in particular where they matter, is about allowing yourself to spend all those thought-tokens on areas that matter.

You don’t want to be innovating your logging tech or your database if the old will work because you might spend 90% of your time trying to get your new, creative logging solution working when you should be spending it on the creative part of your business.

They already have a system for “prepaying”, but it can’t be used to put more credits into your account, they just sit there, waiting to be used by a future subscription.

That is an option for sure, but a very disappointing one. And it comes with a meaningful danger of ending up with 2 subscriptions: one yearly and one monthly. They really, really need to finish their “pay as you go” system. I don’t know why it’s not done yet and there’s been no word about it to my knowledge.

Kagi does have AI too, for what it’s worth. I found it pretty damn good, but I wish I could give them more money. I have a year subscription so I’m stuck without being able to give them *anything* until it’s done.

No argument here.

If we cared enough to be effective, we would be subsidizing / encouraging local manufacture of all of those at a competitive, non-luxury price.

I guess I’m weird. I like refactoring ugly mud and doing performance improvements. I like working on the slow, intentional, process-driven flow of actually migrating services between versions safely.

I don’t hate those and hope I get to keep doing them.

I also hope the AI writes good enough tests that I can trust them during the refactor process.