Ha! At one point some years back, in an internal presentation somebody used an image of an old computer that if you really, really squinted and looked closely, had a topless woman in ascii art in a small area of the computer screen. It was so hard to see that most of us didn't even notice, but one eagle eye did and caused a whole shit storm around it. If the presenter would have said, "Those are just compliance tits" I think my life would have been complete :-D
Great story! I remember sharing my screen at work recently and the URL bar suggested https://thisisnotporn.com/ because I had been playing it a bit on my phone and my browser history synced to my work. I dont know if anyone caught it but I started using a different browser after that. Because it indeed is not porn but hard to explain that!
I'm not GP, but I've been experiencing this too. All my coworkers are in the same boat though, so we don't really have anyone with the deep understanding. Our approach (which has been working pretty well, we've solved a lot of problems and learned some along the way) has been to use AI as an informer who also points us to sources (like documentation, github issues, etc) where we can then read up on something the AI has pointed us at. We try to time box things a bit to prevent going down the rabbit hole, so we don't always get to exhaust our curiosity, but we're continually gaining that knowledge and pressing forward. Most recent example is tuning the kernel settings and our app on our prod machines to behave better for WebRTC packet handling/forwarding. AI for things like ffmpeg has been a god send when nobody on the team is an ffmpeg expert.
I've also had success just asking claude to write documentation on a system or subsystem or module, etc, and reading that. I then sometimes have it turn that into an svg diagram or something visual that often helps understand things. That domain-specific knowledge is hard to gain though, so not a silver bullet by any stretch.
For real, it's been the most validating of my use-open-source ethos than any other examples I can think of! For this open source isn't about the cost, it's about the vendor dependence/neutrality, and that's quite important when it becomes essentially a business requirement.
> If, instead, it was done at USPS offices or even by postal workers on their routes, no one would complain.
You must have had better luck with post offices than I have. Having lived in a dozen states and used many different post offices, the vast majority is an utter nightmare. Between the rudeness and the apathy, I would much prefer the DMV (depending on the state)
In principle, I would agree, however, the types of comments Claude writes are sometimes absurd. It will leave a 25 line comment above a variable talking about how in a debug session, it turned out that this value was too low, so it was increased on the current date to account for whatever. It will also leave giant comments like, reference security review from 2026-05-21. Even when that document is not committed
It will also inject a tons of information that it shouldn't. I do a lot of data pipelines and comments will be like, "this line is because there's 943,048,032 events in the blah table and it forms a conjunctive set with the 43,390,042 rows of the bar table..." but doesn't include the context that was run against a dev instance.
And if I don't catch these and remove the bad information, subsequent passes will flag those comments and get stuck on the fact that numbers don't match and start digging into that "problem" instead of staying on topic.
Ha! At one point some years back, in an internal presentation somebody used an image of an old computer that if you really, really squinted and looked closely, had a topless woman in ascii art in a small area of the computer screen. It was so hard to see that most of us didn't even notice, but one eagle eye did and caused a whole shit storm around it. If the presenter would have said, "Those are just compliance tits" I think my life would have been complete :-D
reply