|
|
|
|
|
by alexpotato
186 days ago
|
|
I work in crypto (L1 chain) as a DevOps engineer (LOTS of baremetal, LOTS of CI/CD etc) and it's been amazing to see what Claude can do in this space too. e.g. had an issue with connecting to AWS S3, gave Claude some of the code to connect and it diagnosed a CREDENTIALS issue without seeing the credentials file nor seeing the error itself. It can even find issues like "oh, you have an extra space in front of the build parameter that the user passed into a Jenkins job". Something that a human might have found in 30+ minutes of grepping, checking etc it found in <30 seconds. It also makes it trivial to do things like "hey, convert all of the print statements in this python script to log messages with ISO 8601 time format". Folks talk about "but it adds bugs" but I'm going to make the opposite argument: The excuse of "we don't have time to make this better" is effectively gone. Quality code that is well instrumented, has good metrics and easy to parse logs is only a few prompts away. Now, one could argue that was the case BEFORE we had AI/LLMs and it STILL didn't happen so I'm going to assume folks that can do clean up (SRE/DevOps/code refactor specialists) are still going to be around. |
|
10 years ago google would have had a forum post describing your exact problem with solutions within the first 5 results.
Today google delivers 3 pages of content farm spam with basic tutorials, 30% of them vaguely related to your problem, 70% just containing "aws" somewhere, then stops delivering results.
The LLM is just fixing search for you.
Edit: and by the way, it can fix search for you just because somewhere out there there are forum posts describing your exact problem.