januzis

4 ms·

1.
by januzis 7y ago
PrintNode, only had good experience with them, migrated from cloud print after I could not get some thermal printers working properly
2.
by januzis 7y ago
I would actually be OK with it, as long as I can objectively say that even though someone is slacking most of the time, he/she is very productive in short bursts, so the overall productivity is on par with the team average. The problem
3.
by januzis 7y ago
Even if you've tied team compensation to the results of the company, you still have to decide how it will be shared among the team members. So how do you go about compensation, bonuses, etc.? The same for everybody?
4.
by januzis 7y ago
This doesn’t solve the issue of individual team member performance evaluation, even if it improved the overall performance of the team, you still wouldn’t know who are under and over-performers.
5.
by januzis 7y ago
That’s the default, I guess, my main concern is that it’s very subjective.
6.
by januzis 7y ago
Yes, the extreme cases are easy to spot, but the nominal cases are not that minuscule, more like one developer being twice more productive than the other, which, I feel, should be recognized and rewarded accordingly.
7.
by januzis 7y ago
Measuring against estimates incentivizes over-estimating, especially if the team is small, and team members know roughly who will do what during the estimation process. Big complicated tasks also tend to be under-estimated, so they would be
8.
by januzis 7y ago
It seems to me there are two sides to engineer's performance: the ability and the productivity. Ability measures how complex tasks can an engineer solve and how well can he/she execute, and the productivity measures the actual amo
9.
by januzis 7y ago
They also discuss a case, where a user uninstalls Zoom, but does not remove the web server, remaining forever vulnerable, because the fix from Zoom will not reach them. That explains the Apple involvement.