5
sethwhite
310d

I find goals for developers to be pure busy work and almost impossible set meaningful ones.

You can't set ticket based goals, because one ticket may take a week or an hour. You can't really set learning goals, because how do you measure 'learning Svelte'? And if that was your goal, what'd be the point of the outcome?

You can set goals like, ensure all tickets have at least one unit test... but then you get tickets that need to get out yesterday and you get people knocking on your door while you're trying to create meaningful tests.

But we often have a meeting to teach everyone how to set goals, then we have to sit and invent goals that satisfy someone in the org, then twist our usual daily work into some BS about how we're working towards the goals in 1:1s and then the whole thing is forgotten by H2, if not sooner. Just to be resurrected in Jan/Feb of next year.

Comments
  • 1
    Like: "learn C++"

    What the fuck does that even mean? You can learn modern C++, but hire on and be stuck in pre C++11 code. You can go template heavy and find your employer doesn't use them heavily, or actively discourages them. Good luck on embedded where the version is usually old. The worst are people who take a 30 day course and think they "know" C++. No, you don't. There is too much shit there.
  • 1
    Learning goals == certificates
Add Comment