zub

I worked at a consulting place for ten years that was packed with a bunch of wise veterans who were mentors for me. They also paid poorly and had no benefits. A pivotal place for me in my career but I should have left a half decade earlier.

And I wanted to work there so badly that I jumped on their first offer. The classic.

Mhmm. I wrote a set of PowerShell scripts to do some basic deployment stuff a while back and I discovered...

- Timing issues with something as simple as "remove file," where the agreed upon Stack Overflow solution was to call it "a few more times until you didn't get an error."

- Broken implementations of recursive folder copy.

- Okay, we'll call upon "rm" and "rmdir" -- oh, PowerShell intercepts those and invokes the previously described buggy routines. (Eventually figured out that I needed to shell out completely.)

In the end I regretted writing these crummy house-of-cards PowerShell scripts.

> I can't see a way that new protocols are going to solve this, unless I'm missing something in how HTTP2 is going to be handled by the browser?

HTTP/2 server push. Your server can proactively deliver things like rollover state graphics knowing that the client will need them.