- Mar 2024
-
third-bit.com third-bit.com
-
Safety Tip Always use === (triple equals) and !== when testing for equality and inequality in JavaScript.
Tags
Annotators
URL
-
- Jun 2023
-
stackoverflow.com stackoverflow.com
-
The old wisdom "mark it private unless you have a good reason not to" made sense in days when it was written, before open source dominated the developer library space and VCS/dependency mgmt. became hyper collaborative thanks to Github, Maven, etc. Back then there was also money to be made by constraining the way(s) in which a library could be utilized. I spent probably the first 8 or 9 years of my career strictly adhering to this "best practice". Today, I believe it to be bad advice. Sometimes there's a reasonable argument to mark a method private, or a class final but it's exceedingly rare, and even then it's probably not improving anything.
-
- May 2021
-
htmlpreview.github.io htmlpreview.github.io
-
Also, it is definitely NOT okay to recommend --force on forums, Q&A sites, or in emails to other users without first carefully explaining that --force means putting your repositories’ data at risk. I am especially bothered by people who suggest the flag when it clearly is NOT needed; they are needlessly putting other peoples' data at risk.
-
- Apr 2021
-
www.washingtonpost.com www.washingtonpost.com
-
Emails show Trump officials celebrate efforts to change CDC reports on coronavirus—The Washington Post. (n.d.). Retrieved April 12, 2021, from https://www.washingtonpost.com/health/2021/04/09/cdc-covid-political-interference/
Tags
- is:article
- government
- politics
- economy
- scientific practice
- data
- COVID-19
- public health
- political interference
- scientific advice
- response
- misinformation
- Centers for Disease Control and Prevention
- children
- schools
- CDC
- bad science
- Donald Trump
- Trump
- lang:en
- science
- scientific integrity
- USA
Annotators
URL
-
- Sep 2020
-
engineering.mixmax.com engineering.mixmax.com
-
There are two ways of handling this with Rollup, as described by the troubleshooting link from the warning. Unfortunately, both Rollup and React recommend the wrong one.
-
- Jun 2020
-
www.reddit.com www.reddit.com
-
BehSciMeta repost. (2020, May 22). "Great piece by James Heathers on how preprints have turned into publicity vehicles and researchers are being irresponsible in not responding to criticism" Reddit. https://www.reddit.com/r/BehSciMeta/comments/go6lik/great_piece_by_james_heathers_on_how_preprints/
-
- Apr 2015
-
wikipediawarning.com wikipediawarning.com
-
Do your research elsewhere.
Again, not bad advice, but for the wrong reasons.
Wikipedia is a good starting point and a great place to get a reasonably reliable overview. The real resource that Wikipedia provides is the Citations and References sections. These are the sources for the detail in the article and recommended further reading to get to the guts of what you're researching.
Other sources are always recommended. More reliable references are always a good thing and being able to get them cited in a Wikipedia article is a good way of giving extra validation given the process required to get something added to an article. It makes the Wikipedia article better and will cause the source article to appear higher in search results also.
-
Never link to Wikipedia from your website.
This is a fair thing to ask of people. The explanation is flawed and the advise is a little too firm but in general it is not bad.
If you are referencing a general topic linking to Wikipedia is fine.
If you are referencing a specific thing you should link to the source material rather than a general article. Chances are reasonably good that if your source material is well researched you could get it added to the sources in the Wikipedia article and maybe even update the general article too.
Wikipedia has rules around editing that ensure factually correct information makes it through. Editing can be challenging but if you adhere to these editing can be quite rewarding.
-