I mean, all I can really say is... if writing some logging takes you one or two days, are you sure you _really_ know how to code?

▲

boxedemp 7 hours ago | parent | next [-]

Ever worked on a distributed system with hundreds of millions of customers and seemingly endless business requirements?

Some things are complex.

▲

shepherdjerred 8 hours ago | parent | prev | next [-]

You're right, you're better than me!

You could've been curious and ask why it would take 1-2 days, and I would've happily told you.

▲

jamesmcq 8 hours ago | parent [-]

I'll bite, because it does seem like something that should be quick in a well-architected codebase. What was the situation? Was there something in this codebase that was especially suited to AI-development? Large amounts of duplication perhaps?

	▲	shepherdjerred 7 hours ago \| parent [-]
		It's not particularly interesting. I wanted to add audit logging for all endpoints we call, all places we call the DB, etc. across areas I haven't touched before. It would have taken me a while to track down all of the touchpoints. Granted, I am not 100% certain that Claude didn't miss anything. I feel fairly confident that it is correct given that I had it research upfront, had multiple agents review, and it made the correct changes in the areas that I knew. Also I'm realizing I didn't mention it included an API + UI for viewing events w/ pretty deltas

▲

therealdrag0 2 hours ago | parent | prev | next [-]

Audit logging is different than developer logging… companies will have entire teams dedicated to audit systems.

▲

fendy3002 3 hours ago | parent | prev | next [-]

Well someone who says logging is easy never knows the difficulty of deciding "what" to log. And audit log is different beast altogether than normal logging

▲

fragmede 7 hours ago | parent | prev [-]

We're not as good at coding as you, naturally.