Hacker News Reader

Could you please clarify this one with examples:

> Perceiving things in terms of facts.

What is an example of a developer being unable to perceive a thing in terms of facts? Inability to accept the specs of a library’s api?

View on HN

More like a willingness to invent data about a thing as opposed to referencing data that is either immediately available or easily found. This often done out of convenience. That is probably fine in casual conversation, but many developers will just guess at performance, requirements, estimations, costs, dependency overhead, and so much more.

It’s a classic failure mode of the software engineer to decide to change something to be “faster,” before even checking to see if and when performance could become a problem.

I personally bucket this skill under napkin math and it is extremely good at guiding technical choices (YAGNI etc)

Reply on news.ycombinator.com