|
|
|
|
|
by rekwah
4021 days ago
|
|
Are you actually slower than coworkers in an apples to apples comparison? Normally when I see things like this, it's usually comparing developers having a different definition of "complete". One will write the code, the unit tests, the e2e tests, and the documentation before saying the task it complete. The other, trumpets completion once the code is done. If you're actually slower, I'd start keeping track of where my time is going. Are you spending too long imagining all possible scenarios of a feature? Taking two hour lunches and coffee breaks every hour? Many hours spent in meetings? Wasting time building a "super generic" solution that isn't necessary? Spending three days writing tests for a feature that took 5 hours? If you don't feel like you're actually slow, it's just a problem of perception. I'd take some higher visibility features and crank them out, working the extra hours if necessary. I'd rather kick the stigma than deal with that anchor around my neck. Tread carefully with this strategy as it can be a double-edged sword and increase expectations and workload. |
|