3 ms·
> First, this guy went out of his way to lie and insert extra bugs in his code to make it appear like manual labor. Second, this guy is doing it all the time I
by BeetleB 9y ago
> First, this guy went out of his way to lie and insert extra bugs in his code to make it appear like manual labor. Second, this guy is doing it all the time
I don't see the difference. I've known people who intentionally work slowly or pretend to do manual labor when they've already got a process for automating it. They'll just goof around for a while and then run the automation.
Whether you're introducing bugs to fix yourself or pretending to work - the effect is the same.
Not as extreme in terms of time as this guy (more like doing a process that took 4 hours in 2 and pretending it took 4 hours).
Initially I felt it was unprofessional. I kind of still do. However, I also knew the management, and the behavior was consistent with the types of rewards management provided: The reward for this kind of increase in productivity was never financial, and was always "OK, now you can do even more work". One person's boost in productivity would raise the bar for the whole team - everyone felt punished. So as time went on, people would come up with process improvements and ensure the management did not know about them.
Why do I still feel it is unprofessional? Behaving like this is not why I became an engineer, where solving problems makes you regret you solve them. So I thought about it hard, and realized I should find a job that encourages and rewards improving productivity, and not uses it as an excuse to give more work.
- deleted 9y ago[deleted]
- wfunction 9y ago> I don't see the difference. Really now? Are you sure it's not a case of you not wanting to see the difference? > Whether you're introducing bugs to fix yourself or pretending to work - the effect is the same. Being at work and not working is quite a far cry from actively lying that you did things that you didn't do, or from inserting defects in your code so that they pay you to remove them. It's at least honest to screw around at work when your manager can observe that fact, and merely turn in the desired output on time. You could argue (rightly or wrongly) that the manager is supposed to be the one tracking your workload. But it's dishonest (and frankly outrageous) to actively lie about what you're doing so that your manager can't track your workload, or to insert defects so that the company -- unaware of your deliberate sabotage -- pays you to fix the "accidental" mistake. What kind of world do you live in where intentions and honesty don't matter, and only "effects" do? Frankly, I'm finding what I'm reading from you and others here so outrageous that I'm nearing a loss for more words. I literally cannot remember the last time (i.e. I don't think there was one) I was this disappointed at HN users and ashamed of even being among them. It's disgusting.
- naasking 9y ago> What kind of world do you live in where intentions and honesty don't matter, and only "effects" do? Probably the business world. If we momentarily put aside the intentional insertion of mistakes which takes the ethical considerations to a whole new level, we're still left with an interesting ethical question of whether automation of your own job requires you to inform your employer of how you're doing your job. That answer isn't so clear to me. You're hired to do a job, and you're doing it to the best of your ability. Do you consider that unethical?
- wfunction 9y ago> If we momentarily put aside the intentional insertion of mistakes which takes the ethical considerations to a whole new level, we're still left with an interesting ethical question of whether automation of your own job requires you to inform your employer of how you're doing your job. That answer isn't so clear to me. You're hired to do a job, and you're doing it to the best of your ability. Do you consider that unethical? I'm not going to "momentarily put that aside". The active lying and sabotage of this case are extremely material facts of the entire discussion. The alternate circumstances you're asking about form an entirely different question that is worthy of a separate post and discussion, and I'm not going to get derailed trying to change the subject and address it here.
- naasking 9y agoI imagine you're familiar with reasoned argument, similar to programming, where one starts with some generally agreed premises upon which one can build to ever more sophisticated conclusions. So again, do you have an opinion on the specific question I asked?
- wfunction 9y agoI really don't have an opinion on your hypothetical situation to present here. Nevertheless, you can still build your argument assuming one way or the other, if that's really what you're trying to do. People can question the assumptions if the need arises.
- hinkley 9y agoManagement almost always treat estimates as promises, and you get what you measure. If you automate and that reduces the best case time for a task, it might not improve the average case very much, and the worst case not at all. That means the difference between the usual case and the worst case gets worse, and you'd be a fool to invite that sort of criticism from the management team more than twice. Your smartest path is to do the task at or under the usual time and spend any remaining budget on improving the situation for next time. Only when you can draw down the worst case time (or frequency) should you set new expectations with the organization.