The great thing about measuring developer productivity is that you can quickly identify the bad programmers. I want to tell you about the worst programmer I know, and why I fought to keep him in the team.
I am a human, who happened to be browsing lemmy when you answered, and work in ML and with a background in algorithms and HPC. It happened to be a lucky coincidence
That’s quite a lengthy response for the time between my post and your write up.
Not sure if you’re a bot or just used one to form your thoughts.
I am a human, who happened to be browsing lemmy when you answered, and work in ML and with a background in algorithms and HPC. It happened to be a lucky coincidence
Ok, so you’re not a software engineer. That’s good to know.
I did not say it has to be kpi on whatever other jargon you want to throw at it.
Software engineers slogan is: enough time and motivation .
Except when it comes to evaluating ourselves then it’s just not possible.
How can that be?
The bullshit excuses we tell ourselves is how we’ve ended up with ridiculous interview cycles with take home test.