90% of programming I have seen after a decade plus of doing it full time is minor changes being made to code that was already made by someone. Likely not documented. Likely already changed in a dozen little ways. Math isn’t the problem. Understanding what the guy who wrote it is often the problem.

Oh and you can’t ask them because they likely don’t work here anymore.

Being a programmer is more like being a detective than anything else unless you work for a small company.

I am saddened to see that this thread had no mention of how many horses it takes to run a router. What do y’all think? Would one be enough? It would need to work in shifts to keep up time at 100%. Maybe 3 to be safe?

Sir Chad carries a twelve pounder hand cannon, and when he ignites the powder the ball sails true into the main deck of the pirate, but the recoil capsizes his vessel.

Stupid sexy Flanders.

That is awesome. And maybe this is a dumb question but… Would that actually make the report of the gun louder?

It’s code, but without automated tests, comments, style rules, and often stored in binary files making change management a nightmare.

It’s trying to paint but you can only use your fingers and also one of the other devs ate all the red.

An amazing story, and just downright perplexing. It is a shame you never found out what on earth was going on in the CTOs head. I would love to understand the thought process (or lack thereof) that went into that.

The future is already here – it's just not evenly distributed.

The Economist, December 4, 2003, William Gibson