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.
@Clent@lemmy.world
link
fedilink
English
-51Y

I literally said what evidence could be collected.

its hilarious how we spend our careers developing complex algorithms, reducing concepts into math and then delude ourselves into thinking the only algorithm that cannot be written is one that evaluates our own performance.

@Zeth0s@lemmy.world
link
fedilink
6
edit-2
1Y

Because it cannot be mathematically developed. KPIs as class of algorithm are linear dimensional reductions from a complex hyperspace to a small, arbitrary reference system built on non orthogonal axes, aimed to capture non periodic, non stationary phenomena (i.e. that unpredictably evolve over time).

Mathematically, performance kpi do not make much sense for most jobs, unless the job is so straightforward that the hyperspace has such low complexity that KPIs are meaningful representation. Not even a call center job has such mathematical characteristics…

As a task, AGI is mathematically much simpler task.

However performance kpis are the only thing many have to judge, as they lack technical and personal skills to do otherwise. It’s a tradeoff, but we must recognize that kpi are oversimplifications with extreme loss of information, many time useless

@Clent@lemmy.world
link
fedilink
English
-71Y

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.

@Zeth0s@lemmy.world
link
fedilink
7
edit-2
1Y

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

@Clent@lemmy.world
link
fedilink
English
-6
edit-2
1Y

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.

Create a post

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



  • 1 user online
  • 1 user / day
  • 1 user / week
  • 1 user / month
  • 1 user / 6 months
  • 1 subscriber
  • 1.21K Posts
  • 17.8K Comments
  • Modlog