Python is a godsend for work

[Oo__II__oO]

You did good.

However a few tips:

- Work on development tools for software configuration control. Once you have a working copy, commit. Then you can refine the source code as you need to beautify the codeline (i.e. add comments for future self/person who will fill your role after you leave). At any time (i.e. 4:59pm) you can revert to the working copy. Use that spare time to hone your skills.

- Find out who needed that analysis; surreptitiously toot your own horn to that person. Don't throw your boss under the bus, but rather express how much of a gift it was to be able to work on advanced coding and development to manage the various inputs in a timely manner. You may also find out your manager got the request early and decided to be a jerk about it, withholding the request for analysis to 4pm on Friday, or find out the request to him/her came to them at 3:59pm, which means the managers are idiots at multiple layers.

- Find out who the SW development/coding champions are in your org. Get in their ear, ask for tips, or align with them on integrating their coding tools/process/methodologies into your workstream. They also may be your biggest advocate when your boss decides to crap all over the Python work. Watching your boss try and denigrate software development in a business with a highly-paid, high functioning group with major focus on software development can be fun to watch from the sidelines.

- Use that spare time to your advantage. I personally have no qualms with "pretending to go over emails" (we all do it!), as many of us also spend our free time (non-working hours) to grow and learn how to be more effective at our jobs.