3 ms·

Depends on where you work. My time at Microsoft was much closer to what you said I will not hear. There was a parable they used to use in training about how a

Depends on where you work. My time at Microsoft was much closer to what you said I will not hear. There was a parable they used to use in training about how a young developer found a flaw that would only happen “one in a million” times - not worth fixing. An older developer does the math on how many times the feature might run across the total userbase and found we’d be annoying millions of users. Microsoft did have a pseudo hazing ritual where you were forced to setup your own machine. I was surprised how many developers couldn’t do that. I was further surprised that ability to do so wasn’t correlated with skill. Being able to find help if you didn’t know was very highly correlated though.

SwiftyBug 7y ago
Do you mean you were forced to assemble your computer, part by part?
- jdsully 7y ago
  They were pre assembled from DELL or HP. You had to take everything out of the boxes hook up monitors, etc. The hard part was installing the OS, drivers, and getting your build environment going. One very excellent developer did not know what a driver was. It was that experience that forced me to reevaluate my biases. I had a few friends there in the late 80s/early 90s apparently at that time everyone watched with great anticipation to see if you could figure out the IRQ settings.
deleted 7y ago
[deleted]