|
|
|
|
|
|
by Apreche
1908 days ago
|
|
|
Our company does OKRs, which is also basically just measurable goal setting. I feel like if I was in a decision-making position in the company, OKRs would make more sense. If I have that kind of power and responsibility of deciding what the company is going to do, then I also have to decide what we want to achieve. But as a software engineer, I don't have any such responsibility. I make what I am told to make. My only goal is to do enough work well enough that the company thinks it is satisfactory. Beyond that I just want to do as little as possible in exchange for the most compensation possible. I also don't have any long term career goals other than to escape capitalism. Therefore when I'm asked to set goals, I find it exceedingly difficult. |
|
|
Initially I set all kinds of amazing OKRs for the tech team: decrease MTTF , MTTR; increase system performance, decrease bug reports, and a lot of other things that on an engineering paper would be great.
But then reality hits: next product feature has to be released NOW. Customer X is complaining because sales promised feature Y but we dont have it, Z provider decided to change from REST to SOAP and the reality is that your MVP code has rest tightly coupled. Oh and the engineers that knew about that code left when google/Facebook offered them 10x payment and free margaritas.