Hacker Newsnew | past | comments | ask | show | jobs | submit | shepherdjerred's commentslogin

That’s what he does except it’s every 6 mo

https://www-cs-faculty.stanford.edu/~knuth/email.html


Claude sometimes refuses to work with credentials because it’s insecure. e.g. when debugging auth in an app.

So, what's your proposal? What should insurers be doing differently?

Operate like they did before they had access to surveillance technology that would have made Gestapo and Stasi blush

This. If you're nearly "perfectly" pricing risk on an individual level then you defeat the point of insurance which is to pool risk.

If my hypothetical cost over an N decade period is within a fraction of a percent of payouts in that time what do I gain by paying for insurance other than creating a principal-agent problem?


You’re mad the insurance companies are charging you what you owe? You do have the option to self-insure.


I can tell you, with absolute certainty, that before AI ~0 junior/mid level devs spent just 20% of their time programming. At least not at tech companies

Every company I've worked for that is the case. Note that I divided a lot of the work out that might be counted as coding though.

Computers are definitely on the path to freeing programmers from programming

Surely you, a programmer, can imagine a way to automate this process

No, I actually haven't made, nor desire to make, a way to automate "thinking about, researching, and solving a problem".

I went into this field because I love programming. I didn't even know how well these jobs paid until my junior year of college when I got an internship at AWS. I constantly programmed and read programming texts in my spare time growing up, in college, and after work.

I love AI tools. I can have AI do the boring parts. I can even have to write polished, usable apps in languages that I don't know.

I miss being able to think so much about architecture, best practices, frameworks/languages, how to improve, etc.


I have met very few devs who know how to avoid useEffect

> with an emphasis on maintaining quality and operational excellence rather than introducing new features

it sounds pretty clear that it's in maintenance mode


It’s clear enough but they aren’t going out of their way to make it obvious. It’s definitely fluffed up / corporately sanitized.

Damage control to limit the rush for the exits?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: