Dynamic languages lack the perfect IDE intellisense that tells us the type of every variable. Thus it is necessary to use variable names that allow future readers of the code to unambiguously determine the type and contents of the variable.

Your phone buzzes with the server alert ring tone. Your product manager taps you on the shoulder: "Um, it looks like we're down." Not a single screen in your web app loads. You attempt to SSH into your server but connecting takes for...ev...er. Finally you connect to the shell and see the CPU pegged at 100%. You tail the access logs, but nothing looks fishy. Site traffic is normal. Frantic and desperate, you reboot the server. The server comes back up ... but immediately the CPU spikes back to 100%.

For the many years, the requirements of my job forced me to use Windows for working on parts of our code base. When working in Windows, I dearly missed the tools of a unix environment (ls, grep, the shell, etc). But over the years I've figured out a bunch of hacks that make using Windows a lot more tolerable. Here they are:

I am a startup guy and software engineer.  I currently am working on co-founding Grokky. Before that, I worked at HubSpot for the better part of a decade. At HubSpot I helped build a powerful suite of marketing software tools that served 10,000 plus paying customers.