(edited) If you don't mind sharing, what is the bug? - My comment originally read as follows, 2 people downvoted it. >I work at Google and recently tried to

(edited) If you don't mind sharing, what is the bug? - My comment originally read as follows, 2 people downvoted it. >I work at Google and recently tried to file a bug about the calculator embedded in search. It was dastardly difficult to find how to file the ticket. It took me maybe an hour. A better system for filing tickets internally and for filing and triaging tickets from external users would be a tremendous asset for Google. I didn't work for Google directly but I did work via another company (Tech Mahindra) so I am saying this as somewhat of an outsider compared with you. You mention a bug about the calculator embedded in search: could you give me the details, and I can try to get it solved via my Google contacts. For context, in my personal experience as a user and engineer, the Google embedded calculator is the best product among all of Google's many offerings and works flawlessly for all inputs. I find it breathtaking. For example, here is how many feet times pounds you can turn 3000 Calories into: https://ibb.co/qJ0Qz0L https://ibb.co/qJ0Qz0L it worked on my first attempt. What does this mean? Well here's a foot-pound: https://ibb.co/N3WCxYV https://ibb.co/N3WCxYV If you weigh 180 pounds you're not climbing Mt. Everest twice (29,032′) without burning 3000 Calories. (Even at 100% efficiency). Try getting a result like that from any other calculator (though Wolfram Alpha gets close). What's the bug you tried to report? (What did you enter, what is the correct output and why is it correct, and what is the returned output and why is it incorrect?) I've never seen it make a mistake so far, and I use it heavily for all sorts of things. (Sometimes I force Google to show me the calculator by typing = at the end of my Google query.) Since the product works so well for me personally, I'd love to understand what problem you have with it.