3 ms·
I get the exact opposite takeaway from: > 7. Your evaluative metrics have shifted Yes they've shifted, but the author implies that the success in the workforc
by mrkeen 7y ago
I get the exact opposite takeaway from:
> 7. Your evaluative metrics have shifted
Yes they've shifted, but the author implies that the success in the workforce needs more rigour than school. It's the complete opposite. Your stuff needs to work in school, and your prof will grade it accordingly. In the workforce, the person 'grading' your work will likely be a product owner who just wants to get the ticket closed. You will hear things like:
* "Let's do an MVP."
* "Let's focus on the happy path."
* "How hard can it be? You're just adding a button."
* "Let's close the ticket and we can create a new ticket if we need to."
You will not hear:
* "This is important, so get it right."
* "Your code was wrong. Let's discuss"
You'll often be stuck with code that you know is flawed, that you want to fix, but the organisation won't give you time to fix it until it's too late.
- kyralis 7y agoIf you don't hear "Your code was wrong. Let's discuss." as a junior engineer, you really should try to find a better team. Junior engineer code (hell, senior engineer code!) is quite frequently wrong, and a team with a good code review culture should absolutely be pointing that out and using it as a mentoring opportunity.
- jdsully 7y agoDepends 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 agoDo you mean you were forced to assemble your computer, part by part?
- jdsully 7y agoThey 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]
- pingyong 7y ago>You'll often be stuck with code that you know is flawed, that you want to fix, but the organisation won't give you time to fix it until it's too late. This has unfortunately been my experience as well. Although in some sense I can understand it now. When only ~10k normal people per year use something, the chances of one of them trying to kill it are apparently pretty low. Although I'm still convinced at some point it is going to happen.