<?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 Lucy Macartney on Medium]]></title>
        <description><![CDATA[Stories by Lucy Macartney on Medium]]></description>
        <link>https://medium.com/@macartney.lucy?source=rss-74c21c0a869a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8toBSwD5Xx5ZK3XZ</url>
            <title>Stories by Lucy Macartney on Medium</title>
            <link>https://medium.com/@macartney.lucy?source=rss-74c21c0a869a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:08:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@macartney.lucy/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[Gumption: A lesson from a postcard and a Toblerone]]></title>
            <link>https://medium.com/@macartney.lucy/gumption-a-lesson-from-a-postcard-and-a-toblerone-caf82b448964?source=rss-74c21c0a869a------2</link>
            <guid isPermaLink="false">https://medium.com/p/caf82b448964</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[bravery]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[university]]></category>
            <category><![CDATA[storytelling]]></category>
            <dc:creator><![CDATA[Lucy Macartney]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 14:09:24 GMT</pubDate>
            <atom:updated>2025-07-09T17:09:19.015Z</atom:updated>
            <content:encoded><![CDATA[<h3>Gumption: A lesson from my favourite teacher</h3><p>We all have teachers that we’ll always remember.</p><p>One of mine was Roger Webster, an older tenured professor who taught “The History of Mathematics” in my final year at university. It was the only class he still taught. He was adorably enthusiastic and charismatic, turning dry historical facts into vivid, captivating stories.</p><p>One day, he taught us about the Rosetta Stone. He told us, excitedly, about how its discovery had unlocked the secret of ancient Egyptian hieroglyphics. At the end of the class, he set us a challenge: the first student to go to the British Museum to see the Rosetta Stone and send him a postcard would win a Toblerone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Aj4wbmFGSmxWaZ0Pg4chKA.jpeg" /><figcaption>The Rosetta Stone</figcaption></figure><p>We were studying at the University of Sheffield and the British Museum was in London. It wasn’t exactly around the corner — a pricey two-hour train journey, or a long drive that would take most of the day.</p><p>By chance, I already had a trip to London planned that weekend. I adjusted my plans to make time to visit the British Museum, see the Rosetta Stone and send Roger a postcard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VqUq9MrI1dyQ-qYq5qgVBg.jpeg" /><figcaption>A picture of the Rosetta Stone from that day</figcaption></figure><p>In our next lecture, he was delighted to tell the class that a student had <em>already</em> sent a postcard from London. Everyone looked around, surprised. I felt myself going red, sinking into my seat, instantly regretting being so impulsive. I didn’t want to look like the teacher’s pet.</p><p>Roger called me up to the front of the lecture hall. He smiled as he handed me the Toblerone. I could feel every pair of eyes on me.</p><p>“This,” he said, pointing to the postcard, “is what I call <strong><em>gumption</em>”</strong>.<br>I’d never heard the word before, but I’ve never forgotten it since.</p><figure><img alt="A definition from the dictionary for gumption: shrewd or spirited initiative and resourcefulness." src="https://cdn-images-1.medium.com/max/1024/1*V_n0wFm45T5H9Rp1odkHLA.jpeg" /></figure><p>Roger went on to explain what he meant. Gumption meant going beyond what’s expected and not being afraid to put yourself out there. It was about caring enough to follow through and having the boldness to act on an idea.</p><p>Most people, he said, wait to be told what to do. Or they hold back out of fear of looking silly. But the people who go far are the ones who take initiative — who do things just because they’re worth doing, who make the effort to send a postcard. He was trying to inspire us to take risks, follow curiosity, and not wait for permission.</p><p>That moment stuck with me. Roger reframed something I was embarrassed about — the impulse to follow through, to make the extra effort — and turned it into a quality worth having.</p><p>Looking back, there have been times when I’ve shown real gumption. Quitting my job to travel South America. Moving to Colombia without a plan. Teaching myself to code when I wanted to change careers. Saying yes to projects before I felt ready and figuring it out as I went.</p><p>But somewhere along the way, I’ve lost that spark. I talk myself out of job applications before I even apply. I tell myself the market’s bad and that being in Colombia makes it harder. I have plenty of ideas but don’t act on them. I feel like I’ve been existing rather than living.</p><p>But I want that to change. I have plenty of ideas — now I need to act on them. I want to step back into showing gumption in my life. That might mean reaching out to companies that I love instead of waiting for the perfect job posting. Creating opportunities instead of waiting for one. Writing more online. Launching a digital product. Starting something on my own. Just like this article — turning an idea into action.</p><p><strong>So here’s Roger’s challenge, passed along to you: </strong>What’s the postcard that you’ve been meaning to send? What idea have you been thinking about but not acting on? What would it look like to show a little gumption in your own life? <strong>I’d love to hear from you in the comments ✍🏻</strong></p><p>After writing this article, I looked up Roger Webster and discovered that he passed away in 2023. This piece is a tribute to him and all the lessons he taught so many of us over the years. Rest in peace, Roger.</p><p>If there’s a teacher who inspired you, maybe now’s the time to reach out and tell them. They probably have no idea how much they meant to you.</p><p><em>I’m Lucy, a British web developer living in Colombia trying to build a different life. I write about life, tech, and whatever I’m learning along the way.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caf82b448964" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The hidden cost of coding with AI]]></title>
            <link>https://medium.com/@macartney.lucy/the-hidden-cost-of-coding-with-ai-d36102c71bf6?source=rss-74c21c0a869a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d36102c71bf6</guid>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[learn-to-code]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Lucy Macartney]]></dc:creator>
            <pubDate>Mon, 23 Jun 2025 16:19:18 GMT</pubDate>
            <atom:updated>2025-06-27T21:06:07.143Z</atom:updated>
            <content:encoded><![CDATA[<p>I was working on a tricky animation problem recently. Since animation isn’t something I work with often, I did what most of us do when we hit a wall: <strong>I asked AI for help.</strong></p><p>I wrote thoughtful prompts. I gave context and explained the problem. I kept refining my wording to try and steer it towards the solution I wanted.</p><p>But the more I prompted, the more tangled things became. Each fix broke something else. I wasn’t getting closer to the solution, I was going in circles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L72e6cJtjngVIkyLPfrAVw.jpeg" /></figure><p>That’s when I realised: <strong>I didn’t actually understand what I was trying to solve.</strong> And when that’s the case, AI usually makes things worse, not better.</p><h4><strong>Why struggling matters</strong></h4><p>I learnt to code before AI tools were popular, and I’m <em>so</em> grateful for that.</p><p>It meant sitting with the problem for hours, working things out bit by bit. No shortcuts. No quick answers. Just me, the code, and whatever I could find on Stack Overflow or Google 😅.</p><p>That kind of struggle teaches you how to think. You learn how to break problems into smaller steps. You start to understand what you’re doing, instead of pasting code and hoping it works. Over time, your skills compound. Each problem you solve makes the next one easier.</p><h4><strong>The comfort trap</strong></h4><p>Lately, I’ve been leaning on AI more. Maybe you have too. AI works well for familiar problems where you have a rough idea of the solution. It can save time and fill in gaps.</p><p>But it’s different when you don’t understand the problem. That’s when it gets tricky. You might end up copying code without understanding it. This feels like progress, but you’re not actually learning anything.</p><p>For simple issues, you might get away with it. But as things get more complex, AI can’t think for you. And by then, you’ve lost the habit of thinking for yourself.</p><p>That’s exactly where I found myself with this animation problem. I was so used to asking AI for help that I forgot one of the most basic problem-solving tools: working through it by hand.</p><h4>Going back to basics</h4><p>In the end, I didn’t solve my problem with AI. I stepped away from the screen.</p><p>I got out my A3 sketch pad and wrote things out by hand. I drew diagrams, made rough notes and mapped out each step of the logic numerically. I went back over animation fundamentals.</p><figure><img alt="An image of some of the diagrams I drew out on my A3 sketch pad. The image shows me mapping out how each petal animates in different phases of the animation." src="https://cdn-images-1.medium.com/max/1024/1*oyHW8098lf61R1sOaukLVA.jpeg" /><figcaption>Some of the diagrams I drew to help me solve the problem</figcaption></figure><p>Then, once I actually understood the problem, I started to code. I worked through it piece by piece. When it finally worked, I understood <em>why.</em></p><p>This process took much longer than expected. I was rusty at thinking through complex problems without AI — a wake up call that this muscle fades if you don’t use it.</p><h4><strong>The takeaway</strong></h4><p><strong>Don’t use AI to solve problems you don’t understand</strong>. If you can’t explain the solution in plain language, AI isn’t going to help you.</p><p>When you’re stuck and nothing’s working, pause. Write it down. Break it apart. Go back to basics. Draw diagrams. Remember how you learnt to code in the first place.</p><p>Because some problems aren’t promptable. And if you stop solving them yourself, you’ll forget how.</p><p><em>I’m Lucy, a British web developer living in Cali, Colombia. I write about tech and life. More coming soon 👀</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d36102c71bf6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>