<?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 Mrs. Flinger on Medium]]></title>
        <description><![CDATA[Stories by Mrs. Flinger on Medium]]></description>
        <link>https://medium.com/@mrsflinger?source=rss-ead2cb5053b4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*eSLjA9c9JaePQorA2G5vYA.jpeg</url>
            <title>Stories by Mrs. Flinger on Medium</title>
            <link>https://medium.com/@mrsflinger?source=rss-ead2cb5053b4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:57:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mrsflinger/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 Tableau to prioritize Accessibility errors]]></title>
            <link>https://medium.com/@mrsflinger/using-tableau-to-prioritize-accessibility-errors-14d56790527b?source=rss-ead2cb5053b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/14d56790527b</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Mrs. Flinger]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 20:04:34 GMT</pubDate>
            <atom:updated>2020-01-10T20:21:20.057Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using Tableau to prioritize accessibility errors</h3><p>Tableau is a tool that helps people see and understand their data. As part of a <a href="http://bit.ly/bringing-a11y">new accessibility program</a>, I utilized Tableau to visually communicate priorities to stakeholders and identify repeated errors, and target quick wins.</p><p>Our senior leadership is interested in high level information: progress over time, the general performance of a page, and hot spots.</p><p>Developers are interested in fixing errors in code and identifying best practices.</p><p>Using Tableau, we can present a high level overview as well as details to keep both parties engaged and informed.</p><h3>The data</h3><p>In order to create our Viz, we need a data set. In partnership with another open-source dev, I <a href="https://github.com/lesliedoherty/a11y">created a command line tool</a> that runs an audit of the top 100 most visited pages of <a href="http://tableau.com/">tableau.com</a>*. To achieve this, we used <a href="https://www.npmjs.com/package/axe-webdriverjs">axe-webdriverjs</a> for the audit, which uses the axe api and selenium webdriver. The results for each page are saved as a JSON file.</p><p><strong>Examples:</strong></p><ul><li><a href="http://tableau.com/about.html">tableau.com/about.html</a> corresponds with audit-date/about.json</li><li><a href="http://tableau.com/about/careers.json">tableau.com/about/careers.json</a> corresponds with audit-date/about/careers.json</li></ul><p>The directory is structure is important to note when we create our join in Tableau, coming up shortly.</p><p>Example Folder Structure of Data:</p><pre>audits/<br>├── date/<br>│   ├── index.json<br>│   ├── about/<br>│       ├── careers.json<br>│       └── contact.json<br>├── anther_date/<br>│   ├── index.json<br>│   ├── about/<br>│       ├── careers.json<br>│       └── contact.json</pre><p><a href="http://bit.ly/a11y_json_example">Here’s an example JSON</a> result from one page of our audit. In the <a href="http://bit.ly/a11y_json_example">JSON example</a>, you’ll see I’m also <a href="https://github.com/lesliedoherty/a11y/blob/master/lib/utils.js#L42">calculating the total number of errors</a> in each category and <a href="https://github.com/lesliedoherty/a11y/blob/master/lib/resultHelper.js#L10">saving them to the metadata object</a> in order to access this information easily to create calculations inside Tableau.</p><h3>Importing data to Tableau</h3><p>Next, we import the JSON to Tableau. I set my schema to include as few levels as possible to reduce the amount of time Tableau takes to load the data. Since each page has its own JSON data, I create a join by wildcard that includes all sub-folders. I expand the search to the parent folder so all future audits are automatically included as well. See this example in Figure 1.1.</p><figure><img alt="Tableau Join screen with options for automatically including files in the data. Both check marks are enabled to expand search" src="https://cdn-images-1.medium.com/max/500/1*h7DyBFO61DZEA0ZcnIxIAQ.png" /><figcaption>Figure 1.1</figcaption></figure><p>Figure 1.2 shows the schema level. Note that the metadata and violations objects are selected. This provides enough information to communicate our main errors but does not include information in passes, incomplete, or inapplicable to prevent overloading the data source.</p><figure><img alt="Schema level window from Tableau Software." src="https://cdn-images-1.medium.com/max/1024/1*iTjpdnkIsl20JA_zU_Ocjw.png" /><figcaption>Figure 1.2</figcaption></figure><h3>Creating the high level overview</h3><h3>Creating a score:</h3><p>One of the main asks from our leadership was some sort of “score” to evaluate at a glance how our pages were performing. The idea comes from <a href="https://developers.google.com/web/tools/lighthouse/v3/scoring">Google’s Lighthouse analysis tool</a>. The <a href="https://docs.google.com/spreadsheets/d/1up5rxd4EMCoMaxH8cppcK1x76n6HLx0e7jxb0e0FXvc/edit#gid=0">calculation for the score is available online</a>, but for our purposes, we just need a simple calculation that will give us a trend over time. As long as it’s consistent, we can use any proprietary method for our calculation.</p><p>I created a calculation by taking the total number of violations for each page and dividing it by the sum of:</p><ul><li>the total Incomplete per page times .15 to weight the value to 15 percent return expected.</li><li>the total Passes per page times .40 to weight the value to 40 percent expected.</li><li>the total Violations per page times .10 to weight violations to no more than 10 percent.</li></ul><p>100 - ([Violations per metadata] / (([Incomplete per metadata] * .15) + ([Passes per metadata] * .40) + ([Violations per metadata] * .10)) * 100)</p><p>You might have noticed we’re not adding our calculations to a weight of 100. That’s ok. Remember we’re not including the incomplete tests and are only looking to find some representation visually on progress.</p><p>Figure 2.1 shows two columns of data: the page path, and the page score. The score is color-coded, to make it easier to identify problem pages at a glance. This Figure is only a partial list. In reality we have this information for all 100 pages run through the audit.</p><figure><img alt="Image of urls and their score in two columns." src="https://cdn-images-1.medium.com/max/1024/1*wgVZLOGJk2nZHR4zNcbmGg.png" /><figcaption>Figure 2.1</figcaption></figure><p>Figure 2.2 shows a chart of the calculated score over time. On the x axis is each month we ran an audit: May, June, September, and January. The top headers indicate the year, 2019 and 2020 (for January). The y axis has the score number. Each blue line in the bar indicates one page. Most pages are clustered around 75 to 90 with a few outliers. Our goal is to reach the highest number possible and trend toward most pages reaching 98 or 99 in automated tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*23OYWvhS5NT3ED12U_o-bQ.png" /><figcaption>Figure 2.2</figcaption></figure><h3>Interpreting the results</h3><p>The rest of the Viz is a more detailed evaluation of our results. These dashboards help us identify priorities and spot trends in errors.</p><h3>Overview: Errors Per Page Over Time</h3><p>To get a high level comparison, let’s take a look at our table of errors and visitors for each url saved for every audit we’ve run.</p><p>The table in Figure 3.1 contains the following information:</p><ul><li>The first cell in each row contains the relative Url.</li><li>The second cell in the row contains the number of errors and visitors for May 7, 2019.</li><li>The third cell contains the number of errors and visitors for June 9, 2019.</li><li>The fourth cell contains the number of errors and visitors for September 3, 2019.</li><li>The fifth cell contains the number of errors and visitors for January 6, 2020.</li></ul><p>Note that the September 3 error count for the “About” url was 31, but on January 6, the error count was 60.</p><figure><img alt="Image with a table of information for url and date, visits, and errors returned." src="https://cdn-images-1.medium.com/max/1024/1*kDlUvyDdaWf_uI7Tq_K8LQ.png" /><figcaption>Figure 3.1</figcaption></figure><h3>Drill down with HTML of errors by Url</h3><p>To understand what changed between audits, we navigate to the dashboard “Html of Errors by Url.” In Figure 4.1 the /about url has several new errors. The image shows a tool tip when hovering over the html. The tool tip provides additional information including the impact of the error, the error message, and a link to the page on production. Our page has been recently updated with new headings and images where many of the errors are occurring.</p><figure><img alt="Three columns of data: relative Url, code of the error, and a color coded square to indicate severity of the error." src="https://cdn-images-1.medium.com/max/1024/1*60VFxefcA-fo2y_r61e-Tg.png" /><figcaption>Figure 4.1</figcaption></figure><h3>Drill down with a graph of errors per page</h3><p>We can use the dashboard displaying a “Graph of Errors Per Page” in a similar way. Here we can compare the total number of errors on each page and see the changes between specific audits by filtering the date.</p><p>Figure 5.1 shows two nearly identical graphs side by side. The graph is a segmented color bar chart sorted by most errors per page to the left and least on the right. We have a legend of error IDs that match each color: yellow for color contrast, gray for heading-order, pink for image-alt and a dozen more. You also see a date filter — the one on the left is set for September 3, 2019 and the one on the right is set for January 6, 2020. The number of errors per Url is slightly more on the left than on the right, indicating fewer errors overall per page.</p><figure><img alt="Two graphs side by side with color coded bar charts. Two boxes for filters: date and legend of error IDs." src="https://cdn-images-1.medium.com/max/1024/1*1dUcW2EpR5i0xbNbZVw82A.png" /><figcaption>Figure 5.1</figcaption></figure><p>If we filter out the color contrast error the page with the most errors is our updated about page. Selecting the error block on the Viz provides some additional information in the tool tip, as show in Figure x.x. Three errors dominate the page: alt text for images, heading order, and discernible text for links. We can group these errors into action items for our content editors and developers to fix.</p><p>The same layout of graph is seen as Figure 5.2 but we no longer have the yellow color-contrast errors loading. The Urls are sorted from most errors to least, left to right. The left most bar is the about Url. By hovering over each of the colors stacked in the bar, the tool tip displays which type of error is associated with that color and Url and the description and number of instances on that page.</p><figure><img alt="Bar chart with Url as the x-axis and number of errors on the y-axis. Each bar is color coded with number of error types." src="https://cdn-images-1.medium.com/max/1024/1*acMB6PXJcI93IyZRPt9mkA.png" /><figcaption>Figure 5.2</figcaption></figure><h3>Finding the lowest hanging fruit</h3><p>Let’s say we want to target errors as a group instead of by Url. This can be helpful for component code fixes or global elements. For this, we compare the target HTML, error ID, and the number of Urls that contain the code.</p><p>The results give us a pattern of code shared among the highest number of pages. For example, in Figure 6.1, the top two errors that occur on every page are landmark errors. Addressing these two pieces of code will affect every page on our site and reduce the total number of errors by two per page.</p><figure><img alt="Three column table with html containing the error, error type, and a bar for each of the Urls that contain the code." src="https://cdn-images-1.medium.com/max/1024/1*CStlBUUjlQzzveZcgm5s9w.png" /><figcaption>Figure 6.1</figcaption></figure><p>We can continue using this method to find component based errors — errors that occur on multiple pages due to shared code.</p><p>In Figure 6.2, we notice the teaser-item component has a heading order error affecting multiple pages. We create a ticket and suggest using our best practices by changing the heading to &lt;h3 class=&quot;heading--h5 teaser-item__title&gt; . Once this fix is complete, we re-run the audit and see we have 82% fewer heading-order errors. The remaining errors are located in fields within the Content Management System as hard coded values and can be identified in new tickets for content editors to address.</p><figure><img alt="Three columns- html with the error, the label heading-order error, and the relative url of the error." src="https://cdn-images-1.medium.com/max/1024/1*nZ0GsLKkXeEQSJLsxrTmCA.png" /><figcaption>Figure 6.2</figcaption></figure><h3>Error Details</h3><p>For those curious to learn more about each error type, I added dashboards with their WCAG and 508 guidelines.</p><p>Figure 7.1 shows three columns of data. The first column contains the ID of the violation such as color-contrast, aria-label, aria-labeleby, and so forth. The second column contains tags associated with that ID such as wcag2aa, wcag143, section508.22.n. And the third column has colorful squares associated with each of the individual pages that contain that error. When the user hovers over the square, a tool tip with information is provided in addition to the id, tag, and url; the description of the error and a message such as “aria-label attribute does not exist or is empty.)</p><figure><img alt="Three columns, error ID, the associated tags of error category, and colorful squares representing each url with that error." src="https://cdn-images-1.medium.com/max/1024/1*2U45PKPqZQBMu9bJSh_Bvg.png" /><figcaption>Figure 7.1</figcaption></figure><h3>Conclusion</h3><p>These are just a few of the ways I used Tableau to quickly identify and prioritize accessibility tasks for each sprint cycle. I’d love to hear from you if there’s a dashboard you would find helpful in your accessibility workflow. Have you found agile methods that work well with your team?</p><p>Working toward an accessible website is an ongoing process. By visibly sharing the results of our efforts, stakeholders gain a more comprehensive understanding of our program.</p><p><em>Footnotes:</em></p><p>*<strong>Automated testing only covers roughly 30–40%</strong> of the errors on a page, so we consider this a quick first pass. It’s important to communicate to stakeholders the need to include <a href="https://www.deque.com/blog/manual-accessibility-testing-approach/">manual testing</a> to get a full picture. More information about manual testing in an upcoming post.</p><p>Interact with the Viz: You can <a href="http://bit.ly/a11yViz">see the Viz here on Tableau Public. This link takes you off the current page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14d56790527b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bringing accessibility to Tableau’s Web Team]]></title>
            <link>https://medium.com/@mrsflinger/bringing-accessibility-to-tableau-ad2bb3db10d9?source=rss-ead2cb5053b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad2bb3db10d9</guid>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[program-manager]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Mrs. Flinger]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 19:44:36 GMT</pubDate>
            <atom:updated>2020-01-10T20:44:23.798Z</atom:updated>
            <content:encoded><![CDATA[<p>Never underestimate the power of positive influence. I first worked with an accessibility specialist on a project with Wells Fargo in 2015. I found her input invaluable to the quality of my code. I would mock up our Front-End templates semantically and she would suggest accessibility enhancements. It was one of the most rewarding projects I worked on.</p><p>That project, and more importantly that partnership, led me to prioritize accessibility in every project. I not only had a new challenge, but a passion behind it. I was hooked.</p><blockquote><em>Many accessibility errors can be avoided by using semantic markup and SEO best practices.</em></blockquote><p>As I do with every project, I focused on accessibility very early in my new role on the web team at Tableau. While the team had a bit of accessibility experience, there wasn’t a standard, or a driver, for compliance. My objective was to bring accessibility to <a href="http://tableau.com/">tableau.com (link takes you to a new page)</a> and move us toward WCAG AA.</p><p>Then something happened that made my passion for accessibility more personal — my dad suffered multiple strokes. He is the person who taught me how to code when I was twelve, and encouraged me to pursue a career in tech. During rehab, I helped Dad access his computer by enabling all the accessibility options. I saw my dad come to life, briefly, as he navigated the familiar space. I promised him I would work to make technology available to everyone, regardless of ability, social status, or aptitude.</p><p><strong>Work as a Team</strong></p><p>One of the core values of Tableau is “We Work As A Team”. This is one of the main reasons I was excited to begin my role here. As a speaker for women in technology and a long-standing advocate for equality in the tech industry, working with a group of like minded developers drew me to the team. I quickly found a friend who wanted to learn about accessibility and we partnered in a grass-roots effort. We approached our product manager and senior leadership with our goals.</p><p>Several key points helped us gain support from leadership.</p><ul><li>We utilized data about the “<a href="https://www.accessibilityassociation.org/content.asp?admin=Y&amp;contentid=559">Return on Disability</a>” to convince executives of the value of accessibility.</li><li>We utilized our own internal core values to re-iterate our commitment to “design for people” and be an inclusive company.</li><li>We identified the <a href="https://www.atlassian.com/team-playbook/plays/daci">DACI role</a>s and participants. I took the role of Driver and worked to ensure stakeholders were informed, got appropriate approval, and collaborated with contributors on the team.</li><li>We partnered with the SEO team to educate stakeholders in the SEO benefits of accessibility.</li><li>We broke out the proposal into phases to lower the barrier-to-entry: an initial phase of research to validate our internal findings; a “build” phase to create the program; a “maintain” phase to integrate and train our developers and content editors.</li></ul><p>Our original pitch is captured in summary on Figure 1.1 from our presentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4B3BLMe3ClRR6qtlF7_Nw.png" /><figcaption>Figure 1.1</figcaption></figure><p><strong>The Evolving Process</strong></p><p>Our ultimate goal is to comply with WCAG AA standards. Accessibility takes time, patience, and the willingness to answer questions and educate each of the teams we partner with. With that in mind, we decided to focus on progress and evolution.</p><p>We established the following priorities:</p><ul><li>Develop a program mission statement.</li><li>Work with a third-party vendor to validate our initial findings.</li><li>Evaluate tools and resources.</li><li>Create an audit process.</li><li>Identify common error patterns.</li><li>Create tickets for known issues with recommended solutions.</li><li>Establish best practices.</li></ul><p>In between dedicated sprints, I worked with our developers using hackathons and code reviews. My team and and I gave multiple presentations on the importance of accessibility and shared our wins in the accessibility program.</p><p><strong>The Details</strong></p><p>During the first dedicated sprint, we involved a third party contractor to run an initial audit and create actionable tickets. I focused on separating code-based issues from content issues. The audit validated our plan to dedicate resources to improving accessibility.</p><p>For the second dedicated sprint, I researched tools and resources, and created a node.js utility which runs an automated audit on the 100 most visited pages. Using the resulting JSON, I created a Tableau Viz to better understand and communicate the findings to the team. For more details about this process, see “<a href="http://bit.ly/tableau-a11y">How I used Tableau to prioritize accessibility errors</a>.”</p><p>With the foundation established, I was able to plan an agile schedule. Each dedicated sprint began with an automated audit and a supplemental manual audit on a specific variety of pages. Each quarter allowed us to narrow in on a specific area. By tackling the low hanging fruit first, we demonstrated quick progress before starting to target more specific error types and their sources.</p><p>A general workflow for each sprint cycle can be visualized as Figure 2.1 and Figure 2.2.</p><figure><img alt="A flowchart of automatic and manual audits pointing to analysis in Tableau, patterns, resources, and action items." src="https://cdn-images-1.medium.com/max/1024/1*686d6EqR0dYhgl0xC4BznQ.png" /><figcaption>Figure 2.1</figcaption></figure><figure><img alt="Flowchart of patterns leading to action items, best practices, and training based on developer, content editor, and design." src="https://cdn-images-1.medium.com/max/1024/1*Pymz3JdffvX3a7KecGaMQw.png" /><figcaption>Figure 2.2</figcaption></figure><p><strong>Take Aways</strong></p><p>It’s important to channel your passion and mission in ways that speak to other’s priorities. My small team started with three people who had a vision and a passion to bring accessibility to the forefront. We adapted our communication style to suit our audience.</p><p><strong>Developers</strong>: focus on writing high quality, semantic code that not only works for accessibility, but improves scalability, reduces bugs, and increases SEO.</p><p><strong>Content Editors</strong>: focus on best practices to ensure audience members can understand content. As a global company, it is imperative we speak to a wide audience and maintain a professional, easily understood resource for customers.</p><p><strong>Executives</strong>: focus on investment versus financial return, and be specific in terms of timelines and goals. While some executives may be swayed by the legal argument, we didn’t find this to be as effective for our team.</p><p><strong>Product Managers:</strong> focus on scalability and time, how you’re going to address the “lowest hanging fruit”, and effective development practices. Be specific with estimates and give clear expectations for scope and completion.</p><p><strong>Audience Participation</strong></p><p>If you’re starting an accessibility program, or interested in learning more, I’d love to hear your thoughts. The accessibility movement is gathering momentum as more and more technologies and humans interact with each other. The internet has brought the world together. As incredible as its power for giving individuals an equal voice might be, we should ensure that voice is available to everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad2bb3db10d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fail Driven Development: a story about how one man can change a life]]></title>
            <link>https://medium.com/@mrsflinger/fail-driven-development-a-story-about-how-one-man-can-change-a-life-18626c0d4a4e?source=rss-ead2cb5053b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/18626c0d4a4e</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Mrs. Flinger]]></dc:creator>
            <pubDate>Sat, 06 Aug 2016 05:10:44 GMT</pubDate>
            <atom:updated>2016-08-06T05:14:28.595Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve gone to, and presented, <a href="http://geeuphq.com/2014/">many</a> <a href="http://www.meetup.com/codefellows/events/225586106/">talks</a> on <a href="https://www.themuse.com/advice/heres-the-real-and-incredibly-simple-way-to-get-more-women-in-tech">Women in Tech</a>. I’m so passionate about this topic that many years ago after graduate school, I proposed a related dissertation for my my PhD. I wanted to research teaching methodologies and retention rates of undergraduate women in computer science, specifically looking for correlations between languages taught and women’s interest and ability to stick with the program. Instead, I had a baby girl and never finished that research, unless you consider <a href="https://www.instagram.com/p/8PISKWNwvo/">coding with my ten year old </a>research. If that’s the case, I’d like to apply for funding.</p><p>My Dad is the one who taught me to code back in 1984 on a Commodore 64, when I was 9. I expand on this in one of my talks, about what it’s like to be a 12 year old girl coding; It’s basically a lot of stuff about boys. Anyway, my Dad is the same one who encouraged me to get back into tech after undergraduate school. He was always telling me that I could do it. “You’re smart enough, Leslie, and there’s no reason not to code.” It’s true, the only reason I could come up with is that it was scary. I don’t know why, but ‘scary’ is the word I used. Math wasn’t scary. Science was’t scary. Hell, I aced chemistry and physics and anatomy and physiology. Those weren’t scary. But code? That shit was Freddy Krueger level terrifying.</p><p>Having this intimate connection to the sensitive topic about Women in Tech makes me hyper aware of different environments. I’ve had a variety of experiences in my sixteen years in tech, from blatant sexism to subtle ‘micro’ aggressions. (I actually hate that term since it’s such a trendy word, but I have nothing else to explain the subtle eye rolls, blank stares when I explain a technical issue which result in them asking my male coworker the exact question and listen to his same explanation, or the hundreds of other small expectations like ‘you can take the notes for the meeting, right?’ because I’m the only girl and that’s a ‘girl’ roll on the team.) People are sometimes appalled at the things I’m told or the ways I’m treated. I recently read Dan Lyon’s “<a href="http://amzn.to/2aFppfg">Disrupted</a>” and relating to some near-abusive experiences in my career, found myself nodding with enthusiasm and for the first time could finally utter the words out loud, “I was not crazy! I am not crazy! This shit actually happens and someone wrote a book about it!” Of course, I know, he’s not a woman in tech, but as an older person in tech, there are a lot of similar experiences and at the end of the day, I’m happy to have something to point to and explain, “This is how I felt, too.”</p><p>Given that previous context, all 16 years, let me now explain how the past few months have been a huge, overwhelming, emotional sort of healing.</p><p>I’ve been working at a <a href="https://www.vectormediagroup.com/">small startup</a>, which I hesitate to even call a Start Up because it’s such a solid little Agency, since February. As a contractor, I can either be as tightly coupled, or as loosely coupled, as makes sense to my Business and to this Agency. Since I happen to have known one of the Founders for many years, someone I respect and admire as a friend and a developer, who is humble and honest and basically just a great person, and since I also <a href="https://www.flickr.com/photos/joelbradbury/6149773081/in/photolist-anr8FT-anrfsa-ansZCQ-anu7tC-anreNR-anrh5e-anrg1T-anre9V-anu3gL-anqNXx-anr4aF-ansk9N-antkAJ-anrcTp-ansTx5-anq1dM-anqzvV-anpR2V-ansHju-anqd9z-antrL7-anqZaa-antvs3-anssyo-antiu3-anqiqt-anpxAZ-anqmik-anstM7-anprHg-ansbSj-ante79-ansvmY-anrchn-anq31F-ant5AC-antydf-anpBCr-anpqDH-anshPf-anspSL-anrgve-anq7XP-anqTWn-anpHft-anpukX-anpMor-anpWwZ-anpoma-agMovR">happen to know</a> a few of the people on my project and have for many years as well, it is a great fit to be Tightly Coupled with.</p><p>A few months ago, at a <a href="http://peersconf.com/">conference I attend</a> hosted by a fabulous lady, with some fantastic speakers, I sat in person with two others from my team. We attended standup on the same screen, which never happens since we’re all remote, and we were able to share drinks and dinners and conversations about our project with more detail and connection than we usually can afford given our geography.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UdoRE28_ByKdgLTKd8xP7Q.png" /></figure><p>Since I had been struggling with something project related, I reached out to ask for some help. Sam offered, on his own time, on his own holiday from work, to sit down with me and Pair Program. We sat together, both of us coding and talking out loud and sharing our understanding of the problem and solution. He guided me, helping point out things I might have missed or something to consider, and left me to continue to work on my own while he attended a few sessions he was looking forward to.</p><p>I continued to work, taking three steps forward and one step back, until connecting with him again, and we sat for another few hours, watching error messages in the console. We celebrated each time the error changed. We’d high-five. “Fail driven development!” Sam gleefully expressed as we cheered a new error. With each problem we stepped closer to the solution. We did so together, without any judgement or harsh words about how we should’ve caught this or that or what an idiot I, or he, was for missing something. We both trudged through the code together until finally, blissfully, I hit refresh and no errors appeared and the code worked as we expected. We shared multiple high-fives (high-fifteens?) and stood up to be greeted by our teammate watching us with fascination as Sam turned to him and validated me by saying, “That was really tough.”</p><p>At the time, I teared up just hearing the words that I had thought so often during the struggle of that piece of code. It was oddly satisfying to hear the validation and even more satisfying to see the nod and understanding of our co-worker, and friend, as he quietly understood the elation. In fact, that evening when I said goodbye to Sam at the after-party, I actually burst into real tears. That emotion caught me off guard. I wasn’t even sure why I was crying, as I explained to my girlfriends, except that Sam did something for me that nobody had ever done: he worked with me as a peer and as a co-worker and validated how I thought and what my ideas and solutions were. For the first time as a female developer, I felt like an equal to a man. And that, apparently, makes a girl cry, gulping, tearful, girl-developer sobs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nm0fCVfW6r4sfr8tFn-6DA.jpeg" /><figcaption>Threeeeeee amigos</figcaption></figure><p>Over the following months, these men grew to be the people I could ask questions to. Without judgement, without questioning my competence, I never hesitated to ask even the seemingly simplest question and always felt so validated to hear, “I’m not sure, that’s a good question. Let’s see…”</p><p>Things I thought should’ve been so obvious, that weren’t to me, were also not obvious to either of them. My Pull Requests were met with kind and valid questions, “What are you trying to achieve here? Would it make more sense to do it this way,” and sometimes the answer was “Yes, it would,” and sometimes the answer was, “No, here’s why.” Both of my replies were valid and met with conversation and solution.</p><p>We continued in this way, <a href="https://www.flickr.com/photos/mrsflinger/albums/72157671226332231">seeing each other at standup on video</a>, sharing questions when they came up and generally enjoying having a wonderful team. Last week we gathered together again, for the third time in person, for a few days in the Vector office. The three of us got on like peas and carrots. As the “oldest threesome” in the office, we generally hung out together and shared stories and ice cream decisions. These are the important things, knowing songs and references from the early 80’s and knowing whether or not the chocolate Sunday was as wonderful as it appeared. (Spoiler, it was.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BQhkOS0FbRzEaFpa2v-9bg.png" /></figure><p>When Sam told us, which he did in our three-group chat, that he was leaving Vector, the same overwhelming emotion came back. I’m happy for him, of course, any company is lucky to have this rare gem of a developer and human being. But I’m sad for our project, for our team, to lose this spectacular person. As much as Stephen and I tried to corrupt his optimistic soul, with our sarcasm and general jaded nature, Sam met us both with compassion and love. <a href="https://twitter.com/monooso/status/728612346969661446">We have a saying now</a>, Stephen and I, which is that <em>We Blame Sam</em> for every time we seek happiness and loveliness, when we put someone first before ourselves, and when we generally seek to understand the beauty of the world, which can be a complete dick otherwise.</p><p>In this way, I want to say a thank you to my friend, to my co-worker, and to someone who might not even know the Very Big Impact he had on my spirit and my being. Sam? Listen up, please, because I know you’re going to try to not take credit for this. But I want you to know:</p><p>I blame you for my professional growth, for my ability to take suggestions well and to learn from someone who understands complexity with high level insightfulness.</p><p>I blame you for my willingness to try new ideas and to extend classes in javascript.</p><p>I blame you for my compassion to other developers and to myself.</p><p>I blame you for my new appreciation of Javascript. And for my appreciation of Naming Things. And my obsession that functions are Verbs and variables and classes are Nouns.</p><p>I blame you for wanting to go to Austin as soon as possible to tell your new team to treat you well because they better fucking understand what a great catch they just caught.</p><p>I blame you for each time I choose kindness over quick-temperedness and taking things personally.</p><p>I blame you for being able to articulate when I’m in code-brain and can’t use English words.</p><p>I blame you for wanting to share every damn photo of my dog.</p><p>And finally, I blame you for opening my eyes to knowing the ten things I can never not un-know, from your presentation in New York. That I will be many people in my lifetime, that the kindness I show to a child means more than I know, to choose the road that gives the best story, that my greatest loss might be my greatest fortune, that I want to live without regrets (and blurt out all my feelings and pretty much every time I think I’d regret not saying something), that I can blame my shoes if my outfit sucks, to listen to my life and tell my greatest story, and finally, to always have something with my coffee, preferably pie.</p><p>I’d write you a function to change each “I blame you” to “I thank you” but I don’t have time to get that PR in before you go.</p><p>So thank you, so much, Sam. For being such a Great Influence in Tech. I think if more people entered this field with your heart, the entire Women in Tech conversation would turn into “How can we change the world with all these amazing humans in tech?” You’re a great umbrella of change, and compassion, and knowledge and your presence does not go unnoticed.</p><p>You will be missed more than you can ever even know, or would let yourself believe. Thank you for being such a positive person in my career, in my life, and in my team. So much love and joy for your future. Also, don’t forget to write.</p><p>-Ldough “flinger” Leslie.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18626c0d4a4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s a conversation I’ve had often these past two weeks.]]></title>
            <link>https://medium.com/@mrsflinger/it-s-a-conversation-i-ve-had-often-these-past-two-weeks-832bd3edb896?source=rss-ead2cb5053b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/832bd3edb896</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[family]]></category>
            <category><![CDATA[code]]></category>
            <dc:creator><![CDATA[Mrs. Flinger]]></dc:creator>
            <pubDate>Wed, 16 Dec 2015 07:48:33 GMT</pubDate>
            <atom:updated>2015-12-16T07:48:33.519Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s a conversation I’ve had often these past two weeks. “You’re leaving <a href="http://deloittedigital.com/">Deloitte Digital</a>? Where are you off to?” “Nowhere yet,” I reply for the millionth time, “Taking some time to find a bit of balance.” The next response comes as almost multiple choice replies; A,”Oh you’re going to be missed so much. I can’t imagine what we’ll do without you. Best of luck.” B, “I’ve been thinking of the same thing but I just can’t find a way to make it happen.” C, “You’re so lucky.”</p><p>That last response, ‘C’, as happens with multiple choice replies, is the most common. This makes me bristle. See, I don’t believe in luck. I believe in a year of hard consideration, of watching carefully the health and status of a family, the financial and health benefit planning of boring reality and of jumping head first with a partner to the dark abyss of unknown.</p><p>I don’t want to hear I’m lucky. I’m not lucky. I’m sadly late with this action and hoping my family will not suffer the worse for it. I also have little support except the acceptance of a faithful spouse that “Things always work out,” which is more than luck, it’s asking fate to intervene.</p><p>It’s not all bad, though. I’m not throwing up the proverbial papers in disgust and running out the door shouting as I make my exit. To be honest, that’s not my style anyway. I’m more of a quiet overachiever, who will continue to work as hard as possible, even up until 4pm on the day I turn in my laptop. I care too much, I work too much, I can’t help myself. It’s for this reason, specifically, that it’s time to make a change. I remind myself that as I catch myself getting teary saying goodbye to familiar faces, friends, and teammates. I will miss them tomorrow. I will not miss the deadlines or commute or trying to balance a demanding corporate job and children and a new puppy. But the people, hell yes, I will miss them.</p><p>I won’t try to convey the intensity of all that is encompassed in “demanding corporate job, deadlines, and balance.” I leave that to someone who so eloquently stated my nearly exact experience in a book, “<a href="http://amzn.to/1T13jkj">Mom’s on the Brink.</a>” Please please<a href="http://amzn.to/1T13jkj"> read this and know that I endorse this completely.</a> It’s my experience. I will share more, of course, as the fog of time lifts and my vision clears, but for now, I let someone so much more equipped at this retrospection to explain it in depth.</p><p>At the end of the day, the Job won and my Family lost. My Career was winning at a high price and my Family was losing. At the end of the day, every day, I couldn’t say no to One More Pull Request. To Helping This One More Item. It’s partly my fault, partly expectation of the machine, and partly our culture.</p><p>What I could change, what We could change, We chose to change. This is not luck, this is sacrifice.</p><p>We’re sacrificing not only financially, but our health benefits, now spending weekends finding options through Obama Care. Let’s not dive in to politics at this point but let me say that without this option, my family may have continued down a path of destruction simply because we couldn’t afford benefits on our own. It’s a seemingly small cost but it can cost lives so much quality.</p><p>What we’re sacrificing in money, we’re gaining in health. At least that’s our goal. The mental and emotional quality of having a family unit able to be mindfully present each night and each morning at breakfast, without rushing to another call or an early morning check in, we hope, sustains us. My mother said, multiple times, “You think your children need you when they are young. They do, but here’s the thing, they need you exponentially more when they hit Jr High. That’s when you need to be there. Always.”</p><p>With a sixth grader and a third grader, musician and athlete, we can’t afford any time away. Two commutes: two and a half hours a day each, sports, music, homework, playdates, and now, puppy. Something had to break and I’m sad to say it was nearly us.</p><p>These are the thoughts I remind myself as I sit with my team, feeling the pressure as I no longer am able to contribute. I sit with them, huddled in our “War room” as we look at work remaining to be done before a massive deadline Friday. I know I’m leaving them in a lurch. I feel so guilty of this. “You’re the only one who can do this job,” I’ve heard. It’s comforting because I know I’m appreciated and in a strange way, validated. It’s been tough, and all the bullets I’ve try to shield my other devs from, I now show in my hands, as I share with them the burden coming up on them.</p><p>I don’t make a big deal about my leaving. It takes some people by surprise. I’m not good at good-byes. I’m better at, “I’ll see you later,” because I don’t believe in endings. I tell myself this again, as I give out hugs and watch eyes and see, and feel, the emotion behind them. I turn away before they see me get teary. The sincerity of the well wishing starts to crack my resolve. But the family gaining from this decision, not a lucky one, but a difficult one, is waiting at home.</p><p>My most recent project team takes me out to dinner. We share war stories. We’ve bonded in the past few months in the way people who endure hard times always bond: Respectfully, with inside jokes, and a shared sense of worthiness. It’s odd how much I love these people, how much I’ve been frustrated by, angered by, thrilled by, and protected by these very people. I understand the words, “We were on the project {var} together,” as an almost war cry. No explanation is needed beyond that sentence. You’re bonded because you’ve been through something together.</p><p>It’s late and my team is just packing up. I know the minute I walk out the door, I can’t come back in. I’ve turned in my badge. There is some niggling as co-workers, or rather ex-coworkers, nudge me saying, “I’ll let you back in. Can you finish that Jira ticket if we assign it to you?”</p><p>The thing is I would. Which is why I’m leaving.</p><p>I smile, I nod, I feel both terrible and terribly frightened. I feel optimistic and finished. I couldn’t go another minute. I couldn’t go four more days to the finish line, I couldn’t go another step. I think of our brand new puppy, 9 weeks old, when he’s decided there’s no more walking. He sits, among whichever commotion is happening, and waits.</p><p>I’m nearly puppy-like in my need to be still now. The family needs me to be still now. I physically can not be part of this wheel. So I have to watch it as I walk out the door.</p><p>Hugs are given, more looking-away by me, more wiping of tears, more promising to be in touch, more possibly future work by contract. I know life gets in the way of the closest of friends, I know it will happen to many of us. I also know, life has a way of velcro-sticking those we need to remain in contact with and I know those people will continue to show themselves throughout my now and forever.</p><p>It’s at this moment as I’m about to close the locked door, without way of re-interane, on the place that’s nearly as comfortable as home now, that a friend comes running at me with the bottle of wine. “You can’t leave without a gift! You need this!” I laugh, look away again, and wipe the tears. “Of course! Thank you Uncle D!” It’s not an expensive bottle, it’s a $9.99 Costco buy, but the sentiment raises the value ten fold. I’m on the verge when the door closes behind me.</p><p>It wasn’t until I finally found myself in the bathroom, that I cry. I look at myself in disbelief. I am crying! At leaving a job! But I take a lesson from my mindfulness app and I go with it. I feel all the feelings. It’s so “Inside out” but it’s also good. I let myself feel the sadness, the frustration that it couldn’t keep working, the disjointed expectation, and I lay the hope of my career at this place at the foot of its grave for the last time. Women in Technology, I spoke so passionately about only a few months previously. “Too many woman are leaving the workforce because of work/life balance.”</p><p>Today, I am a statistic.</p><p>I drive in the rain, that long commute home, for the last time. I think of a quote that I heard on a podcast recently, “All one ever truly wants is to be missed.” I am thankful for being missed.</p><p>I tuck in my children and snuggle with the puppy without thinking of that late night call, or of checking email, or slack. I open that bottle of wine to celebrate, and sit to write my thoughts. It’s the first time in nearly four years I feel the freedom to write this down. The realization hits me like a wave, as I watch the puppy running in his sleep, as I hear my son’s heavy breathing, and my daughter and husband’s “nearly finished epic story-book” being read. I am thankful for this experience, for this day, for this time.</p><p>I will end with this, raising my proverbial glass, as only an optimistic could do: Here’s to tomorrow. Here’s to the next forever. Here’s to making the next generation not choose career or family. And, not at all least, here’s to you all, my friends, my teammates, my companions, my sanity, and of course, my family. Thank you for this experience. Thank you. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=832bd3edb896" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>