8 ms·
I agree with this, which is why I found it a good moment to ask a bit more about the discipline itself with regards to this thread. I'm suspecting that more peo
by melvinroest 6y ago
I agree with this, which is why I found it a good moment to ask a bit more about the discipline itself with regards to this thread. I'm suspecting that more people disagree than they are commenting here as I'm seeing some downvotes. Unfortunately, they're not participating in the discussion as it would be quite interesting to tease out more why this is or isn't a useful skill. Apparently, opinions on the topic are a bit polarized.
Personally, another thing I find it useful for is for salary negotiations when you're talking face to face. Simply being able to guestimate a company's revenue, amount of clients, cost and their mindset gives you an idea if a low ball or high ball offer is due to mindset or due to finances.
I find in general that estimations of these types are amazingly good for when you really only have a few seconds, or to warrant further inspection. Like you said, if something is orders of magnitude away, then you already know the answer.
- proverbialbunny 6y agoHow can you see downvotes? I haven't gotten any and that's all I can see. Taking a stab in the dark here but it might be because YC is mostly software engineers and these kinds of problems rarely fit into the domain. It's a useful skill set, absolutely, but isn't something taught in computer science. On the data science side this has to be used all the time for most problems, but there are not many data scientists or other kinds of analysts on YC, so the kinds who use these tools are more than likely not going to be represented.
- melvinroest 6y agoYou see -1 points, and so on. At the moment it's slightly more upvoted, I wish I could actually see all upvotes and downvotes as it'd tell me how controversial my comment is.