Hacker News new | ask | show | jobs
by csbubbles 3591 days ago
I believe you can apply the "parameters" exactly same way to everything. They are just different.

The criteria could be:

* The time one would need to implement some particular task (build a website, application, algorithm, etc.) – you can measure it in minutes/days/months and compare.

* How much support the written piece of code would require over time – the number of bugs, the time required to fix those.

* How much effort is needed to extend the code – time spent on new features or changes built on top of that code.

* How clean the code/design is – the time another person would spend to understand the logic to get onboard to comfortably work with it after.

These are just off the top of my head, you can come up with much more, probably. I believe, everything is measurable. You just need to understand the specifics of the industry and decide what exactly to measure.

1 comments

Thanks for the reply. It was really illuminating and when I think about it more, it makes all the more sense. The number of bugs, the number of times another person who is working on your code asks you something etc.
Yep, exactly. You just need to compare everything against the same context.