4 ms·
While I agree with fast + time wasted = normal speed, in reality it is not the wasted time that plays the role. In most companies developers don't have a fixed
by hvasishth 17y ago
While I agree with fast + time wasted = normal speed, in reality it is not the wasted time that plays the role. In most companies developers don't have a fixed 8 hour job and most of them work more than 8 hours a day on a routine basis. I have seen managers who valued the total time spent working more than the actual work accomplished. So a developer who works about 8 hours a day was ranked below someone who spent 10-12 hours a day working even though it was the former who was accomplishing more tasks.
- oujheush 17y agoWhat about someone who works 10-12 hours and accomplishes the most tasks? I think you have to understand the corporate mindset without abandoning your black-belt coder-fu. Yes, you have to emphasize how difficult what you did was. You have to point out what you've accomplished. And tie yourself in directly with producing specific pieces of revenue wherever possible. But this will all be helped if you can program well. And if you want to play office politics, it'll be useful to have the ability to accomplish someone else's job in half the time, if you really can.
- motters 17y agoIt's often hard for a manager to judge how productive a developer is being. Often they're insufficiently qualified to judge the standard of the code being produced or whether one solution is more elegant/reusable than another, and instead are just using heuristics which work for other types of employment, such as estimating how much overall time and effort was put in.