Developer at Microsoft since 1999. I work on HoloLens. I work to get more people, especially women, into computer science. I play ice hockey, and have 3 kids. Check out my #EvilPlanToSaveTheWorld.
To be honest, I disagree with #2. It is not always in the best interest of your customer or your employer to do your absolute best every time. There are times when it is important, and times when it is not. When it is not, the price you pay is the opportunity cost of everything else you could have improved during the time you were polishing that unimportant detail. Of course, every dev thinks they make the right balance of speed vs. perfection, yet every dev does it differently. So it is best to get a second opinion from someone with a little different outlook than you, whenever you go far toward one or the other.
I am a product engineer and have helped build software from small startups, to manipulating hundreds of millions of data points. I write API's and make tools that make developers lives easier.
I could agree with that. There would be a balance. If in a given case doing your best prevents you completing something in a timely manner (#4 & #6) then you would have to use best judgement. I don't really touch on that as well as I should. But I believe this to be a valid point. But it also has to be taken into account with the others.
Developer at Microsoft since 1999. I work on HoloLens. I work to get more people, especially women, into computer science. I play ice hockey, and have 3 kids. Check out my #EvilPlanToSaveTheWorld.
I am a product engineer and have helped build software from small startups, to manipulating hundreds of millions of data points. I write API's and make tools that make developers lives easier.
Yea personal judgement is part of it too I think. As long as overall you have your best intentions in mind and strive to do your best. There will always be some variation in that depending on the person.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To be honest, I disagree with #2. It is not always in the best interest of your customer or your employer to do your absolute best every time. There are times when it is important, and times when it is not. When it is not, the price you pay is the opportunity cost of everything else you could have improved during the time you were polishing that unimportant detail. Of course, every dev thinks they make the right balance of speed vs. perfection, yet every dev does it differently. So it is best to get a second opinion from someone with a little different outlook than you, whenever you go far toward one or the other.
I could agree with that. There would be a balance. If in a given case doing your best prevents you completing something in a timely manner (#4 & #6) then you would have to use best judgement. I don't really touch on that as well as I should. But I believe this to be a valid point. But it also has to be taken into account with the others.
I suppose it could be a matter of how you define doing your best. Best possible code vs. applying yourself to the best of your abilities.
Yea personal judgement is part of it too I think. As long as overall you have your best intentions in mind and strive to do your best. There will always be some variation in that depending on the person.