“I could do this better and faster if I used Python.”
“No.”
“Just a few libraries and some attempts, and I am sure it will not only save time, but smooth things out for later.”
“You need IT permission for even a single installation. Just let it go.”
It happens in almost every organization. Every now and then, you come across a task begging for a Python script. But NO. Either that rigid IT firewall blocks you, or a panicked manager assumes opening a terminal means you’re hacking the mainframe or leaking proprietary data. You are left staring at a high-end ThinkBook that has been locked down into a glorified web browser.
I cannot disclose the exact details, but the sheer volume of nested conditions and calculations became frustrating after a few iterations. I was agonizing over how easily it could be automated. I needed a workaround. The answer was right in front of me, and I had the perfect intern to help me out.
The task had calculations after calculations. Conditions under conditions. It was straightforward-complex. I realized I could replace Python with a single, local HTML file with built-in JavaScript. I could even give visuals to it; the interface wouldn’t be boring, and the task would feel like play.
I created the structure of the process, defined conditions, and added formulas. The intern was great; it followed my instructions and even pitched better visuals. The HTML file was ready within an hour or so. The ordeal was to rid it of bugs. A couple of hours of stress testing not only did that, but also introduced some exceptions that made the theory behind the file rock solid.
Three days of work wrapped up by the evening of day one. The next two days? Spent reading.