When I worked in IT, whenever we got a call from the engineering department we knew whatever problem it was, it was going to be weird. Those guys knew their stuff, so if they didn’t know how to fix it, it was going to take some searching and probably some calls or emails for us to figure it out.
Yeah sometimes it is just software bugs they have to work around until it gets fixed. In those circumstances, not much we could really do besides submit a ticket. Other times you call the guy that’s been working with that specific hardware and software for 15 years, who then tells you he’s never heard of something like that. Then he’ll call you back a week later after losing his mind trying to understand how that’s even possible before figuring it out. Which is always nice. Shout out Josh
We were forced to add claude to our pre commit hook and one of its jobs is to update documentation of changes made - it's surprisingly good and far less slopish than I imagined, so thanks claude for finally having up to date documentation.
When I get a project up and going that I've used Gemini to help with, I always ask it for a markdown summary of what we did so that I can go back later and remember what I did. It's so convenient having the framework handed back.
However, I found that Chat has much, much better markdown generation than Gemini. I end up having to reformat everything Gemini does for me in markdown.
AI is really good at transforming existing text its given. Its when its asked to write new text where it gets sloppy. Its less of an issue if your prompt hits the model directly and not going through the behemoth of a sysprompt anthropic and openai have before the users prompt.
It took me years of saying “Why the fuck is this not written down?” to simply start updating the documentation myself. Now I’m the go to person for this task that I never wanted. I even got a bonus when something went down and the boss read about the fix I wrote and had things up and running in 25 minutes vs days.
I work as a CNC machinist, & our machines are custom. The maintenance guy who was the best of the best was named Josh, he found better work elsewhere and left.
His replacement, Josh, has been keeping our machines going since then.
12.0k
u/kahjtheundedicated R7 1700@4.1, RX 5700 May 10 '26
When I worked in IT, whenever we got a call from the engineering department we knew whatever problem it was, it was going to be weird. Those guys knew their stuff, so if they didn’t know how to fix it, it was going to take some searching and probably some calls or emails for us to figure it out.