I don't know. I just can't get excited about numbers.

I'm a builder. I'm excited about things working from start to finish.

Id be excited about numbers if it was from 0 users to 100 users.

Not 10000 to 10500.

That's not an engineers job, is it?

Context plz

@MammaNeedHummus his OnlyFans

@MammaNeedHummus performance anxiety.

@Demolishun thank you for making my evening

lol. that's a pretty awesome interpretation.

So to provide some context. I was in a meeting where people were demoing. But in our company demo is almost never a demo of the feature we've done. It's always "how much we moved the metrics by". and then everyone will be "oh I'm so excited by that"

I just can't. can't get excited for it. Id get excited seeing how a feature does something quicker, easier. How much faster etc. Not by how numbers like how much more/less traffic it caused.

It seems to be. somebody else's job.

@iceb

It is someone else's job.

KPIs are important, and invaluable when well defined, but they often require good multidisciplinar people.

For plain developers, they are not your concern, and as you aptly said, should focus on making things work within the boundaries you accepted.

@CoreFusionX plus a lot of devs get into this job because they can directly see the effect their code has on people (help / delight them by automating the mundane or excite them with a game)

I get it. It's repetetive - you're fine with just knowing KPIs are up and you don't need to see a detailed monthly report. I feel the same way.

But I think you'd miss these numbers if you NEVER saw them. I was once in a team where all our demos just showed theoretical improvements to load times etc but we couldn't measure if they actually moved the needle, and that was unnerving.