<?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 Kevin on Medium]]></title>
        <description><![CDATA[Stories by Kevin on Medium]]></description>
        <link>https://medium.com/@Just.Photos?source=rss-73cfa63c0a5d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Kevin on Medium</title>
            <link>https://medium.com/@Just.Photos?source=rss-73cfa63c0a5d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:34:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Just.Photos/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[How AI Can Help Software Technical Writers Work Faster Without Sacrificing Quality]]></title>
            <link>https://medium.com/@Just.Photos/how-ai-can-help-software-technical-writers-work-faster-without-sacrificing-quality-654f5ce9f7e7?source=rss-73cfa63c0a5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/654f5ce9f7e7</guid>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Thu, 13 Aug 2026 21:09:07 GMT</pubDate>
            <atom:updated>2026-08-13T21:09:07.694Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4BKMDPJQFzqlscgh9IoWxQ.jpeg" /></figure><p>A practical, plain-English guide for documentation teams that are curious about AI but not quite sure where to start.</p><p>If you write software documentation for a living, this probably sounds familiar: everyone wants clear, accurate, up-to-date content, but the product keeps moving. New features appear. Interfaces change. APIs evolve. Support teams uncover fresh user pain points. And the people who know the answers are often too busy building the thing to stop and explain it.</p><p>AI will not magically fix all of that. It will not understand your product better than your engineers, replace your judgement, or guarantee that every sentence is correct. But used well, it can take a lot of the repetitive, first-pass work off your plate. That gives technical writers more time for the work that really matters: understanding users, asking better questions, checking the details, shaping the information, and making sure the final content actually helps someone get something done.</p><h3>First, what do we mean by AI?</h3><p>In simple terms, AI tools can analyze, summarize, generate, classify, or reshape text and other information. Some tools can create a first draft from a prompt. Some can suggest clearer wording. Some can help you find relevant information buried in documents, tickets, chats, or code repositories. Others can explain code, create examples, or automate small steps in your workflow.</p><p>The key point is this: AI is not one magic button. It is more like a collection of helpful assistants. Each one can speed up a specific part of the documentation process, but you still decide what is accurate, useful, safe, and appropriate for your audience.</p><h3>Where AI helps most in a technical writing workflow</h3><h3>1. Turning raw information into a workable outline</h3><p>Documentation projects rarely begin with a neat brief. More often, they start with a pile of product requirements, Jira tickets, pull requests, design notes, meeting summaries, screenshots, and quick explanations from engineers. AI can help turn that pile into something you can actually work with: a proposed structure, a list of likely topics, and a set of questions that still need answering.</p><p>That does not mean asking AI to invent the documentation for you. It means asking it to organize what you already have. For example, you could give an AI tool release notes and acceptance criteria, then ask it to suggest an outline for administrators, developers, and end users. Even if the outline is not perfect, it gives you a faster starting point and helps you spot gaps early.</p><h3>2. Creating first drafts from trusted source material</h3><p>Let’s be honest: the blank page is often the hardest part. AI can help you get past it by producing a rough first draft from trusted source material. That might be a procedure, a concept topic, an API description, an FAQ, or a release note. You still need to review and reshape it, but you are no longer starting from nothing.</p><p>The time saving comes from skipping the first blank-page struggle, not from skipping review. A sensible workflow might be: give the AI tool a specification, user story, and style guide; ask for a draft; check every technical claim against the source; test the steps in the product; then edit for clarity, tone, and audience needs.</p><h3>3. Rewriting for clarity and plain language</h3><p>A lot of software documentation starts out sounding like it was written by experts for other experts. That is understandable, but it can be hard on new users. AI writing assistants can help simplify dense explanations, shorten long sentences, remove ambiguity, and turn overloaded paragraphs into clearer steps.</p><p>The trick is to be specific. Instead of saying “make this better”, try something like: “Rewrite this procedure for a first-time administrator. Use active voice, keep the steps short, preserve product names exactly, and do not add any new information.” You are much more likely to get a useful result when you give the tool clear boundaries.</p><h3>4. Maintaining consistency across large documentation sets</h3><p>Consistency is one of those things readers only notice when it goes wrong. One page says “sign in”, another says “log in”. One guide talks about “workspace owners”, another says “account administrators”. AI-powered style and terminology tools can catch these differences early and suggest standard wording.</p><p>This can make review much smoother. Instead of waiting until the final pass to find every inconsistency, writers can run checks as they draft. That means fewer surprises, less rework, and a cleaner handoff to editors and subject matter experts.</p><h3>5. Explaining code and APIs more quickly</h3><p>For software technical writers, code-aware AI tools can be a real time saver. They can summarize what a function appears to do, explain a configuration file, draft API descriptions from an OpenAPI specification, or compare code comments with published documentation. Used carefully, this can speed up developer docs, SDK guides, and internal engineering content.</p><p>But this is also an area where you need to be cautious. AI-generated code explanations can sound confident even when they are missing something important. Treat them as a useful starting point, not the final answer. Check them against the source code, tests, working examples, and, where needed, a knowledgeable engineer.</p><h3>6. Repurposing content for different audiences</h3><p>One feature can create a surprising amount of documentation work: release notes, user guide updates, admin procedures, developer references, support briefings, FAQs, and more. AI can help turn one approved source into several audience-specific versions, which saves time and keeps the message consistent.</p><p>Of course, each version still needs a writer’s judgement. Developers need precision and examples. Support teams need symptoms, causes, and fixes. End users usually want the shortest path to success. AI can create variations, but the technical writer decides what each audience actually needs.</p><h3>Common AI tools and how technical writers can use them</h3><p>· <strong>General-purpose AI assistants:</strong> useful for brainstorming outlines, drafting from source notes, simplifying explanations, creating examples, and generating review checklists.</p><p>· <strong>AI writing and editing tools:</strong> useful for grammar, tone, readability, sentence structure, inclusive language, and style guide alignment.</p><p>· <strong>Documentation platforms with AI features:</strong> useful for knowledge base articles, topic reuse, search improvement, content recommendations, and publishing workflows.</p><p>· <strong>Code assistants:</strong> useful for explaining code, drafting API references, creating example snippets, and comparing documentation with implementation.</p><p>· <strong>Search and knowledge retrieval tools:</strong> useful for finding relevant source material across repositories, tickets, conversations, and existing documentation.</p><p>· <strong>Automation tools:</strong> useful for triggering draft updates from product changes, routing content for review, creating summaries after meetings, and tracking documentation tasks.</p><h3>A practical AI-assisted documentation workflow</h3><p>1. <strong>Collect trusted inputs.</strong> Gather requirements, tickets, designs, source code, meeting notes, and existing documentation.</p><p>2. <strong>Ask AI to summarize and identify gaps.</strong> Use AI to produce a short briefing and a list of unanswered questions.</p><p>3. <strong>Create an outline.</strong> Ask for a structure based on audience, task, and content type.</p><p>4. <strong>Generate a first draft.</strong> Use only approved source material and instruct the tool not to invent missing details.</p><p>5. <strong>Validate the technical content.</strong> Test procedures, verify code samples, and confirm assumptions with subject matter experts.</p><p>6. <strong>Edit for users.</strong> Improve flow, remove ambiguity, simplify language, and align with the style guide.</p><p>7. <strong>Run consistency checks.</strong> Use AI-assisted tools to check terminology, tone, formatting, and completeness.</p><p>8. <strong>Publish and monitor.</strong> Use analytics, support trends, and user feedback to identify where documentation needs improvement.</p><h3>Prompt examples technical writers can try</h3><p>Prompts work best when they give the AI tool context, a task, constraints, and a clear output format. Here are a few examples you can adapt to your own documentation work.</p><h3>Outline prompt</h3><p><em>“Act as a software technical writer. Using the source notes below, create a documentation outline for a new feature. Include sections for overview, prerequisites, step-by-step procedure, configuration options, troubleshooting, and open questions. Do not add details that are not supported by the source notes.”</em></p><h3>First-draft prompt</h3><p><em>“Turn the following product requirements and acceptance criteria into a first draft of a user guide topic. Write for a first-time user. Use clear headings, short paragraphs, and numbered steps where appropriate. Mark any assumptions or missing information in a separate ‘Questions for review’ section.”</em></p><h3>Plain-language rewrite prompt</h3><p><em>“Rewrite the following technical explanation for a non-expert user. Keep the meaning accurate, use active voice, avoid unnecessary jargon, and preserve all product names, command names, and parameter names exactly as written.”</em></p><h3>SME review prompt</h3><p><em>“Review this draft as a subject matter expert. Identify any claims that need verification, any missing technical details, any steps that may not work as written, and any terms that should be checked against the product terminology list. Do not rewrite the whole document; focus on review comments.”</em></p><h3>Consistency-check prompt</h3><p><em>“Check the following documentation draft for consistency. Look for inconsistent terminology, mixed spelling variants, inconsistent button or menu names, shifts in tone, and repeated information. Return your findings as a table with three columns: issue, location, and suggested fix.”</em></p><h3>Audience-adaptation prompt</h3><p><em>“Using the approved feature summary below, create three short versions of this content: one for end users, one for administrators, and one for support agents. Keep the facts consistent, but adjust the level of detail, examples, and emphasis for each audience.”</em></p><h3>How to protect quality while moving faster</h3><p>The biggest mistake is treating AI speed as a replacement for documentation discipline. It is not. You still need trusted sources, human review, tested procedures, clear terminology, and sensible rules about confidential information. If your organization requires transparency around AI-assisted content, build that into the process too.</p><p>A useful rule of thumb is this: let AI speed up low-risk transformation work, but keep humans in charge of high-risk judgement calls. Summarizing notes, suggesting outlines, and rephrasing paragraphs are good AI tasks. Approving technical claims, deciding what users need, publishing security-sensitive instructions, and signing off final content should stay with people.</p><h3>What this means for the technical writer’s role</h3><p>AI does not make software technical writers less important. If anything, it puts more focus on the skills that make good writers valuable: judgement, curiosity, structure, clarity, and empathy for the user. The writer becomes less of a manual transcriber and more of a strategist, editor, information architect, user advocate, and quality gatekeeper.</p><p>In short, AI can help writers spend less time wrestling with the mechanics of production and more time doing the work that makes documentation genuinely useful.</p><h3>Getting started without overwhelming the team</h3><p>If your team is new to AI, start small. Pick one repeatable, low-risk task, such as turning release notes into a draft changelog or rewriting an internal procedure for clarity. Decide what source material you will use, what prompt you will try, how the draft will be reviewed, and how you will judge whether the experiment worked.</p><p>Once people are comfortable, you can expand gradually. Build a small library of prompts that work. Share examples of good and bad AI output. Agree how to handle confidential data. Add terminology checks. Connect AI tools to the places where documentation work already happens. The aim is not to chase every shiny new tool. It is to build a repeatable workflow that helps writers produce trustworthy content faster.</p><h3>Conclusion: AI is a force multiplier, not a replacement</h3><p>Software technical writing has always needed a mix of precision, empathy, structure, and curiosity. AI does not change that. What it changes is how much time writers need to spend on the first pass, the repetitive pass, and the consistency pass.</p><p>Used well, AI can help technical writers get from raw information to useful documentation more quickly. It can shorten timescales, reduce friction, and improve consistency. But the quality still comes from the writer’s judgement. The future of technical writing is not AI instead of writers. It is skilled writers using AI thoughtfully to create clearer, more reliable documentation at the pace modern software demands.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=654f5ce9f7e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Battle over Atlantis]]></title>
            <link>https://medium.com/@Just.Photos/battle-over-atlantis-5b1750fc7133?source=rss-73cfa63c0a5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b1750fc7133</guid>
            <category><![CDATA[fantasy]]></category>
            <category><![CDATA[atlantis]]></category>
            <category><![CDATA[scifi]]></category>
            <category><![CDATA[adventure]]></category>
            <category><![CDATA[steampunk]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Tue, 19 Nov 2024 22:29:32 GMT</pubDate>
            <atom:updated>2024-11-19T22:29:32.773Z</atom:updated>
            <content:encoded><![CDATA[<p>In the expansive azure sky, an airship of the Atlantean Sky Navy cut through the clouds, its sleek, metallic hull shimmering under the sun’s rays. This was the flagship of the fleet, the Dauntless, a majestic sight, blending the advanced technology that was trademark of the city state of Atlantis combined with the artistic design that lifted it from a simple ship of war to a thing of beauty. The ship floated serenely on the warm air currents as it patrolled the skies above Atlantis. The crew, a mix of seasoned veterans and eager novices, felt a surge of pride as they navigated their vessel through the sky. They knew they were part of something greater, something that represented the pinnacle of their civilization’s achievements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vw9MUW92V6dQ4trTVfcJzA.jpeg" /></figure><p>The serene atmosphere was suddenly shattered by the distant roar of engines. The crew quickly realized that danger lurked just beyond the cloud bank behind them. Captain Al-hain Lorcha sat in the control room of the ship, the tension from the command crew was palpable. Reports streamed in from all sections of the ship, each one more alarming than the last. The ship was about to come under attack, and it was not just any foe; it was the Southern Coalition, a confederacy of nations who had long resented the power and wealth of the fabled city of Atlantis.</p><p>From his vantage point, the captain could see the first wave of enemy vessels, forming dark silhouettes against the vibrant sky, emerging like ominous shadows from the cloud bank where they had been lying in wait for the Dauntless. They were smaller, more agile fighters, designed for speed and surprise. Across the ship, the crew sprang into action, a whirlwind of movement and urgency, as they prepared the defences. Lorcha felt a mix of anxiety and determination wash over him. He knew they were the best crew in the fleet and that they had trained for moments like this, but nothing could truly prepare them for the chaos that would soon unfold.</p><p>As the enemy ships closed in, the commander’s voice was steady yet urgent, rallying the crew. “Battle stations! Prepare to engage!” His words echoed across the ship, igniting a fire in the hearts of the crew. Glancing around at the bridge crew, Lorcha noted that their faces were a mix of fear and resolve. United by a single purpose, a shared understanding that they must protect their home at all costs.</p><p>The first volley of fire erupted from the enemy ships, bright streaks of energy piercing the air. The crew watched in horror as the salvo struck the airship, the impact reverberating through the hull. Alarms blared, and the ship shuddered, but the pilot held position. The gunners returned fire, and the sky became a flaming battleground, filled with flashes of light accompanied by the roar of weaponry. It was a dance of destruction, a chaotic spectacle that felt to the crew both surreal and terrifying.</p><p>In that moment, the crew was acutely aware of the stakes. This was not just a battle for survival; it was a fight for the very essence of what Atlantis represented. Each shot fired, each manoeuvre executed, was a testament to the crew’s resolve. Their camaraderie shone through, as they worked in unison, anticipating each other’s moves, and bolstering one another’s spirits. Lorcha felt a strange sense of clarity amidst the chaos; purpose clear, and bond unbreakable.</p><p>As the battle raged on, some of the enemy ships began to falter, caught in the crossfire of the Dauntless defensive measures. Victory was close, but the fight was far from over. Just when it seemed the Dauntless might gain the upper hand, a massive enemy airship emerged from the clouds, dwarfing the Atlantean vessel. Its dark form loomed like a predator, and a wave of almost palpable dread washed over the crew. This was no ordinary attack; it was a calculated strike aimed at crippling the heart of the Atlantean Sky Navy.</p><p>With renewed intensity, the commander shouted orders, and the crew responded with fervour. The airship shook as she dodged incoming fire, weaving through the sky like a dancer in a tempest. Lorcha could see the determination in his crews’ eyes, a fierce resolve that mirrored his own. Despite the overwhelming odds, the Dauntless pressed forward, survival depending on the crew’s unity and unwavering spirit.</p><p>As the battle reached its climax, Lorcha found himself reflecting on the nature of conflict. It was chaotic, unpredictable, and yet, it brought out the best and worst in us. In the face of adversity, we were driven to protect what we held dear. The Atlantean Sky Navy was not just a military entity; it was a symbol of the aspirations of the people of Atlantis, their dreams of a future that was bright and filled with possibility.</p><p>Finally, after what felt like an eternity, the enemy began to retreat. The efforts of the crew working as a cohesive unit had turned the tide of battle, and as the commander looked out over the battlefield that was the sky, he felt a surge of pride. The Dauntless had faced the storm and emerged victorious, but the cost was evident. The sky, once so beautiful, was now marred by the remnants of battle — a reminder of the fragility of peace.</p><p>In the aftermath, as the crew tended to the wounded and assessed the damage, Lorcha realized that this experience would shape them forever. He realised that he did not just have a crew here; he had a family forged in the fires of conflict. Together, they had faced the darkness and emerged into the light, a testament to the indomitable spirit of the Atlantean people. And as the sun began to set on the horizon, casting a golden glow over the battered airship, he understood that the journey was far from over. The skies over Atlantis were theirs to protect, and this newly forged family would rise to meet any challenge that lay ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b1750fc7133" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bleakness …]]></title>
            <link>https://medium.com/@Just.Photos/bleakness-e4992660c8a0?source=rss-73cfa63c0a5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4992660c8a0</guid>
            <category><![CDATA[my-photography]]></category>
            <category><![CDATA[forest]]></category>
            <category><![CDATA[poetry]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Wed, 11 Jan 2023 09:13:07 GMT</pubDate>
            <atom:updated>2023-01-25T16:04:12.263Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCavjgUfUWju2S8rxQqdbg.jpeg" /></figure><h3>Bleakness …</h3><p>a bleak landscape<br>bereft of new life<br>a world transforming<br>in winter’s cold strife<br>hints of blue way up high<br>a promise for tomorrow<br>a message in the sky<br>dispelling sadness and sorrow<br>spring will soon be close by<br>a gift of new desire<br>letting hearts fly<br>and setting souls afire</p><p>🖤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4992660c8a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Undiscovered Country]]></title>
            <link>https://medium.com/@Just.Photos/the-undiscovered-country-6290557bd274?source=rss-73cfa63c0a5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6290557bd274</guid>
            <category><![CDATA[poetry]]></category>
            <category><![CDATA[forest]]></category>
            <category><![CDATA[my-photography]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Wed, 11 Jan 2023 09:05:59 GMT</pubDate>
            <atom:updated>2023-01-25T16:04:40.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xdVenAZfaelJsK38gt4Y0g.jpeg" /><figcaption>The Path to the Undiscovered Country</figcaption></figure><p>following a path into <br>the undiscovered country, <br>leading us on and cleansing <br>our troubled mind, <br>as we walk our way <br>into tomorrow, <br>we’ll not know <br>just what things we’ll find, <br>for in our desires and dreams <br>lay everything we need, <br>so keep on going <br>and hold that line</p><p>🖤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6290557bd274" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Return to the Diet …]]></title>
            <link>https://medium.com/@Just.Photos/return-to-the-diet-371cc4bd4dfe?source=rss-73cfa63c0a5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/371cc4bd4dfe</guid>
            <category><![CDATA[diet]]></category>
            <category><![CDATA[weight-loss]]></category>
            <category><![CDATA[body-shaping]]></category>
            <category><![CDATA[keto]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Mon, 02 Jan 2023 11:20:21 GMT</pubDate>
            <atom:updated>2023-01-02T11:20:21.091Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Male Muscular Torso. Close up of fit male torso and abdominal muscle with arms outstretched. Black and White studio shot isolated on white." src="https://cdn-images-1.medium.com/max/1000/1*_Wzj7kGkh0kzwWd56zyKVA.jpeg" /><figcaption>The body I would like to have rather than the one I have at the moment!</figcaption></figure><h3>Return to the Diet …</h3><p>After having 2 weeks away from the Keto diet (Christmas time, mistletoe and wine …) it is time to return. I ended the first stage of my body re-fit a week before Christmas with a weight loss of 28 pounds (just under 13kg) over 10 weeks, so pretty pleased with that as an outcome.</p><p>It was nice to get back to a more normal diet for the couple of weeks over Christmas, had a superb Indian curry, and a couple of good Chinese meals over the period and obviously Christmas dinner with all the trimmings. I continued my intermittent fasting during the period (only eating during an 8 hour period each day and simply drinking lots of black coffee and water for the rest of the 16 hours of the day) as I have kinda got used to that regime and it didn’t interfere with Christmas.</p><p>However as nice as the more normal diet was I am looking forward to getting back to the Keto. How mental is that? How can someone be looking forward to going back onto a restrictive diet unless they are crazy? No one ever accused me of being that sane though lol. Seriously I am looking forward to continuing to fix my liver and pull more inches off my waist (currently sitting at about -3 inches around 35–36).</p><p>I was talking to someone last year (about 3 days ago lol) and in discussing the diet process, I said I was measuring the reduction in inches rather than pounds (or kilos), which he thought was a really cool way to measure. He pointed out that weight can fluctuate up and down over a period, but your waistline is a much better yardstick (mine is now under a yard lol). So my aim is to hit 32–34 inches around the waist by the end of this leg of the diet in 13 weeks, which for an old fart like me would be amazing as I haven’t had a waistline in that ball park since I was a teenager.</p><p>And if I can continue with the exercise regime to reshape this tired old slab of meat then all the better. I will continue with the sit-ups, the cross training, the power twister exercises and the walking to try and increase my stamina, strength and improve my general fitness.</p><p>Watch this space …</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=371cc4bd4dfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[… and Rise]]></title>
            <link>https://medium.com/@Just.Photos/and-rise-173cecce9c6f?source=rss-73cfa63c0a5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/173cecce9c6f</guid>
            <category><![CDATA[wellbeing]]></category>
            <category><![CDATA[exercise-at-home]]></category>
            <category><![CDATA[lifestyle]]></category>
            <category><![CDATA[health]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Mon, 28 Nov 2022 08:34:14 GMT</pubDate>
            <atom:updated>2022-11-28T08:34:14.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDRIsUjQtmklKnFgI5WtXQ.jpeg" /></figure><p>What a difference a couple of weeks makes! In <a href="https://medium.com/@KevinTye/decline-21ed5b0fb5ba"><strong>Decline …</strong></a> I wrote about how I had felt that as I had reached my late middle age, my health and wellbeing was declining. Well I just had my Monday weigh-in, a ritual I began after starting my low-carb diet and for the 7th week I am down another 3lb (1.4kg) taking my weight loss to 21lb (9.5kg) over the 7 weeks.</p><p>More importantly, I am doing more regular exercise. I have a FlexCore workout device that helps exercise the body’s core and I have been using that every day for the last few days to assist in doing 60 sit ups a day, plus I am now doing 5 mins an hour (during my workday) on my cross-trainer. This amounts to significantly more exercise than I have been undertaking for a while and I feel better for it.</p><p>Across the summer I would try and walk a couple of miles at least 3–4 times a week, in the forest behind my house, however now the late autumn weather is here, (rain!!!) this is not quite as palatable, so indoor exercise is more the way.</p><p>I guess I am lucky that my workspace, a cabin at the bottom of my garden, has the room for some basic home gym equipment: a cross-trainer, a FlexCore, some weights, a power bar and some exercise tubes. These have been sat there for a while without much use, however now the crunch has come and I have to improve the way my body is working, they are a Godsend (and I am aware that if I had put them to better use earlier, things might have not got to the point where I <strong>have</strong> to use them, there goes that 20/20 hindsight).</p><p>I am going to step up this regime as my stamina builds and see if I can not only take the weight off, but do a little re-shaping at the same time. I am already noticing that my blood pressure is stabilising to a lower better managed level, that I am not craving sugary snacks anymore and that I am on the last notch of my belt, (when I bought the belt in July, I was barely able to fasten it onto the second of the five notches) so quite soon I will be needing to make some more holes, or god forbid, buy a new belt.</p><p>Time will tell, but if I keep at the diet and exercise for the next 4 weeks (yes I am pausing the diet if not the exercise over the Christmas period) I am hoping that I will have lost a total of 33lb (15kg), putting me at a weight I have not been for over 20 years with a level of fitness I have not enjoyed for probably 25 years.</p><p>Wish me luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=173cecce9c6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decline …]]></title>
            <link>https://medium.com/@Just.Photos/decline-21ed5b0fb5ba?source=rss-73cfa63c0a5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/21ed5b0fb5ba</guid>
            <category><![CDATA[wellbeing]]></category>
            <category><![CDATA[health]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Thu, 17 Nov 2022 09:48:31 GMT</pubDate>
            <atom:updated>2022-11-28T07:37:37.338Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A man is measuring his waist" src="https://cdn-images-1.medium.com/max/749/1*3VTBCl4HnXE1pukByVgVaQ.jpeg" /></figure><p>This is a story about how I reached my middling years and things began to stop working. Nothing has fallen off yet and I am hoping it won’t, but at my age, you never can tell.</p><p>I have been a Crohn’s Disease sufferer since I was 21-ish, I say -ish because I first showed symptoms (which no one in the medical world seemed to recognise for best part of a year) when I was 21 and was diagnosed formally at 22. But Crohn’s is something you learn to live with, learn to accommodate, like an old friend who travels with you all your days. No Crohn’s is not what started my decline. What started my decline was my own stupidity, eating all the wrong things!</p><p>When I hit my 50s, (having already dodged the death bullet 3 times at that point — 6 lives left) I was running in at around 266lbs (121kg), no that is wrong, I wasn’t running anywhere, I was walking, slowly. I had a particularly bad Crohn’s flare-up which had me feeling like crap on toast and forced me to talk to my Doctor. My own Doctor was unavailable so I had a chat with a colleague of his who turned out to be a bit of an expert on Crohn’s. He helped me sort out my flare-up and suggested I stop eating so much and lose some weight.</p><p>So I did! I bought a cross-trainer, lived on salads, and took these little blue pills, (no not those little blue pills, fat-binders), and low and behold, I dropped about 40lbs (18kg) in 3 months. And as soon as I went back to some semblance of a normal diet, some of those pounds went back on, not all but some. Wind the time machine forwards about 4-ish years and I was diagnosed with Type 2 Diabetes, oh and high blood pressure, but not high cholesterol! Go team me! Wind the time machine forward another 5-ish years and I have a blood clot in my leg (not a Deep Vein Thrombosis, but bad enough). Six months later I am told I have fat deposits in my liver, enough to give me stage 2 liver damage.</p><p>I am just falling apart!</p><p>But, the Doc said, “it is reversible”. So, I made the hard decision of dropping my intake of carbs down to a low level and put my body into Ketosis, (in Ketosis, you change your body chemistry so that instead of burning sugars you burn fat). I don’t know whether my Ketogenic diet is fixing my liver as I don’t have a fibro scanner to hand, but in 5 weeks, I have lost 14lbs (about 6.5 kg) and 2 inches (5cm) off my waist. So I am going to pursue this diet, continue down the road a ways and see if I can continue to lose weight, on the basis that if I am burning fat, at least some of it should come from my liver, shouldn’t it?</p><p>Ah, who knows. All I do know is that if I continue to lose weight steadily, I will probably:</p><ul><li>bring down my high blood pressure,</li><li>push my Diabetes into remission (with a little luck)</li><li>Remove the fat from my liver,</li><li>need more holes in my belt to keep my trousers where they should be!</li></ul><p>At any rate, losing weight for me can only be a good thing. So wish me luck on my journey, I’m going to need it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21ed5b0fb5ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>