mystifyingpoi

> has a tendency of running "find"/"ls" on your home folder

I've seen this first-hand. I was doing some work in a repository, Claude concluded it needs to investigate, how some AWS resources are created, and it literally started scanning ~/* for Terraform code. Which it found and started browsing through.

Or, when I asked Claude to debug some Spring issue, corporate firewall blocked Maven Central, so it literally started scavenging ~/.m2 caches to find the jar it desperately needed. Then it could not find it, so it started to clone Spring sources from GitHub to build the missing jar. I stopped the clone mid-way. I wish I was joking, I only stepped away from the keyboard for one minute.

> And to answer the burning question in your head, our goal isn’t AI that replaces SREs. It’s AI that supercharges SREs.

Ah, that bullshit reasoning again. No, if you build something that "supercharges SRE", someone will be made obsolete.

I'm geniuinely sick of this framing, seeing people at my company building company-wide skill repositories and shoving contents of their brains into slick Markdown documents. Well thanks, now our AI knows everything, good luck with your future career (if there is any left).

> SREs should configure their infra by hand sometimes to not lose that skill

Actually... yeah, I'd totally say that. Some SREs in my company never wrote a single line of HCL that wasn't a call to a in-house, pre-approved module. They think they know Terraform - they don't, and they don't know what's under these modules either.

I hate DST switching, and since last 3 days I've tried to live as if DST didn't happen, go to sleep super early etc.

It completely fails when you account for everyone else around you. Could work if you live alone with flexible working hours. But having a semi-active social life and kids makes it impossible.

> less mundane

This 100%. Past me would really enjoy writing a regex or inspect some undocumented API. Today me likes solving problems more, so I just throw Claude at the undocumented endpoint and after 10 minutes I've got a documentation with examples.

I also do not believe in it, rather I believe in 100% test coverage for the money-making code. Which is something like 5% of a product in reality.

Okay, I'll bite the bait. Assuming that I am a regular user (think gamer), I have a Windows PC, no dev tools, no AI subs or accounts, no GitHub. How specifically can I do the steps required to propose the fix they way you suggest?

It's basically industry standard right now, for shows to be pre-programmed this way. It has some disadvantages, but IMO there are more pros than cons, mainly predictability. (source: I was making the guide tracks)

How could you prove it was not a fair random generation? It's totally possible.

While I agree with the debt part, API pricing can also change at any moment. Well, anything can change at any moment, it's still wild west outta here.

Interesting point - syntax sugar was nice when writing code by hand. Now we'd be fine if no such sugar was added anymore ever again.

Does this excuse the main page missing any information what this thing even is? Come on.

Why does this need OIDC at all? Basic email + password account is like 1-2 prompts away.

Now there is Monday again, no more coding, back to babysitting agents.

Yeah, that's annoying. I've cross-checked with another engineer before filing the ticket. I agree that just slop-shotting someone is just a bad mannner.