Where do companies otherwise prioritize long-run development over short-term output? In my experience, generally nowhere. So why would this make managers push RTO more?
Some who already want RTO may use this as an excuse, but I would think it would actually reduce RTO pressure overall, as it confirms less short-term productivity, which is what companies actually care about.
In some areas and for some people, Medicaid probably does count as proper healthcare. But it certainly doesn't for other people / other places. Imagine there being one doctor within a multi-million person metro area who takes Medicaid for some sub-specialty. 90 minutes away from you by car. And you don't have a car. This is the reality for millions of Medicaid recipients, including ones I know personally in Chicago.
If I were making a single line code change, then Claude's "style" would take me enough time to edit away that it would make it slower than writing the change myself. I'm positing this is true also for the parent commenter.
This is interesting, and I'd say you're not the target audience. If you want the code Claude writes to be line-by-line what you think is most appropriate as a human, you're not going to get it.
You have to be willing to accept "close-ish and good enough" to what you'd write yourself. I would say that most of the time I spend with Claude is to get from its initial try to "close-ish and good enough". If I was working on tiny changes of just a few lines, it would definitely be faster just to write them myself. It's the hundreds of lines of boilerplate, logging, error handling, etc. that makes the trade-off close to worth it.
This has been true since it stopped being true for Internet Explorer. I've not noticed any significant change over time. I have been using Firefox for over 20 years.
Some who already want RTO may use this as an excuse, but I would think it would actually reduce RTO pressure overall, as it confirms less short-term productivity, which is what companies actually care about.