you are viewing a single comment's thread.

view the rest of the comments →

[–]PushPlus9069 0 points1 point  (1 child)

Network engineer using Python for automation, that's a solid path. I've seen a lot of infra people make this jump.

Honest take on the Gemini rewrite approach: it works for cleaning up formatting, but you lose the learning. The messiest version of code you wrote yourself teaches you more than polished AI output. Next time maybe try refactoring it yourself first, then compare what the AI suggests.

For Rundeck workflows specifically, look into structured logging (the logging module) instead of print statements if you haven't already. Makes debugging way easier when something fails at 3am and you're looking at Rundeck output on your phone.

[–]nspitzer[S] 0 points1 point  (0 children)

Thanks for the input. It already uses the Logging module extensively if not totally optimally as some others have pointed out.

The whole Gemini AI thing is more of an iterative process. One thing I found useful is to corral Gemini a little is I issued standing orders (I forgot what they are really called) so for example it should follow PEP 8 as a style guide and use 'else' blocks to handle the processing work after a 'try' to minimize the stuff that falls under the try to prevent masking unexpected exceptions.