4 ms·
OP here. I think this is exactly right "The exact number is irrelevant, the fact that there is a number is relevant. That means the developer not only understoo
by mcenedella 6y ago
OP here. I think this is exactly right "The exact number is irrelevant, the fact that there is a number is relevant. That means the developer not only understood the business requirements but also measured the impact afterwards."
In follow-up interviews, the interviewer may dig into those results, and in reference checks, may try to confirm your achievements, so I do not think it's accurate to say it would be OK to use BS numbers.
But the overall sense that numbers are important, and send an important signal about a developer's work habits, patterns and practices, is true.
- marcinzm 6y agoA number can be corroborated by multiple people and have a logical chain to its creation and still be utter BS. Even scientific papers with their standards have massive issues with reproducibility. Look at the HN comments pointing out measurement methodology flaws when some corporate blog claims X% improvement. My point was more towards those engineers who are sticklers for accuracy and truth. It doesn't matter in this case. Mass delusion is fine as long as enough people believe it and there's a thin veneer of logic around it.
- wolco2 6y agoThat's not really the type of information offered during a reference check. Did x employees actions on this project result in a 27% increase in engagement? A lot of places only give yes this person worked here between those two dates. The person giving the reference would be in no position to answer in many cases. Legally a company doesn't want to get sued because they told another company the person didn't hit 27% when they might be able to prove they did.