I feel it misses a reliable take-down of the systems people. Recipe: (1) ask the person if they have evaluated some framework which would take months to evaluate; (2) suggest that their hard work reinvents the wheel; (3) step back and enjoy a smug victory. On the odd occasion that they have evaluated the framework you named, you can simply try again a few minutes later with a different framework. If you are challenge…
Nice comment, but you should rewrite it in Rust.
How to Criticize Computer Scientists (2001)
31–40 of 104 posts
Re: How to Criticize Computer Scientists (2001)
#32Re: How to Criticize Computer Scientists (2001)
#33"Oh look, another dev surprise."
"They improved the code... To run in O(2^n) time."
"I'm sure it worked in dev."
"I can't believe it passed QA!"
Re: How to Criticize Computer Scientists (2001)
#34Cosmology: Use the word "cosmology" interchangeably with "astronomy."
Simulations: "Did you include dust?" If they say yes then ask about magnetic fields. Either way, claim that they tuned their physical hyperparameters to achieve their results.
Observations: "Did you follow up with ?" Pick one that's especially competitive to request observations, such as Hubble or SOFIA or ALMA, so that if the answer is no they'll feel extra bad about their rejected Hubble/SOFIA/ALMA observing proposal.
Re: How to Criticize Computer Scientists (2001)
#35Criticism should not be insulting. The primary title of this document is a thinly veiled attempt of shrouding the author's true intent. It's clear from their final words on the topic that they mean to insult, not criticize.
> How To Criticize Computer Scientists > or > Avoiding Ineffective Deprecation And > Making Insults More Pointed
Am I missing something? Isn't your failure to read the full title a result of your desire to insult the author, rather than to criticize them? Wasn't this done already at Xerox PARC?
Re: How to Criticize Computer Scientists (2001)
#36> In fact, this is merely an extension of a ploy used by children on a playground: "Oh yeah? I could have done that if I wanted to." Or by adult professionals on Hacker News.
Re: How to Criticize Computer Scientists (2001)
#37This article had the most volunteer translations I've ever seen (26). I wonder why.
Google Translate produces a better translation (which is of course still awful), but I have a feeling that the one in question was made by an earlier version of Google Translate as well.
Re: How to Criticize Computer Scientists (2001)
#38> Like mathematicians, theorists in Computer Science take the greatest pride in knowing and using the most sophisticated mathematics to solve problems. This reminds me of some papers that got their proofs wrong by applying some fancy theorems. The fact that their results are correct clearly suggests that those theorems were added as a second thought.
If you browse r/MachineLearning, you will see many people complaining about unnecessarily convoluted mathematics that are literally there to appease reviewers and don't actually say anything useful.
Re: How to Criticize Computer Scientists (2001)
#39I would actually love the non-joke version of this article about how to constructively criticize, especially when you have to do it via text.
Your meaning is perfectly clear (and I’d also like that article), but for some reason 25% of my brain is stuck reading “text” as “text message” and imagining someone banging out a critiquing response in T9 mode on some old Nokia phone.
LOL UR PPR SUX JK ;)
Re: How to Criticize Computer Scientists (2001)
#40I would actually love the non-joke version of this article about how to constructively criticize, especially when you have to do it via text.
https://www.brainpickings.org/2014/03/28/daniel-dennett-rapo...