Post

John Nunemaker
@johnnunemaker.com

I feel seen. This quote explains my life now... "skilled engineers needed to steer Claude away from over-engineering parts of the system in response to hypothetical concerns".

0 reposts0 likes

jamie
@jamie.ideasasylum.com

> We don't need the nil check / safe access operator here. You can assume a <thing> always has a <other thing> Claude: well, actually there are three rows out of 500M which don't Technically correct but definitely not how a human codes

moger777.bsky.social
@moger777.bsky.social

The thing I run into is that it will have the nil guards everywhere, not just at code boundaries like user input or database rows. It makes the bulk of the codebase I read the same type checks everywhere. I'm still of the mindset that code should be reviewed but maybe I'm just holding onto the past.