From 17380280eccdab2e135d714ce72fc59e7f110f0d Mon Sep 17 00:00:00 2001 From: Thomas Date: Wed, 14 Jun 2023 20:30:01 +0100 Subject: [PATCH] blog: always the same warning signs --- ...3-06-14-link-always-the-same-warning-signs.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 src/content/blog/2023-06-14-link-always-the-same-warning-signs.md diff --git a/src/content/blog/2023-06-14-link-always-the-same-warning-signs.md b/src/content/blog/2023-06-14-link-always-the-same-warning-signs.md new file mode 100644 index 0000000..dbfd4ba --- /dev/null +++ b/src/content/blog/2023-06-14-link-always-the-same-warning-signs.md @@ -0,0 +1,16 @@ +--- +title: 'Link: Always the same warning signs' +date: 2023-06-14T19:29:00.425Z +slug: 2023-06-14-link-always-the-same-warning-signs +author: Thomas Wilson + +--- +I came across a link to [Always the Same Warning Signs](https://www.science.org/content/blog-post/always-same-warning-signs) (science.org) while browsing Hacker News. + +It goes over some of the warning signs around revolutionary (and lucrative) commercial science breakthroughs, like in pharmacology. Specifically, what if it seems too good to be true. + +The piece gives three warning signs which ring true in an engineering setting: + +1. Only one person can get this great stuff to work +2. Legitimate questions are met with stonewalling +3. Important data are missing or kept secret. \ No newline at end of file