HN user

closeparen

20,532 karma
Posts5
Comments7,432
View on HN

From what I've read, very few people who buy ortho split keyboards, even people who love and swear by them, ever recover their WPM. I could never get comfortable on my Ergodox. The Glove80 seems more promising, but I can't afford the productivity hit at work, particularly when communicating on Slack. But the Kinesis Freestyle2 with the tenting kit quickly became my daily driver & basically solved my wrist and thumb pain.

Now, since it's impossible to code review the tens of thousands of lines of code that AI produces

I would simply not ask the AI to write me more code until I'm satisfied with the code it's already written! But it is true there's more of an opportunity to let the thing rip if you can give the harness the ability to meaningfully verify its own work.

Name, address, and phone number served plenty of critical functions when they were published in the White Pages. Cell phones not being listed there was kind of an accident of history. It was common to call a listed landline and be given or forwarded to a cell number. Only after most people stopped having landlines altogether did a phone number come to be considered sensitive information (unless you were a celebrity or something).

Ironically Facebook is responsible for much of this, as friending someone on Facebook became a lower stakes, less intimate alternative to exchanging phone numbers.

Around $400 a month of plans buys roughly $2800 of API usage at list prices, which is a real bargain right up until you hit the ceiling. The plans are metered, and any large AI native workflow will chew through the included tokens fast

I don't think that's true at all. I'm doing 8-12 PRs a week at work, all primarily Claude Code, and the usage at API billing has never broken $500/mo.

It is too bad that so many companies have built these huge microservices beasts where you cannot run much more than unit tests locally, and you pretty much have to guess at the impact of your change until you have merged it, deployed it, and turned on the feature flag for your own account / test account. This loop is slow, which is perhaps a cost they are willing to pay, but it is also not safe for agents, which will be a massive setback.

The narrative "we don't need as many staff because of AI" is a labor disciplining device whether or not it is true. Remaining engineers, loaded up with more projects under the threat of layoffs and with no outside opportunities, work nights and weekends to get them done. Then it is literally true that we accomplished more with less. And in a sense it is even "because of AI." But not in the way that you're supposed to think they mean it.

Which is why junior and senior talent alike are forced back into the office. Except that tenured senior and staff employees from the boom times are in the San Francisco office, but all the new grad hires from the last 2-4 years are in various third world offices. And neither of them can get conference rooms, so everybody's on Zoom at their desk all day, trying to be heard over their neighbors.

Is this situation so uncommon? Almost everyone who lives in a house in California, for example, is living primarily off the unrealized gains on their home equity. Very few have the wage income to qualify for a mortgage on what their lifestyle is worth now.

California contains a lot of houses!

Average American workers provide in-person services that don't scale and can't get much leverage from technology. Retail, hospitality, construction, care work, etc. They have not seen the kind of wage growth that accrued to the laptop class, but for the same reasons they are not as vulnerable. Probably we will end up alongside them. Plenty of demand growth coming in the elder-care sector.

We consider a measure of necessity spending that includes but is not limited to childcare, external credit card payments, gasoline, general retail, grocery, housing (mortgage/rent), insurance, cable TV/broadband, public transportation, tax payments, vehicle costs and payments. We consider spending across payment channels (ACH, credit and debit card, bill pay). Income is defined as regularly recurring payments into accounts, such as payroll, social security, unemployment insurance pensions, and annuity income. Households are defined as living paycheck to paycheck if in the quarter their necessity spending exceeds 95% of their income

This is more thoughtful than some "paycheck to paycheck" discourse, put objectively well-off people definitely put themselves into this picture by signing up for more house, more car, or more credit card spending than even the relatively high level they can afford.

Seems most relevant in a hobbyist context where you have personal stuff on your machine unrelated to your projects. Employee endpoints in a corporate environment should already be limited to what’s necessary for job duties. There’s nothing on my remote development VMs that I wouldn’t want to share with Claude.

It would be better if they specifically excluded advertising uses of call metadata, etc. I assume this is getting mixed in from their ecommerce efforts to sell the devices. But how do you expect them to play back the voicemail if they don’t have it? What would be the point of "please leave a message after the beep" if the audio is going to /dev/null?

It would be pretty spooky if your voice managed to come out the other party's telephone without ever having been collected into and processed by the telephone network. Taking audio from one place and transporting it to another is what we pay it for.