<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Christian Skotte on Medium]]></title>
        <description><![CDATA[Stories by Christian Skotte on Medium]]></description>
        <link>https://medium.com/@Skotte?source=rss-19064712eb94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WeeDBS67zpAPRgpA_4xLsQ.jpeg</url>
            <title>Stories by Christian Skotte on Medium</title>
            <link>https://medium.com/@Skotte?source=rss-19064712eb94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:52:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Skotte/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Using Facts, Not Fact-Checking, To Fight Fake News]]></title>
            <link>https://medium.com/@Skotte/using-facts-not-fact-checking-to-fight-fake-news-49012f6bc0e9?source=rss-19064712eb94------2</link>
            <guid isPermaLink="false">https://medium.com/p/49012f6bc0e9</guid>
            <category><![CDATA[fake-news]]></category>
            <category><![CDATA[climate-change]]></category>
            <category><![CDATA[science-communication]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Christian Skotte]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 19:37:48 GMT</pubDate>
            <atom:updated>2018-01-12T19:37:48.377Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article is based on a talk I gave at the University of Missouri School of Journalism as part of a fellowship from the Donald W. Reynolds Journalism Institute.</em></p><p>I was recently on a bus where I encountered a woman of a type I hear about often but rarely see in real life. She was white, in her late 50s or so. She was using her smartphone to scroll through Twitter. She mostly followed “news” sources who I knew trafficked in dubious or outright false information.</p><p>But it was her behavior that interested me the most. She would click on an article, look at the headline, scroll through it faster than any human could actually read, and then share it. The amount of information that she consumed was minimal. But she was spreading information to everyone who followed her. This is the Typhoid Mary of fake news.</p><p>We know this happens. After the Las Vegas shooting in October, we saw fake news spreading on social media. <em>The shooter was Muslim. The shooter was a Nancy Pelosi donor. </em>Neither of those turned out to be true. But that didn’t stop the hoaxes from spreading.</p><p>This is not a new idea, of course. Mark Twain was famously quoted as saying that a lie can travel halfway around the world before the truth can put its shoes on. (He never said that. The quote first appeared in 1919, nine years after his death.) “Factoid,” a word that now means a curious piece of trivia was originally coined by Norman Mailer to mean a fake fact that was passed off as true. But social media, the internet, and our entire communications framework have sped up how fast these fake facts spread while diminishing the ability of traditional sources of information to correct the record.</p><p>We see it in my world of science journalism.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/0*wg2JPvLrI0zyCO7R." /></figure><p>Although most Americans now concede that Global Warming is happening, <a href="http://www.pewinternet.org/2016/10/04/public-views-on-climate-change-and-climate-scientists/">most don’t think it will be a problem in their lifetimes</a>. And according to <a href="http://www.pewforum.org/2013/12/30/publics-views-on-human-evolution/">Pew research</a>, 4 in 10 Americans believe that humans have existed in their present form since the beginning of time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*cvzwLeGlRyxV1WnU." /></figure><p>This science illiteracy is a problem for an economy that is increasingly based on technology. It’s bad for a democracy that depends on people being able to separate fact from fiction. And as someone who works in science media, it simply pisses me off.</p><p>So what can be done? At <em>Science Friday</em> we cover a lot of issues that are controversial in the general public but are actually settled science: Things like <a href="https://www.sciencefriday.com/articles/articleshow-will-climate-change-hurt-the-american-economy-depends-on-where-you-live-pc/">climate change</a>, <a href="https://www.sciencefriday.com/segments/genetically-modified-parasite-shows-promise-for-malaria-vaccine/">vaccines</a>, and <a href="https://www.sciencefriday.com/segments/scientists-develop-a-hornless-cow-through-gene-editing/">GMOs</a>. And we’ve had hundreds of experts over the years explaining these topics to our listeners. Similarly, there are outlets that produce well researched factual media that describe these issues. But they can’t compete with memes, clickbait-y articles that deny basic science, and social media posts that obfuscate legitimate science.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YxsHCjymrTcQyBT2QQSolg.png" /><figcaption>Screenshot from Twitter</figcaption></figure><p>Clearly we can’t continue to do things like we’ve always done them and expect different results.</p><p>That’s why we’re working on something that we hope will be a solution. And we stumbled onto it because our fans asked us for help.</p><p>Starting next week we will launch a series of resources that we’re calling <strong>Science Facts</strong>. These resources offer short, shareable facts about scientific issues that are controversial in the general public but are settled for scientists.</p><p>These resources are not for the science deniers themselves, however. Our listeners have been asking us for years to help them talk with their friends and family who don’t “believe” in science. Our fans understood that things like man-made climate change were real and they believed it was happening. But they wanted to know how to talk with their friends and family who don’t get it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gUh5d5V9yx_EUzsN." /><figcaption><a href="https://www.sciencefriday.com/articles/how-to-talk-about-climate-change-with-a-denier/">https://www.sciencefriday.com/articles/how-to-talk-about-climate-change-with-a-denier/</a></figcaption></figure><p>Over the years we’ve dabbled in ways to address this problem. In early 2017 we did a segment on “<a href="https://www.sciencefriday.com/articles/how-to-talk-about-climate-change-with-a-denier/">How To Talk To A Climate Change Denier</a>” and we summarized the experts’ findings as quote cards that our audience could share over social media. But they wanted more. They wanted actual <em>facts </em>to present. Science Friday is not an advocacy shop, and we don’t do commentary. But we do have 25 years worth of radio where people have talked about some of these issues.</p><p>So we decided to create some of these resources for our fans to help them have productive conversations. How do we help make the conversations productive?</p><p>We’re drawing on research that shows that <a href="https://www.americanpressinstitute.org/publications/reports/survey-research/trust-social-media/">friends and family are better at changing minds</a> than media institutions. And we also know that <a href="https://hbr.org/2015/02/why-debunking-myths-about-vaccines-hasnt-convinced-dubious-parents">repeating false claims</a> simply serves to reinforce them. From our research we found that the key to helping have these conversations is to:</p><ul><li>Make sure not to repeat any falsehoods, even to debunk them</li><li>Give people new information</li><li>Present the information multiple times in multiple formats</li></ul><p>We pitched the idea of creating these resources to the Reynolds Journalism Institute at the University of Missouri, and they thought it would be a good project. We worked with Mizzou journalism students to take the words of experts and turn them into social media-friendly content. Each of these resources is fact checked and accurate. But they’re also catchy, shareable, and designed to communicate a concept quickly.</p><p>So that’s what we’re working on. We’ll launch the first of these over social media on Tuesday, January 16. And we’ll be surveying our listeners to see what kinds of conversations these <strong>Science Facts</strong> spark.</p><p>I honestly don’t know if these facts will change the behavior of the fake news Typhoid Mary who I saw on the bus. But if she has a friend or family member who listens to Science Friday then maybe the next conversation they have about climate change will be productive and backed up by facts. If so, that’s good for the Earth, good for our democracy, and a good first step to combating fake news.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49012f6bc0e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Coming of Larkin:]]></title>
            <link>https://medium.com/@Skotte/the-coming-of-larkin-85f04b94294a?source=rss-19064712eb94------2</link>
            <guid isPermaLink="false">https://medium.com/p/85f04b94294a</guid>
            <category><![CDATA[pregnancy]]></category>
            <dc:creator><![CDATA[Christian Skotte]]></dc:creator>
            <pubDate>Sat, 22 Jul 2017 17:31:52 GMT</pubDate>
            <atom:updated>2017-07-26T03:46:04.811Z</atom:updated>
            <content:encoded><![CDATA[<p>Or We Fought the Medical Establishment and … Well … We Got a Baby</p><p>Larkin Irene Skotte came into the world at 1:15 a.m. on Tuesday, July 18. It was not an easy journey.</p><p>Molly’s water broke the evening of Sunday, July 16. She was trying to finish up one last work project before giving birth. We gathered up our “go bag,” called our friends who agreed to watch our dog Falco, and headed to the hospital.</p><p>Because Molly tested positive for <a href="http://americanpregnancy.org/pregnancy-complications/group-b-strep-infection/">GBS</a>, we knew we needed to get her antibiotics from the hospital. We assumed that because Molly wasn’t yet in active labor, we would see a doctor, get our antibiotics, and head home until Molly’s contractions were more active. This was our first mistaken assumption.</p><p>Molly planned on giving birth at the new <a href="http://www.nyp.org/lowermanhattan/clinical-services/obstetrics-and-gynecology/birth-center">birthing center</a>, an area within the labor and delivery unit at NY Presbyterian hospital which promises a more natural birthing experience, with intermittent fetal monitoring, lots of space for moving around, low warm lighting, private bath tubs, and nurses who are trained to let birth take its course. The birth center is designed for low-risk pregnancies, and we had to take special trainings and ensure Molly was very healthy in order to qualify to give birth there. We were given a list of reasons why a woman wouldn’t be allowed to have a baby in the birthing center, and we were confident that none of them applied to us.</p><p>We arrived at the hospital (after a truly zany cab ride … but that’s another story) around 10:00 pm on Sunday. We were directed to the labor triage area, a series of beds separated by curtains overrun with hospital smells, scary-looking machines, and people scurrying around. They hooked Molly up to a blood pressure monitor and to a fetal monitor. They took her temperature and drew her blood. It felt institutional and impersonal; not at all like the birthing experience we had envisioned. But again, we thought we would soon get some antibiotics and be sent on our way.</p><p>Unfortunately, Molly’s blood pressure came back high. The nurse didn’t tell us that it was a problem, and we were so excited and nervous that we didn’t think to ask. The nurse left and we were alone under the harsh fluorescent lights of the triage area. Eventually our midwife was called. She explained to us that Molly’s blood pressure was high enough for them to have concerns of <a href="http://www.mayoclinic.org/diseases-conditions/preeclampsia/home/ovc-20316140">preeclampsia</a>. That meant that not only would we be “risked out” of the birthing center, but she’d also need to be admitted right away.</p><p>We were moved to a room in the labor and delivery unit around midnight on Sunday night/Monday morning. It wasn’t as nice as the birthing center. But it was large and private. There was a couch for me to sleep and the staff brought me sheets and pillows. “We can make this work,” we thought. The nurses told us to get some rest and that the next midwife on duty would be in at 6:00 am. I slept for about an hour. Molly didn’t get any sleep at all.</p><p>The next morning our <a href="http://zenmommas.com/">amazing doula Aimee</a> arrived and Chris, Molly’s mother, continued her drive from Ohio. Molly was having irregular contractions. The midwife saw us and told us that she wanted us to get to a place where Molly was having contractions that lasted for a minute and that came every three minutes. I did my best to support Molly while she was having contractions and to keep her spirits up between contractions. Because of Molly’s blood pressure, Molly and the baby were being continuously monitored for blood pressure and heart rate. This meant that Molly was wired up to a series of computers and couldn’t move more than a couple feet in any direction. She felt like a caged beast.</p><p>Over the next few hours Molly experienced irregular contractions. Chris — who had initially feared the baby would be born before she got there — arrived at around 1:30 pm on Monday. We were content to let the birth take its time as long as both the mother and the baby were healthy. We saw no reason to introduce interventions that would speed up the birth. But as Molly’s blood pressure continued to rise — 170/120 was the highest I remember seeing — the medical staff became concerned, especially because Molly’s water broke 17 hours earlier, increasing the chances of a dangerous infection.</p><p>The midwife encouraged us to give Molly <a href="https://www.thebump.com/a/pitocin">pitocin</a>, a synthetic version of oxytocin, the hormone that stimulates labor. We were against this for a number of reasons: pitocin has been linked to some complications in labor, but it also meant that Molly would be tethered to yet another device (pitocin is delivered intravenously), and we were concerned about the cascading nature of interventions — once one intervention happens it’s easier for doctors to make the case for others.</p><p>We managed to convince the medical staff to delay pitocin while we tried other home remedies to speed up labor. But after a few hours of those, we decided to take the midwife’s advice and introduce pitocin. At 3:30 in the afternoon they added the IV. We were getting further and further from our vision of a natural birth. But at that point we really just wanted to have our baby.</p><p>With the pitocin dripping through Molly’s body, the contractions started coming more frequently, but they were still irregular. Around 7:00 the midwife did a cervical exam and found that Molly was seven centimeters dilated. She still had a ways to go (10 centimeters is considered fully dilated), but she was getting closer.</p><p>Finally around 10:00 Molly was fully dilated and the contractions were regular enough for Molly to start pushing. Molly and I assumed that it’d take just a few pushes to get baby out. We were wrong on this score as well.</p><p>By the time midnight rolled around, Molly was exhausted. She had been pushing for two hours, and hadn’t had any sleep for over 40 hours. She tried at least four different birthing positions. But none of them seemed to work well. And with each new position, the pressure on Molly’s body shifted, causing her more pain. Morale was starting to slip, and we wondered if we would ever see our daughter.</p><p>Finally, the midwife let us know that she was going to have to bring in the attending physician. Molly had been laboring for too long and her blood pressure was too high.</p><p>Dr. Jew (yes that’s his real name) arrived about 20 minutes later. The midwife briefed him on the situation. He explained to us that we had two options: he could use the vacuum to suck the baby out while Molly pushed, or we could have a C-section. Molly was ready to just have the C-section. We were so exhausted and had traveled so far from our initial birth plan that it seemed like the logical next step. But then Molly had a contraction and Dr. Jew was encouraged by how close the baby was to being born. He convinced us to have one more push with the vacuum. And then, miraculously, baby Larkin was born!</p><p>The mood in the room changed completely. I was bawling my eyes out. Chris and Aimee were shouting and laughing. Molly was jubilant (or as jubilant as someone who had just endured 30 hours of labor can be). Larkin was quickly checked by a pediatrician and then brought back to Molly for skin-on-skin contact. We had a couple of hours in the delivery room with Larkin before we had to move into the postpartum unit. We really thought Molly’s struggles were over and that she’d be able to get some rest. Again, how wrong we were.</p><p>Molly was wheeled to a shared post-partum room. Almost immediately after she was put in her bed she began writhing in pain. It was indescribably difficult to watch my beautiful, strong wife feeling so miserable after what she had just experienced. I managed to get the nurses to give her some narcotic pain pills but there was some confusion in the order and it took precious minutes for them to make their way to Molly. In the meantime, she was straining against herself, trying to get comfortable in any way possible. Finally the midwife arrived and explained that Molly had just had a difficult birth and that all of the endorphins were wearing off so she was now feeling all of the pain that her mind had been blocking.</p><p>It seemed a reasonable explanation. And once Molly had the pain pills and started listening to a podcast, she did seem more relaxed.</p><p>Chris and I took the opportunity to head back to Molly’s and my apartment in Brooklyn to try and get some rest.</p><p>An hour later, Chris got a text from Molly’s phone. Molly had handed the phone off to the midwife as Molly was being wheeled into emergency surgery. Chris called the midwife and found out that Molly was suffering from internal bleeding which manifested as a vaginal hematoma.</p><p>Apparently, two hours after we left Molly yelled into the hallway that she was in pain. The head of the labor and delivery unit and the head of the midwife program were passing nearby. They examined her and were dismayed by the swelling in her vulva. They gathered a team and raced her into the operating theatre.</p><p>Chris and I had only slept about an hour each when we got word that Molly was heading into surgery. We quickly dressed, called a cab, and headed back to the hospital (working our way against rush hour traffic on the Brooklyn Bridge). That car ride was the single scariest moment of my life.</p><p>We got to the hospital and — after a few minutes asking around — found out that Molly was on the sixth floor. We took the elevators up and waited in the waiting room. Chris sat while I paced. The midwife arrived and explained that Molly had made it out of surgery. They repaired the bleeding and drained the hematoma. She was going to be okay! Chris and I both broke down with tears of joy. The midwife led me to the nursery to see Larkin and took Chris to the recovery room to see Molly.</p><p>After checking on Larkin, I made my way to the recovery room. Molly was a bit doped up — she asked at least three times where her phone was — but she was smiling and doing fine. She required two transfusions of blood and the doctor said he wished he could’ve taken a picture of her swelling to show his students <em>just how bad it can get</em>.</p><p>Describing it as an “emotional roller coaster” doesn’t do justice to what we experienced over those few days. We felt higher than the stars when we first met Larkin. We grieved for what could have been when we weren’t able to have the birth we wanted. And there’s no word for the terror I felt when I thought I might lose Molly.</p><p>But in the end, Molly is doing fine. And we’re blessed with li’l baby Larkin, the most perfect baby the world has ever seen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMRlt6VgRoOIsnUTlkUn4g.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85f04b94294a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>