<?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 Jackie Feminella on Medium]]></title>
        <description><![CDATA[Stories by Jackie Feminella on Medium]]></description>
        <link>https://medium.com/@jaclynfeminella?source=rss-7c4b9d0dcba1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LtCb8tPbDnmtTjFxxK0Bgw.png</url>
            <title>Stories by Jackie Feminella on Medium</title>
            <link>https://medium.com/@jaclynfeminella?source=rss-7c4b9d0dcba1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:19:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaclynfeminella/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[Why I love creating technical documentation]]></title>
            <link>https://medium.com/@jaclynfeminella/why-i-love-creating-technical-documentation-2bc53dd559a5?source=rss-7c4b9d0dcba1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bc53dd559a5</guid>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[technical-documentation]]></category>
            <category><![CDATA[technical-writing]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jackie Feminella]]></dc:creator>
            <pubDate>Sat, 16 Jan 2021 16:08:21 GMT</pubDate>
            <atom:updated>2021-01-16T21:56:42.626Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why I love creating technical documentation as an engineer</h3><p>There are plenty of types of technical documentation: Application README’s, project requirements, release notes, API documentation, just to name a few. In this post, I want to take a look at the benefits of technical documentation, and why I’ve learned to love creating and consuming internal technical documentation.</p><p><em>Caveat number one</em>: I am not a technical writing expert. I’m an engineer who enjoys creating technical written documentation and finds it beneficial to myself and teams.</p><p><em>Caveat number two</em>: Written documentation comes in so many different formats and is stored in many different locations. Meeting notes, project tickets, Slack updates, google docs, knowledge management systems — many of these locations and tools for documentation have a distinct (or maybe blurry!) purpose. Choosing where to store your documentation and keeping it all up to date is absolutely its own challenge, that I’ll leave for a future post. For now I’m going to treat technical documentation as a broad practice, and will try to mention some specifics when it might be helpful.</p><p>If you’re an Engineer reading this, I know it can be scary or daunting to create written documentation. It’s different. It’s new. You might feel vulnerable sharing what you write, because you’re used to writing <em>code</em>. However, I believe that writing technical documentation makes you a better engineer, and benefits you, your future self, and your whole team.</p><h4>It supports a “Remote First” culture</h4><p>Written documentation helps create a culture of <a href="https://circleci.com/blog/what-it-means-to-be-remote-first-vs-remote-friendly/">remote-first work</a>, which not only benefits ourselves <em>during</em> the pandemic, but sets us up to be more flexible and information-equitable <em>after</em> the pandemic. Some of us will stay remote, many of us might want a hybrid of remote and office work, and the rest of us are bound to at least have the occasional work from home day. Prioritizing a habit of written documentation ensures that information stays accessible, no matter where you work.</p><h4>It helps break down Knowledge silos</h4><p>Not every person on your team or in your organization will work on every project. Documenting what you know about a technology, project or feature lowers the chance of a <a href="https://stackoverflow.blog/2019/09/30/hidden-and-siloed-knowledge-within-your-organization/">knowledge silo</a>, and relieves some pressure on yourself as a potential subject matter expert.</p><p>Have you ever been asked the same question multiple times? Congratulations, that means you have some valuable knowledge to share! That’s a great chance to document the question + answer in an accessible place for your team. This will save your future self from answering the same question repeatedly, and will empower others to find answers they need, even if you’re not available. You’ve now saved your future self time and energy, and unblocked your teammates. You might even want to find the answer to that question again some day.</p><p>Have you ever joined a project that lacked documentation? You might’ve found yourself wondering how to get up and running on an <a href="https://cocoacasts.com/what-to-do-when-you-inherit-a-software-project">inherited application</a>, what the architecture of the project looked like at a high level, or even the scope of what it was responsible for. Many engineers run into this from time to time. This is a great opportunity to backfill documentation, for both yourself + future contributors to the project. Backfilling documentation, or ideally creating it throughout project development, is considerate to both yourself and future contributors to the project.</p><p>A personal rule of thumb that I try to keep in mind is, <strong>create documentation the way you would want to receive it</strong>. It’s an investment to both your future self and your teammates.</p><h4>It helps you deepen your own understanding</h4><p>Explaining something to someone else is a great way to deepen and reinforce your own understanding of it. Writing can be a form of asynchronous explaining, and I’ve found that technical documentation helps me analyze my own understanding of that information.</p><p>It also helps me stay curious about what else I might want to learn or add that would round out my documentation. Ideally, once you share your writing, your readers and teammates will ask questions and poke holes which will help you challenge your assumptions and understanding, leading to more accurate documentation and a more engaged team.</p><h4>It’s a transferable skill</h4><p>It’s no secret that software language trends go through ebbs and flows. I’ve been working as an engineer for about five years, and have seen countless system migrations, project re-writes, and adoptions of newer, better languages and frameworks. This constant cycle of learning and changing what languages you work in or what projects you work on can be exciting for many engineers.</p><p>However, practicing clear communication skills is something that will carry over across any language or project you work on, and will be a reliable asset to you and your team. I’ve found that I’m able to rely on this skill and habit as a force of stability throughout times of change and growth.</p><p>Being an advocate for and creator of documentation will likely help you be an even more valuable asset to your team and company, and gain trust if you’re conveying accurate information.</p><h3>Looking ahead</h3><p>In future posts, I’d like to cover types of technical documentation, as well as cover how to go about collecting diverse viewpoints, collecting feedback, and fact-checking your own work so that you can ensure you’re providing the most accurate documentation possible.</p><p>Thank you for reading! How has written documentation benefited yourself or your team?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bc53dd559a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a Front End Engineer can Benefit from DevOps]]></title>
            <link>https://medium.com/@jaclynfeminella/how-a-front-end-engineer-can-benefit-from-devops-9043cebefd8?source=rss-7c4b9d0dcba1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9043cebefd8</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Jackie Feminella]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 23:57:06 GMT</pubDate>
            <atom:updated>2022-07-01T22:53:39.662Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWYm3Dm7s0t8lLWYRW4pow.jpeg" /></figure><p>As any type of software engineer, having some DevOps chops can make your job easier and benefit your career. While everyone’s tools, terminologies, and interests are different, from my experience, the word “Fullstack” doesn’t just cover databases &amp; JavaScript anymore. For me, it includes <a href="https://aws.amazon.com/devops/what-is-devops/">DevOps</a>, which encompasses infrastructure and tools around deployments &amp; integration.</p><p>You may have a DevOps Engineer or team dedicated to the following things, and if so, that’s amazing! Here are a few reasons I’ve found that having DevOps knowledge as a Front End Engineer has benefitted my job and career.</p><h3>I’m empowered to fix big problems</h3><p>My company has on-call rotations. Occasionally, applications and services go down, or fatal errors get thrown. It’s empowering to pull application logs, troubleshoot the ElasticBeanstalk interface, or SSH into a problematic instance (if you have proper access of course). These skills help me get to the root of an infrastructure problem and enable me to triage quickly. This ability saves our end-users frustration from a broken website, and saves my company money that could be lost by the application being down.</p><p>No one likes a fire, however, I’ve noticed that leadership teams tend to reward when employees respond to this type of urgency in a timely way.</p><h3>I more deeply understand the interaction of Front End &amp; APIs</h3><p>My team has several monitoring tools that help us visualize what activity is occurring in our applications, one of which being NewRelic. NewRelic provides a dashboard for all of the interactions that our application makes. I can view external requests, how long they take, and see if any errors are happening.</p><p>I work on a Front End React application, so seeing visual trends of our API calls helps us catch any anomalies or bugs. If an API call suddenly takes 10 times the amount it took yesterday, I can raise this concern and troubleshoot the issue.</p><h3>I can save the company money</h3><p>Maybe your team hosts on Heroku right now, and loves it! Maybe instead though, you’re finding Heroku’s configurations to autoscale too limiting. Did you do the math and learn you could save money using AWS because of more fine-tuned auto scaling features?</p><p>If you’re aware of the infrastructure that’s hosting your code, you’re in a better position to have success pitching these types of suggestions. You might even save the company money, which won’t go unnoticed.</p><h3>I can improve my productivity</h3><p>Are your deployments really long and painful, but you have no idea why? If you get more involved in what the deployment process is doing behind the scenes, you can increase your team’s build speed. This too can save the company money, ship features more quickly, and boost morale for your team team.</p><h3>It’s the reason our apps exist</h3><p>Like fuel for the body, our apps wouldn’t be available to users if servers didn’t host our applications. It’s fun keeping the full picture in mind, and having appreciation for what actually is letting us do our jobs and reach our user base.</p><p>What other benefits have you noticed from flexing DevOps skills in a non-DevOps role? I’d love to learn from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9043cebefd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>