<?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 ivy 🧚✨ on Medium]]></title>
        <description><![CDATA[Stories by ivy 🧚✨ on Medium]]></description>
        <link>https://medium.com/@subvertivy?source=rss-d55815dedab8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NMuIve2Lx7pHV-Mdqc7Mpg.jpeg</url>
            <title>Stories by ivy 🧚✨ on Medium</title>
            <link>https://medium.com/@subvertivy?source=rss-d55815dedab8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:29:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@subvertivy/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[The Manic Pixel Dream Girl]]></title>
            <link>https://medium.com/misplaced-musing/the-manic-pixel-dream-girl-b114da3f1aa3?source=rss-d55815dedab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b114da3f1aa3</guid>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[belonging]]></category>
            <dc:creator><![CDATA[ivy ✨]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 19:30:27 GMT</pubDate>
            <atom:updated>2024-02-16T19:30:27.353Z</atom:updated>
            <content:encoded><![CDATA[<h4>How damaging stereotypes stunt progress toward a nuanced representation of multifaceted women, toxically reinforcing gender inequality in the space.</h4><p><em>🔖 Welcome to </em><strong><em>Misplaced Musing</em></strong><em>! I’m Ivy — an unconventional leader in tech curious to explore damaging stereotypes that can ultimately prioritize ego over humans.</em></p><p><em>This essay analyzes parallels between film’s toxic Manic Pixie Dream Girl trope and tokenization in the technology industry — how undermining complexity and agency of women in both storytelling and career disrupts progress toward a fair, nuanced representation of multifaceted women.</em></p><p><em>Though this essay draws parallels specifically to women in film and tech, tokenization unfairly affects all marginalized individuals.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*sVpbvvDZhc_yV9bD.gif" /></figure><p>Drawn to complex, melancholy films with characters navigating heavy challenges with deep sensitivities, I somehow remained pathologically unaware of a fictional character trope coined by Nathan Rubin, a film critic who extends analysis into profound cultural commentary. This unnamed trope threaded captivation through some of my favorite films while leaving me ignorant of its complex implications in both fiction, and more problematically, society.</p><p><em>Eternal Sunshine of the Spotless Mind</em>, one of my favorite films, whose main female protagonist, Clementine, boldly garbs brightly colored hair with a matched eccentric and unconventional approach to the world generally, emotionally journeys through the deep complexities of romantic love. She’s confused yet analytical, and passionate yet avoidant: a perpetual enigmatic contradiction. I was hooked on her theorized character development — a development that wasn’t written for her in the film explicitly.</p><p>I found similarities to Clementine when introduced later to the film <em>Scott Pilgrim vs. the World</em>. This film portrays a similarly unbothered and mysterious female protagonist, Ramona Flowers. Ramona helps the male lead confront his past in pursuit of his own profound self-discovery. Lacking her own substantial storyline, and with her colored hair similar to Clementine’s, I had to imagine Ramona’s depth.</p><p>This theme continued through the deeply moving film,<em>The Perks of Being a Wallflower</em>, depicting the struggles faced in a group of misfit friends. The female lead, Sam, unsurprisingly embraced an unconventional pixie cut, an eccentric attitude and a similarly relied-on sensitivity to Clementine and Ramona. She had a stronger referenced past in the film, but largely positioned throughout the movie to support the male lead through his own experience with trauma as the focus. Her storyline, again, lacked substance.</p><p>My quiet categorization of loved films that exposed this character trope of self-assured, though stereotypically unusual, women who calibrated the sensitivities of others (but toxically, particularly the cliché of their male love interests) wasn’t coincidence. This character trope, Rubin ultimately regretfully wrote in a critique for <em>Elizabethtown</em> which narrated a similarly quirky female lead, is the Manic Pixie Dream Girl (MPDG).</p><p>Once I stumbled upon Rubin’s classification of this character trope, the weight of its definition became complicated. Rubin lamented in his historic definition that the MPDG trope “exists solely in the fevered imaginations of sensitive writer-directors to teach broodingly soulful young men to embrace life and its infinite mysteries and adventures.” These women, not written with intention to develop their own nuanced complexities, existed in these films as one-dimensional distractions that guide the less whimsical male leads away from pain and instead into profound realizations they seemingly can’t do alone. Written to fuel unrealistic male fantasies, their deserved agency and innate depth is undermined. Damagingly, these characters are also, then, completely disposable.</p><p>The MPDG trope became incessantly pervasive across popular culture, referenced ubiquitously throughout film critique and extended through to society’s characterization of actual “Ethereal Weirdo”s (Mindy Kaling’s <a href="https://www.newyorker.com/magazine/2011/10/03/flick-chicks">satirical film name</a> criticizing this archetype). It offensively targeted films referencing deeply complex women characters, with the phrase wrongly implying their lack of depth, but more problematically extended through to real life women. Zoey Deschanel, for example, has perpetually struggled to escape the media-exaggerated caricature. Her twee aesthetic in both <em>500 Days of Summer</em> and the television series <em>New Girl</em>, being her comfortable style outside of these characters, superficially labeled her as a MPDG. She <a href="https://variety.com/2022/film/news/zooey-deschanel-rejects-manic-pixie-dream-girl-label-1235327531/">denounced the intended lightheartedness of the label as a toxic simplification of a multi-dimensional woman</a>.</p><p>After Rubin’s provocative critique gained cultural traction, the prevalence of the supporting, disposable Manic Pixie Dream Girl (MPDG) in media noticeably declined. What had initially been a lighthearted reference to unconventional women in media, intended to critique misogynistic storylines, evolved into something more insidious. This portrayal was not only insulting but damaging, reducing fundamentally complex women to mere plot devices designed to facilitate the growth and development of male protagonists. Even more concerning is that the existence of the MPDG stereotype predates Rubin’s naming of the trope, suggesting deeper societal issues regarding views on women.</p><p>While the classification of women through the MPDG lens is now rightfully condemned, broader efforts are needed to avoid shallow oversimplifications of multifaceted women in society. These written women were neglected, explaining my unsatisfied curiosity in who they were beyond the written screen. My interest in these films complicated as did my enlightenment on their stereotyped role. My relatability to the unconventional nature of their characters expanded through to the experienced neglect navigating my own professional atmosphere as the constant unconventional character. Clarity on the MPDG, it’s history and societal impact, exposed a troubling link between pervasive stereotyping in media and damaging biases in my own professional environment within the technology industry.</p><p>At the heart of these misogynistic gender biases lies the harmful association of specific roles and traits exclusively with masculinity. In male-dominated industries, where these biased associations are deeply ingrained and reinforced by limited representation, the task of promoting a more inclusive and respectful portrayal of women’s diverse capabilities becomes remarkably challenging. With the persistent gender disparity in tech, there’s a risk of a similar trope emerging — one that I’d call the Manic <em>Pixel</em> Dream Girl (MPxlDG), with eerie parallels to the original.</p><p>Importantly, my coined MPxlDG doesn’t actually exist in the tech industry. Instead of recognizing and prioritizing each woman’s individual strengths, there’s a danger of viewing them as uniform entities, overshadowing their unique capabilities and skills. Similar to the original pixie written in film, this pixel exists as a concept to merely support the main group in focus (being the male majority), instead of being fairly recognized for forging her own ambitious path in tech. She becomes the enigmatic side character, void of her own backgrounds, experiences, competencies and desired advancements. The Manic Pixel Dream Girl stereotype stunts progress toward a fair, nuanced representation of multifaceted women and toxically reinforces gender inequality in the space. This is the real danger of what’s referred to as tokenization.</p><p>Tokenization is an extraordinarily harmful consequence when companies create an appearance of prioritized and valued Diversity and Inclusion (D&amp;I) standards, while failing to directly address systemic inequalities and inequities for these individuals. While the pursuit of diversity of thought should be paramount, driving real innovation for these companies, the reality often sees efforts driven by a need to meet D&amp;I regulatory requirements or enhance optics during hiring. In this context, individuals are then reduced to tokens, akin to the Manic Pixie Dream Girl trope in film, serving as pawns in a larger corporate narrative.</p><p>Failing to recognize their intrinsic value and unique contributions, these individuals are simplified to mere representatives of their gender or minority group. In these industries lacking adequate representation, the risk of tokenization becomes almost unavoidable. An obsession with productivity and competitiveness often results in a prioritization of business interests over the well-being and diversity of individuals. Consequently, damaging stereotypes faced by minorities are sidelined or disregarded altogether.</p><p>Echoing Rubin’s Manic Pixie Dream Girl trope, we witness an equally perilous consequence: the disposability of minority individuals. This is radically damaging to each individual’s morale and career advancement, but also stunts the drive toward fair representation wholly. By pigeonholing minority individuals as mere tokens of D&amp;I initiatives, they are stripped of agency within their work environments. Their invaluable contributions and skills are unfairly disregarded, leaving them feeling marginalized and undervalued.</p><p>Unlike their majority counterparts, who are evaluated as individuals, these individuals are lumped into a larger category, making fair career advancement nearly impossible. This systemic tokenization not only undermines morale and a sense of belonging but also exacerbates feelings of imposter syndrome, further hindering just equity and necessary retention efforts. So we perpetually neglect and lose women in the field, and now become desensitized to this toxic perception of the disposability of minorities.</p><p>The misuse of these multifaceted women as disposable pieces used to accelerate and enhance the focused plot of the male-lead in film required a cultural critique and shift toward female-centric storytelling — either in writer and director or in character. Demanding authenticity and diversity from audiences, with accountable backlash when lazy stereotypes were used changed the film landscape dramatically. Prioritizing genuine diversity in the technology industry, stifling the possibility of tokenization, necessitates a similar condemnation to Manic Pixel Dream Girl stereotyping. Keeping the leaders of technology storylines accountable to constantly strive toward authenticity and diversity can’t be the sole responsibility of the minorities at risk of the MPxlDG label. The movement to end tokenization critically needs voices throughout the <em>entire</em> hierarchy of tech.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b114da3f1aa3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/misplaced-musing/the-manic-pixel-dream-girl-b114da3f1aa3">The Manic Pixel Dream Girl</a> was originally published in <a href="https://medium.com/misplaced-musing">Misplaced Musing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Suffocating Absorption of NormCore]]></title>
            <link>https://subvertivy.medium.com/the-suffocating-absorption-of-normcore-29b766ef0575?source=rss-d55815dedab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/29b766ef0575</guid>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[belonging]]></category>
            <category><![CDATA[unconventional]]></category>
            <category><![CDATA[homogeneity]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[ivy ✨]]></dc:creator>
            <pubDate>Thu, 08 Feb 2024 19:40:53 GMT</pubDate>
            <atom:updated>2024-02-08T19:40:53.940Z</atom:updated>
            <content:encoded><![CDATA[<h4>How the superficiality of this fashion convention points to a broader pressure of stifling homogeneity in tech</h4><p><em>🔖 Welcome to </em><strong><em>Misplaced Musing</em></strong><em>! I’m Ivy — an unconventional leader in tech curious to explore damaging stereotypes that can ultimately prioritize ego over humans.</em></p><p><em>This essay deconstructs freedom of identity in career and the intense magnetism of assimilation. For those who get offended by the phrase “tech bro”, I urge you to read with an openness that considers the negative impact it has on those who might look the part.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJ-heIT3L9Qg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJ-heIT3L9Qg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJ-heIT3L9Qg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1a457741b4ff68c4605c061bc91e403a/href">https://medium.com/media/1a457741b4ff68c4605c061bc91e403a/href</a></iframe><p>Stories of anecdotal “tech bro” nightmares exist openly within my now comfortable circle of like-minded friends in tech. Intimidation, frustration at the unacknowledged privilege, truly hostile or uncomfortable experiences are disheartening and real. <em>Brotopia</em>, by Emily Chang, describes how “[f]rom its earliest days the industry has self-selected for men: first, antisocial nerds, then, decades later, self-confident and risk-taking bros”. This is a commonly referenced excerpt from her 2018 novel exposing discrimination in the technology industry as it effectively captures the common thread of exclusion. The very clear preference in selection has persisted from hostility and bias toward those who don’t fit into that latter category of self-confident risk-takers. These same risk-takers who commonly carry privileged labels of miraged meritocracy and present as the archetypal Silicon Valley nerd.</p><p>I want to be explicit: the reference to this canonical tech bro isn’t intended to generalize every male within the space; quite the opposite. The toxic tech bro identity negatively impacts the experience for marginalized individuals, and that impact remains inclusive to anyone from unconventional paths or who displays less privileged characteristics. Even those who <em>seem</em> like a tech bro superficially. Factors like gender, sure, but also wealth, race, sexual orientation, network, alma mater, attractiveness, or ability can contribute to the perpetuation of this toxic stereotype. My reference of tech bro does not simply equate to white males in tech.</p><p>This one-dimensional identity, though, is plastered as the epitome of wealth and success in the technology industry. It toxically drowns out those who don’t resonate with the values or experiences of this group. Ambition to disrupt industries isn’t a trait exclusively held by this tech bro and the capability to execute successfully isn’t either. The real lack of representation leading to rampant bias toward groups outside of this majority makes operating any other way disagreeable, and at times career-damaging. So the professionally stoic, high-ego, normcore tech bro (and those who mask the facade strategically to gain acceptance, understandably) perpetually dominate as normal.</p><p>Normcore. I first heard this term sitting in a conference room with our Engineering leadership team. This was typical water-cooler conversation while we awaited a meeting start. I felt more comfortable perceptibly distracted on my laptop while quietly observing, and the “<em>I’d classify myself as normcore</em>” phrase piqued my interest. After a quick Google search I was educated with the new-generation, fashion-industry definition for what Mark Zuckerburg and Steve Jobs embraced wholly. Average-looking clothing. Thoughtless style, to leave room for more important decision-making throughout a visionary’s day. The grey shirt. The Patagonia zip-up. The black turtleneck. The normcore identifier at the conference table was wearing a zip-up and khakis. Completely juxtaposed with my pixie-cut styled with bows, a loud graphic-tee that read “Chronically Online”, thrifted jorts I meticulously found at Goodwill on a trip back to my hometown in the Midwest, and knee-high decorated cowboy boots. The normcore look shared by the majority of leadership noticeably differed from my personal expression. This palpable difference accentuated a gap I was already experiencing as the only woman at that same table.</p><p>This phrase goes beyond merely describing an average style. More importantly, it implies a cultural attitude that rejects the pursuit of individualism through distinct self-expression. While there are positive implications, such as resistance against maximalist consumption, within the technology space, the value often shifts toward homogeneity and presumed intellect. As Zuckerberg famously stated, seemingly trivial decisions like choosing a shirt in the morning consume energy that could be better used to solve critical, technical problems. The philosophy is clear: reducing any minor decision outside of one’s career can lead to faster success. This is unrealistic for most, and severely stifling for any diversity of expression, thought, or identity which all fuel creativity.</p><p>Without overextending on a seemingly superficial difference of fashion choice as the example, it points to direction of homogenous assimilation. This harms a supportive environment for representation of expression, fashion in this example, but more profoundly the expression of unique thought.</p><p>The obvious difference, and now descriptive characterization of that thoughtless style to optimize for computing elsewhere, bred my own anxiety. My journey to find personal individualism was not defined superficially by my developed unconventional style but has been sharpened by my more profound philosophy to liberate from extremely conventional societal norms instead. And so much of that desire for freedom was catalyzed by my early experience in tech. I intentionally, and stressfully, absorbed into the bro-culture to optimize for my own career potential.</p><p>Pieces of my early assimilation ranged from suppressing curiosity around self-expression, hyper-vigilance to hide my Midwestern roots in both culture and speech, mimicking office norms dominated by masculine interests. Letting go of my identity extended to overcompensation in effort while navigating intense imposter syndrome, feeling I had to prove I was worthy from my background to the masked tech bros around me. The stress of deserved place affected my unconcerned collaboration. I felt paralyzed offering ideas, posing questions, or raising conflicts to the group for fear of stereotyping myself as disagreeable. My fear of boldly bringing my own authentic self into the space and my effort to remain competitive stifled potential for candid self-expression. These pressurizing environments can often lead to groupthink and homogeneity, stifling the potential for a more inclusive industry culture. Inspiring diversity of thought and authentic expression of identity demands real vulnerability but rewards both a sense of belonging for the individual and lucrative collaboration for the company.</p><p>👾 <strong><em>For those struggling to find a sense of belonging or who are paralyzed from anxieties about deserved place in your career, join me on </em></strong><a href="https://discord.gg/5YeKzUfy"><strong><em>Discord</em></strong></a><strong><em> for a supportive ear</em></strong></p><p>Explicit reference to vulnerability can often evoke caricatures of radical sensitivity and awkward individualism. This perpetuation stems from the intersection of absorbing tech bro stereotypes — characterized by this obsession around career and a competitiveness and aggressiveness for wealth — and the archaic, damaging <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8469901/#:~:text=Traditional%20masculinity%20is%20considered%20as,19%2C20%2C21%5D.">traditional masculine ideology</a> commonly referred to as ‘toxic masculinity’. Embracing true, vulnerable self-expression becomes challenging amidst these societal masculine norms, as vulnerability is unfairly labeled as weakness. Consequently, individuals in the industry may resort to hyper-competitiveness, ego overcompensation, and a marked lack of empathy to avoid being perceived as less capable.</p><p>In a massively dominated industry where men struggle to shed the intense, stereotyped masculinity, and where there’s a general anxious assimilation to the marketed identity of success, the industry hinders the freedom to be oneself. Without a liberated sense of being, we’re all hyper-aware of how we’re perceived, suffocating the deeply thoughtful, understanding, curious, and unique groups of free-thinkers. In an industry valuing and demanding deep innovation, losing unfettered creativity, experimentation, and novel problem-solving from expansive diversity in thought feels paradoxical. The constant pressure to conform to this nebulous standard of tech bro, or its acceptable normcore conventions, severely deteriorates psychological safety and sense of belonging for most. If we call to reference Irvin Yeaworth’s 1958 horror movie ‘The Blob’, the contradictory pursuit to reduce complexity of thought and experimentation outside of tech creates and fuels a very undistinguishable monster. Normalizing sameness isn’t a good thing.</p><p>In my personal life, the journey to denounce this pressurizing conventional identity in both work and life has been exceptionally demanding yet magically freeing. This intention to boldly express my identity, my culture, my thoughts and sensitivities has catapulted me into a shamelessly effective leader in the space. Leading by example has influenced that same freeing feeling for my peers and colleagues.</p><p>Cultivating empathetic environments where my team feels psychologically safe demands deliberate effort. It involves directly asking about <em>emotions</em>, providing ample space for thought, recognizing the nuances of each individual’s identity, and nurturing them accordingly. Consistently reinforcing what actually matters, coupled with my own candid admissions of uncertainty or shortcomings, cultivates this culture characterized by humility, empathy, and safety. This is what really powers free-thinkers and innovation.</p><p>Fostering environments where employees genuinely feel safe to express their unique individuality is crucial for nurturing innovation. As leaders in the field, it’s lucrative to confront fears that often drive an avoidance of vulnerability and suppress self-expression. When creating these environments that reward vulnerability with acceptance, the space rewards stronger and more creative solutions. Building and nurturing a supportive culture goes beyond merely challenging norms in attire or vilifying this ‘tech bro’ stereotype; it requires dismantling the facade of what success in tech traditionally looks like. When individuals feel safe to express themselves freely, creativity, boldness, and collaboration flourish.</p><p>Celebrating unique expressions of identity unleashes profound innovation — perpetuating homogeneity critically contradicts this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29b766ef0575" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Autonomy of Discomfort]]></title>
            <link>https://medium.com/misplaced-musing/the-autonomy-of-discomfort-29a38da2c5de?source=rss-d55815dedab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/29a38da2c5de</guid>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[glass-ceiling]]></category>
            <dc:creator><![CDATA[ivy ✨]]></dc:creator>
            <pubDate>Fri, 02 Feb 2024 21:27:17 GMT</pubDate>
            <atom:updated>2024-02-02T21:32:13.310Z</atom:updated>
            <content:encoded><![CDATA[<h4>How the pervasive inequity of choice severely hinders marginalized groups as they strive for growth beyond their comfort zones.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*jxpWHdQUKjqcN7Fy2an3QQ.png" /></figure><p>I began feeling deeply haunted by my earliest undergraduate memory. Mehmet, though students referred to him casually as “Memo,” triggered a profoundly memorable spark during the Computer Science school’s inaugural freshmen acceptance speech. “To succeed in this field, you must become extremely comfortable seeking discomfort,” he ended while unpacking candy and Nerf guns from plastic grocery bags to gift in exchange for questions. A creative spin on the ubiquitous advice that real growth happens outside of one’s comfort zone. Instantly admiring a relatable, spunky technologist, my personal career compass direction was now set.</p><p>Becoming adept at sensing forthcoming deviation from my now North, fear lurked in when the shadow of complacency began following my later role as a Senior Quality Engineer at Robinhood. Possessed, it was almost uncontrollable when my fingers began typing in LinkedIn’s search field for “Quality Engineering Management jobs.” Outgrowing my role, I desperately needed either a promotion or an exorcism.</p><p>Soon after the intention was set to move on and up, I interviewed for the buzziest Head of Test position at a cutting-edge blockchain startup. What eventually evolved into a middle-management role initially allured me as a strategically advertised director role. From an individual contributor (IC) directly to the sole visionary for quality at the company. Cryptocurrency markets were at their peak in December 2021; cultural relevancy was high, and I could taste the excitement of extreme startup volatility. Known volatility, though now with an intensified challenge of explicitly setting direction and leading processes and teams. Delicious. Knowing determinately that the internal jump to director at Robinhood was impossible for me, this was my compass’s calibration back to the course of discomfort.</p><p>The leadership role’s responsibility suite, mostly ambiguous though somewhat descriptive by individuals who lacked software quality experience, was predictably overwhelming. I was now completely alone and relatively inexperienced in defining, scaling, and executing a vision that optimally maintained an unreasonably high velocity without shipping any tolerable bugs. My previous role at Robinhood comparatively now felt effortless, serving the reassurance that I was positioned well beyond where felt comfortable.</p><p>Metaphorically looking down at the greater height with sweatier palms and a subtly faster heart beat, I exhaled the triumphant sigh of relief that I was a few rungs higher on my ladder. Memo’s speech no longer tormented me; the confidence securing a challenging role soothed my guilt.</p><p>The role’s advertisement was dramatically rosier on paper. My exhilaration of greater heights rapidly evolved into an understandable anxiousness to strategize how I could realistically exceed my superiors’ expectations with such a challenging landscape. Expected but tough. Leadership above me blissfully unconcerned with completely dysfunctional inherited architecture, scrappily built by engineers long gone. This was now my problem. Balancing full-time individual contributor tasks with scaling demands. Typical in a small startup missing experienced leadership while entering into a needed growth phase. Aptly strategizing total investment in the only real path to managing these expectations, I needed a team to support navigating the predictable growing pains within a hyper-growth startup.</p><p>Blind investment in sourcing and interviewing competent engineers wasn’t sufficient, albeit much speedier. I had a maddening, constant hum as one of only two women on the leadership team. A whopping 20% representation. This hum signaled the persistent, painful reminder that without intentional sourcing, I was perpetuating a very pronounced disparity. A disparity within my control. Ignoring the perpetual diversity crises within tech, all to prioritize my own success, deeply deviated from my integrity — a compromise I could not justifiably make. Though safer for myself to interview hastily, I had a responsibility as a fellow woman to intentionally source for diversity.</p><p>I was excluded from any compensation discussions during hiring. Recruiting and upper-leadership handled negotiations from prospective engineers. During a casual late-stage conversation with an engineer in our interview cycle, typically sell-calls, she and I vulnerably discussed worry over her deserved “Staff Engineer” title. On her behalf, I worked aggressively to convince upper-leaderships approval to internally secure her extended offer. The correlation from title to compensation, respect internally, and advancement externally for future roles is meaningful. Companies strategically downplay its importance through expressions of value of grit and passion over one’s title. Staff engineering titles internally were rare, and she was the sole woman staff engineer. A massively deserved accomplishment for her and small success for representation in an extremely male-dominated company and broader industry.</p><p>Maintaining this equal balance, though, was exhausting and rapidly uncontrollable, firstly damaged by the company’s first round of layoffs. Crypto markets were widely slowing down, and the followed impulse to grow recklessly required tough decisions to now cut costs. Her layoff rationale was unexpectedly brought to me by upper-leadership. The direction was finalized without my invited participation and completely out of my control to argue after news was delivered. The explanation of her chosen layoff, with the second team member remaining alone, was convoluted and puzzling. Their rationalization had something to do with no longer having a business-need for Staff engineers. Not all Staff engineers were part of the layoffs. Apparently, this was a business-need examined for my team of two only. I would be delivering the news to her, of course — the company wanted to maintain their integrity.</p><p>Witnessing one of our highest-ranking engineers exiting without satisfying explanation on a team that desperately needed to continue scaling stirred forceful discomfort in her and me both. Leadership approved continued hiring following this first layoff, now for one level lower. Functioning outside of where felt comfortable in this scenario didn’t seem to feed into either one of our continued career successes.</p><p>Though an irreversibly broken Test Infrastructure team, our Product Quality team maintained higher morale, shielded from the pointed layoffs. I had more competency now as a maturing leader and sought out knowledge around their backgrounds, sustained performance, competency, and ownership to maintain active concern in their career. The sharper and frequency at which I could communicate their value helped pave their future advancement. This effort, though, exposed an obvious base-salary disparity between the two engineers on the team. Balanced in gender representation, it demanded action to escalate resolution for equitable compensation between both.</p><p>Shielding my direct report from daunting advocacy for herself, her curiosity of the communicated raise led to a necessary explanation. Striking enough ambiguity to keep this memorable as motivation for her future negotiation without causing tension toward her peer, the company, or tech generally was critical for both her morale and her awareness of potential inequity. Phrasing this less bluntly toward her at the time, she was simply paid less with more experience and stronger performance.</p><p>Although acting out of explicit fairness, I also felt emotionally compelled here. My own pay at the company was tens of thousands of dollars less than the same-level and similarly experienced male peers I worked alongside — validating the heavy narrative of pervasive pay-gap in tech. My colleagues collaborated with me in honesty so I had fuel to advocate for myself up to my manager. Though excluded from negotiations when signing offer letters, managers had access to their report’s salaries once onboarded — he knew the disparity existed.</p><p>Often triggered by that emotional connection, and exacerbated by typical societal expectations, the burden of addressing career inequity is frequently placed upon marginalized groups, exclusively. Confronting this territory of adversity boldly requires embracing a discomfort that consequentially often triggers massive implication to their own career and the career of who they’re advocating for. This is just another layer of injustice. My own internal reputation for pushing on biases and injustices was becoming starkly obvious to leaders at the company.</p><p>Eventually, I became the only woman left in Engineering leadership. I repressed the subconscious worry that I was ultimately devalued for my vocalization and even greater fears of being largely a D&amp;I token for the company, overlooked as a number to look good. The same ambition driving advancement in my own career and the career of minorities I led powered undervalued, oftentimes completely unknown, or reputationally damaging pursuits for fairness and progression.</p><p>My own small experience with an early-stage startup, one without active regulation and accountability, represents a small example of the dramatic scaling problem contributing to broader, perpetual disadvantages for minorities. Ultimately I quit my position with frustration around tokenization, under-appreciation, and unaddressed biases. Originating as a pursuit for greater challenge and career growth slowed down my trajectory for felt success. Memo’s energizing speech to strive for success by living outside of one’s comfort zone, conceptually simple for so many, radically complicates when operating outside of the majority.</p><p>I’m tossing it to whoever graciously finishes reading this article. Does it resonate?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29a38da2c5de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/misplaced-musing/the-autonomy-of-discomfort-29a38da2c5de">The Autonomy of Discomfort</a> was originally published in <a href="https://medium.com/misplaced-musing">Misplaced Musing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Irresistible Chip on Your Shoulder]]></title>
            <link>https://medium.com/misplaced-musing/the-irresistible-chip-on-your-shoulder-9b894f5310bd?source=rss-d55815dedab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b894f5310bd</guid>
            <category><![CDATA[attrition]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[ivy ✨]]></dc:creator>
            <pubDate>Thu, 18 Jan 2024 18:28:14 GMT</pubDate>
            <atom:updated>2024-01-18T20:25:34.337Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What exuded the attractive allure of perseverance to others slowly damaged my internal sense of purpose.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-7R8fcSVMEihvBoKvuQycg.png" /><figcaption><em>DALL-E Prompt: “metal pieces jutting out of the shoulder of an alien cyberpunk girl, subversive, moody, 8K portrait, shot on contax t2, portra 160 film”</em></figcaption></figure><p>My journey into the FAANG ecosystem and through to what I viewed as a canonically successful role in the technology industry originated from a tiny farm town located in rural, bumfuck Southern Indiana. This software-savant (/s) sat solitarily behind a computer on MySpace, finding ways to manipulate the design of my profile from templated HTML/CSS layouts for the novelty of my profile’s viewers’ experience.</p><p>I had no idea this was “coding” and I had no idea what languages I was interacting with, I was merely desperate to create a cute, minimal section in the middle of a patterned background that independently scrolled to show interesting facts about myself with every other excessive MySpace feature hidden from view. The goal wasn’t learning, the goal was profile novelty, thus stronger social status.</p><p>When degenerately making these profile edits on a school computer with our lab-administrator stealthily watching over my shoulder (I mean, there were 8 students in my class with my mother as the school secretary to our principal — I’m clueless where my confidence of lawlessness came from), I consequentially awarded notes that:</p><ol><li>I was no longer allowed to have MySpace</li><li>The administrator was impressed with my design and coding ability</li></ol><p>Unbothered by the command to stay off of Tom’s OG social platform and validated by the early affirmation, my tech career was profoundly catalyzed. What was originally ignorant play and exploration within the design space, formalized into a budding, though exceptionally pressurizing career. I no longer “coded” for the experimentation and visual appeal, I now confronted the perpetual adversities of advanced topics completely over my head.</p><p>In my early teens, I began attending summer camps avoiding the wearable tech courses and instead grappled with Artificial Intelligence and Quantum Computing. Intent on learning new programming languages, I sat in Java classrooms as the 30th student in a room full of 29 boys (if unclear, I am a woman). Ivy Leagues weren’t on my radar, instead I meticulously curated a resume that secured my admission into the School of Informatics and Computing at Indiana University. This was both a family alma mater and the hub for a relatively good Computer Science program — the only college I applied to, with my intense worry about an average SAT score lessened upon acceptance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D9x7Y0HMjJM_wTryPag5_g.png" /></figure><p>Now on a hardening career path, my focus shifted to landing internships at top technology companies. My manufactured professional identity donned a powersuit with borrowed leather binders holding half-page resumes and navigated shoulder-to-shoulder career fairs. Warnings sparked from peers that companies like Google would most certainly overlook a freshman from my college with my background, and instead I should aim for more realistic companies. I <em>did</em> get that Google internship, though it wasn’t the coveted Software Engineering (SWE) role. My triumphant defiance of expectations ended abruptly when a Googler approached my TechStop help desk, shockingly questioning my decision to take the perceptibly less valuable IT role instead of the SWE role. I wasn’t offered a SWE role.</p><p>Factors emphasizing my perceived inadequacy in an overwhelmingly complex field began accumulating.</p><p>Now tasked with suppressing constant stress to achieve top grades in my Computer Science courses, I feared both survival in a highly-competitive space branded by a non-Ivy League college and dreaded the next impossible challenging algorithm homework assignment. But getting the grades wasn’t sufficient, I needed to teach these classes as an undergraduate to prove my competency. Teaching was intense and demoralizing. Every “let me think” to buy time eroded my confidence, exacerbated by confessions of interest in me (albeit <em>really</em> in the hope for a complete solution to their complex algorithm homework).</p><p>My fear standing out as a <em>respected</em> engineer in a room full of individuals who looked just like the advertised Silicon Valley nerds grew as quickly as the deep insecurities surrounding my deserved place as an engineer. I overcompensated by networking closely with my university professors, desperate to both subtly communicate my earnestness in a space saturated with talent but collect bits of validation to soothe my gradually damaged confidence.</p><p>These anxieties compounded, fueling my decision-making and persistently occupying my thoughts. It felt crucial — without this obsession to prove myself, I was convinced of my inevitable dismissal in classes, throughout the broader school, and within the massively competitive industry. I exhausted myself and spent my confidence, facing pure rejection from leading companies for Software Engineering roles, until the pursuit to compete with my peers and secure an engineering job after graduation landed me at Apple as a Quality Engineer (QA) in the heart of Silicon Valley.</p><blockquote><a href="https://link.medium.com/e8sTnJGwrGb">“This is an easier entry-point to ultimately becoming a software engineer” I rationalized, masking the perverted feelings of rejection and defeat. Venturing into the tech industry through the lens of a QA engineer left me grappling with a sense of failure. That vivid image of the enthusiastic Software Engineer I aspired to be clashed with the, in my mind transient, role of QA I found myself in. My commitment to leveraging this role as a stepping stone towards the more profound and respected software engineering position deepened and soothed my shame.</a> 🔖</blockquote><p>My inherent, though unconscious, drive to assert my competence and earn respect as an engineer became evident during an early performance conversation. The director of our QA organization explicitly recognized this intrinsic quality as a valuable strength. With enthusiasm and sincerity, he celebrated the undeniable presence of a “chip on my shoulder” as a significant factor in my hiring, embedding the claws of that chip even deeper. Without prior awareness, it now became apparent the chip existed from an exhaustive pursuit for merit, the desperation to stand out as exceptional, and an anxiousness about my value — constantly affirmed by others with generational Ivy League or Silicon Valley roots, stronger degrees, more respected roles, their own comforting representation.</p><p>This director’s validation coerced me into a toxic relationship with my chip, steering to me notice signs of unworthiness and undervaluing that naturally, perversely, powered my clearly impressive work ethic and impact.</p><p>This was delivered to me under the guise of massive performance strength, this chip being an indicator of grit— difficult to hire for explicitly but one of the most invaluable characteristics of high-impacting performers. The director validated the deep anxiousness I experienced from my younger years through to industry. This explained my abandonment of the creative aspects of engineering to instead move through the maze of masochistic motivation to prove that while not like the stereotypical Silicon Valley successors, I could be a technologist.</p><p>The prevalence of what’s known as the “imposter syndrome” across young professionals, women specifically, the general population within the tech industry glaringly exceeds 50%. Lack of support or recognition, radical comparison, isolating fear of failure intensified by limited representation — thus community — a perfectionism that might be personality driven, but anecdotally cyclically worsens from self-doubt and feelings of micro-failures. Perfectionism can manifest as striking attention to detail and rigor, and that self-doubt can easily become hidden to others by an overcompensation of perseverance with the ultimate goal to succeed (or in the case of the imposter syndrome, keep cover as a fraud) in any context. Obsession with high-quality output, rigor, resilience, tenacity— all skills hired for, nurtured when identified, celebrated when impacting the team, indirectly the business.</p><p>So the chip on my shoulder similarly gets nurtured, as <em>I</em> grow my <em>chip </em>grows — I’m fed the narrative that my grit is unmatched and my skills are exceptional. My internal narrative, though, is instead fed with contradictory fears of worthiness, intensified by increasingly challenging situations and injustices encountered in my formal career — factors that initially gave rise to this chip.</p><p>This persistent drive to prove oneself remains sustainable only until the burgeoning weight of the chip becomes too overwhelming of a burden to reasonably carry.</p><p>Ubiquitous, hidden feelings of ultimate unsustainable exhaustion worsens when understanding the hardships or insecurities felt by immigrants, individuals without support to pursue conventional degrees, those facing socio-economic hardships, the massively underrepresented navigating male-dominated spaces, those challenging societal norm. Their boldness and resilience when surmounting challenges of big tech powers a blindly celebrated grit, indirectly powering the underlying dystopian motivation to prove worthiness in a space.</p><p>Burnout pipelines stabilize and strengthen:</p><ol><li>Employees with “chips-on-their-shoulders” are hired for their represented grit during the interview process</li><li>Now these individuals experience a desperate need to demonstrate their worthiness while competing with seemingly more prestigious or more capable peers</li><li>To expose their value at the company, they intentionally take on greater workloads ultimately sacrificing any meaningful work/life balance to accomplish the tasks, exceeding expectations</li><li>Toxically, leaders celebrate the intensity given to work as a passion for their mission</li><li>Leaders failing to match recognition for that specific individual’s strengths leaves them overworked, exhausted and now completely under-appreciated</li><li>This triggers validation to the chip’s ultimate fear of failure or unworthiness, triggering the intense and often irreparable feelings of burnout</li><li>Now we have attrition for the company, directionless burnout for the employee</li><li>🔁</li></ol><p>Companies often have pipelines designed to hire employees who demonstrate passion, persistence, or rigor. But there exists a vivid gap when it comes to rehabilitating perpetual ‘chip-on-the-shoulder’ employees who are motivated by fear. Without addressing and soothing the insecurities of these employees through empathetic and intentional reprogramming, nurturing their talents and interests, and promoting psychological well-being both at work and in their personal lives, we risk losing humanity in the tech industry.</p><p>This chip, originating as armor to help construct a psychological safety that empowers the exploration of innate talent in a space full of creativity and innovation, understandably becomes too heavy to carry.</p><p><strong>With safer environments, we shouldn’t need armor.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBb1QKhXa3qC9AsX4SbIjQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b894f5310bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/misplaced-musing/the-irresistible-chip-on-your-shoulder-9b894f5310bd">The Irresistible Chip on Your Shoulder</a> was originally published in <a href="https://medium.com/misplaced-musing">Misplaced Musing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architects of Happiness]]></title>
            <link>https://medium.com/misplaced-musing/architects-of-happiness-43937d893e34?source=rss-d55815dedab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/43937d893e34</guid>
            <category><![CDATA[devx]]></category>
            <category><![CDATA[morale]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[developer-experience]]></category>
            <dc:creator><![CDATA[ivy ✨]]></dc:creator>
            <pubDate>Thu, 11 Jan 2024 20:18:21 GMT</pubDate>
            <atom:updated>2024-01-11T20:18:21.335Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>If you care about preserving your builders’ morale and retention, stop downplaying the importance of internal-facing engineering disciplines.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*39cwVoJ2vXMvldnjOXURKQ.jpeg" /><figcaption><em>Robot Carnival (1987)</em></figcaption></figure><p><em>The concept of “internal-facing engineering” generally in the tech industry can encompass an exceptionally broad range of roles. In this article I’m focusing on </em><strong><em>Developer Experience (DevX)</em></strong><em> engineers who provide platforms and tools to accelerate engineering teams and </em><strong><em>Quality Assurance (QA)</em></strong><em> engineers who play a pivotal role in ensuring software quality during the development of new features.</em></p><p><em>I suspect, though, the sentiment expressed in this essay will resonate with all internal-facing teams.</em></p><p>Underlining the profound impact of the less-frontline, internal-facing engineering team is ultimately quite simple. Their suite of technical responsibilities includes mitigating convoluted complexities, which, when executed effectively, powers a higher-functioning pipeline. With these teams building and maintaining strong and stable pipelines, product-facing developers can more effortlessly overcome entrenched roadblocks allowing them to build and launch higher-quality products faster. These internal-facing engineers dedicate their careers to the success of a broader team, directly influencing the final product’s success for their users.</p><p>How powerfully mission-driven of a chosen discipline to invest ones’ technical focus and career growth powering optimal infrastructure that directly influences the health of the team and company. It generally feels like this altruistic choice — sure, partially selfish, as it involves pursuing an interest in fundamental technology or problem-solving scope — empowering the technology to reduce complexity for the engineers building what the user sees, interacts with, and recognizes as the brand. In my personal experience within this domain, I and my colleagues who are deeply dedicated to enhancing internal infrastructure and processes are propelled by a profound commitment to the product and its users. Not only do internal-facing engineers provide substantial nourishment to Engineering operations, keeping everyone optimally propelled with intensified momentum and sharper focus, but they do so fueled by one of the most significantly sustainable motivators: <strong>passion</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*D3DPhLQSiuz2OLeF.gif" /></figure><p>When we conceptualize Engineering operations theoretically <em>excluding</em> this described nourishment provided by QA and DevX disciplines, we’re imagining an Engineering organization that requires their frontline backend and product builders to own <em>every</em> comprehensive aspect of software development. To fully appreciate the weight of these responsibilities, let’s consider a single engineer tasked with creating and managing their own test environments and data. They must also scaffold and build their CI/CD infrastructure, ideate, execute, and automate expansive testing — manually and in automation — that accurately represents users. On top of this, they handle the instrumentation and monitoring of system health, addressing emergent alerts to maintain accuracy, stability, and overall system health.</p><p>Beyond the technical aspects, their work extends to forging strong interdisciplinary bonds when developing new features, significant investment in documentation for future reference, staying attuned to user happiness, and discerning defects post-launch. The responsibilities on that single engineer to steward stable software development removes potential for deep focus making forward-progress incredibly unrealistic.</p><p>I intentionally enumerate these requirements as <em>essential</em> considerations for the software engineer in this hypothetical scenario. In this world without internal-facing teams, the engineer not only struggles to build the product swiftly, hindering a crucial competitive edge, but also lacks the capacity to fulfill the myriad other requirements necessary for maintaining high-functioning and stable systems — both figuratively within the team and literally within the technical pipelines. Without embracing these requirements properly, the <em>product’s</em> quality degrades while concurrently damaging user happiness. Without embracing them properly, the <em>engineer’s</em> lack of focus would ultimately also diminish the users’ happiness irreparably. It’s a failing scenario.</p><p>It’s clear that demanding builders to unblock and guardrail <em>themselves </em>while sustaining enthusiasm for their ownership and thrive as a competitive product with loyal customers is, respectfully, absurd. Prioritizing QA and DevX teams within an Engineering organization, who wholeheartedly take on these responsibilities crucial for the product’s optimal health and the company’s success, is an undeniable benefit. By delivering powerful tooling that guards developers and empowers high-speed productivity, these internal-facing engineers offer more than invaluable internal tooling.</p><p><strong>💥 Expert architects within their technical domain, QA and DevX engineers also emerge as passionate architects powering morale within the organization, subtly yet profoundly influencing the entire team (and oftentimes the entire company).</strong></p><p>The subtle organic characteristics of internal-facing engineers contribute to high-morale organizational cultures, with an even more intense impact on each individual builder. Product-facing engineers anticipate daily reassurances and genuine comfort from their counterparts, who are able to empathize with the pressurizing expectations projected onto these builders from leadership. The support network within the team dynamic of peer product-facing engineers is evident. However, a deeper symbiotic relationship emerges when internal-facing engineers, driven by a deliberate desire to reduce technical overhead and accelerate progress, work ruthlessly to unblock and provide guardrails for safe product-shipping. This dynamic amplifies an unmatched emotional connection specifically between that product-facing builder and the internal architect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*8En5r6nYVgkLeVUE.gif" /></figure><p>The development of this emotional bond occurs naturally, requiring no active effort when companies effectively nurture radically committed QA or DevX engineers (along with broader internal-facing engineering disciplines akin to these). The efforts expended aren’t exclusively aimed at nurturing these teams for the sake of this advantageous relationship, but rather because of the incredible myriad of impact these teams provide for the ultimate synergy of highest-quality software development operations. Consequently, this supportive relationship emerges effortlessly as a valuable byproduct.</p><p><strong>💥 This symbiosis strikes an invaluable intersection improving velocity, product quality, and developer happiness collectively.</strong></p><p>Reflecting on this hypothetical of the imaginative software engineer forced to own their own quality and velocity at the cost of the product’s success while maintaining a sustained morale to avoid irreparable burnout is a little radical. Transitioning from this hypothetical to <em>actual</em> reality, we accept massive costs when organizations neglect to recognize the value of QA and DevX teams (or any internal-facing engineering team). Tactically failing to prioritize their initiatives or processes within the broader company goals and inadequately resourcing these teams has a downstream impact on overall developer happiness. Failing to support these teams forfeits (or severely neglects) that allocated focus of responsible champions who own culture of continuous improvement and fervently advocate for individual developer needs. The costly elevated pressure and diminished reassurance introduces unavoidable risk to an essential sense of <em>security </em>within the broader Engineering organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*eoCaJHlAC45CTRiR" /><figcaption><a href="https://medium.com/@ivy.eth/the-automation-utopia-is-a-mirage-17a7c5c6cf27">I urge you to read through misconceptions of Quality Engineering to understand the cost of overlooking this discipline. </a>🔖</figcaption></figure><p>Avoiding risk that overextends product-facing developers, which inevitably leads to straining pressure undeniably difficult to sustain, can be achieved by fostering a culture of respect and recognition for <em>both</em> product contributions <em>but also </em>the critical internal contributions powering this work. This necessitates an investment in resourcing, technical infrastructure and communicated value — <strong>all amplified by respected leadership</strong>. Such an investment materially elevates the entire Engineering organization acting as an infectious force that magnifies development speed, product quality, and overall morale.</p><p>My impulse to enumerate the reasons I feel leadership perpetually <em>falls short</em> investing in these critical engineers thrusts me into an angsty attitude that requires it’s own dedicated essay for deeper analysis (therapy?). Instead articulating three common leadership failures that prevent recognition of talent across QA and DevX teams, thus stunting the technical <em>and </em>emotional-value they bring to teams, feels appropriate here.</p><p><strong>1️⃣ Limited, <em>Limiting</em> Measurement</strong></p><p>Instrumenting less thoughtful performance measurement within Engineering and overly prioritizing the pace of feature development can lead to a severe oversight of signals within an organization. The inclusivity of core values within QA and DevX contributes to an awareness of each engineer’s impact on operational stability, scalability, external user happiness, and the promotion of collaboration, rigor, and a continuous improvement mindset among peer engineers. This not only expands the nuance beyond stereotypical measurements of an engineer’s success but also ensures leadership consideration of profoundly impactful values. Thoughtful analysis of each engineer’s impact is crucial, and it significantly benefits the broader intention of investing in tracking the holistic function of the company.</p><p>Ignoring these values during performance measurement not only severely neglects Engineering disciplines who aren’t exclusively shipping code, emphasizing established optics of less importance, it also signals to your product-facing engineers their value is completely restricted to staying head’s down and shipping <em>as quickly as possible</em> — so pressurizing and morale-damaging to both.</p><p>Including metrics that extend through holistic values of internal multiplying through smart collaboration or thoughtfulness and impact to external user happiness through a rigorous attitude helps prevent this limiting environment from manifesting.</p><p><strong>2️⃣ Economic Ignorance</strong></p><p>The cost of excluding QA and DevX disciplines during planning initiatives, however structured for the company, unfortunately sabotages the team’s success and security of progress. Missing active consideration of experimentation and testing requirements, environment changes and infrastructure impact caused by new or changing dependencies, or perception from existing user demographics, the roadmapping and predicted estimations are stunted with inevitable downstream disruptors. These factors are essential to feature-development and <em>will</em> eventually surface with reported defects, broken systems, customer escalations— all impacting now or future timelines.</p><p>When teams observe perpetual indicators that their target launch dates were missed or delayed, <em>even if this was the direct cause of ignorance during leadership planning</em>, this looming “explanation-burden” (a phrase I feel properly defines the doomed feeling of reporting unfavorable circumstances to leadership) really damages morale. The value of QA and DevX currency, when emphasized and considered top-down, limits the risk of spending even more (time, resources, money, <strong>happiness</strong>) from uneducated estimations.</p><p>This is easy to avoid— keep internal Engineering managers included in planning conversations. Simple.</p><p><strong>3️⃣ Superiority Complex</strong></p><p>Leadership’s exclusive focus on the impact of product perception and competitiveness within the problem space, while neglecting internal-facing disciplines, hinders collective growth and overlooks powerful strategic factors. Passionate QA and DevX teams, empowering faster development and delivering higher-quality experiences to customers, realistically contribute to evident improvements in overall customer satisfaction. However, when leadership frequently attributes these positive effects solely to smart product management, accurate market-fit, or an astute leadership strategy, critical factors from these internal-facing teams are often suffocated and overlooked.</p><p>This again perpetuates an ignorance of the significant value that internal-facing engineering disciplines bring to an organization and hinders the necessary investment required to continually empower the impact generated by these engineers. For leadership to avoid neglecting these disciplines, it’s as easy as maintaining a mindful pulse on the output and impact of these teams. This benefits the potential for both recognition and an even stronger, refined strategy.</p><p>Recognizing and sufficiently prioritizing internal-engineering disciplines is absolutely imperative for preserving builders’ morale and maintaining expert ownership over the technical architecture that powers high-velocity, high-quality product development. Acknowledging the often overlooked and undervalued disciplines, <em>especially</em> from essential precedents set and reinforced by leadership teams, organizations reap organic reward from this stewarded culture of quality, continuous improvement and a true <em>care</em> for their peers. This manifests in an unmatched and tough-to-manufacture collective synergy that propels company success. Without this intentional acknowledgement, the damaging neglect felt by these internal-facing engineers absolutely extends through to product-facing engineers and risks overall attrition across the broader Engineering organization, materially damaging the product’s potential success, sure, but also risking career-damaging emotional turbulence of your most passionate <em>people</em>.</p><p><strong>In essence, the architects of happiness reside within these internal-facing engineering disciplines, and their value is integral to the success of the entire engineering organization.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*MJy6iHOmr5iMQCMj.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43937d893e34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/misplaced-musing/architects-of-happiness-43937d893e34">Architects of Happiness</a> was originally published in <a href="https://medium.com/misplaced-musing">Misplaced Musing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Automation Utopia is a Mirage]]></title>
            <link>https://medium.com/misplaced-musing/the-automation-utopia-is-a-mirage-17a7c5c6cf27?source=rss-d55815dedab8------2</link>
            <guid isPermaLink="false">https://medium.com/p/17a7c5c6cf27</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[burnout]]></category>
            <dc:creator><![CDATA[ivy ✨]]></dc:creator>
            <pubDate>Fri, 22 Dec 2023 17:02:13 GMT</pubDate>
            <atom:updated>2023-12-22T17:02:13.595Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Let’s get real about the stereotypes that consequentially result in shitty software, disjointed teams and precious builders’ time wasted.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*kRg6Z4FkAg7QwXv32dfAcA.jpeg" /></figure><p>In December 2021, I embarked on a pivotal journey as the Head of Test at a cutting-edge blockchain startup. Tasked with shaping the vision and providing executive leadership for the automated testing strategy of their web and mobile applications, my mandate extended to ensuring the robust health and stability of the CI/CD pipeline.</p><p>The overarching objective was ambitious — to forge an industry-leading automation engine that never falters, delivering top-tier software for developers to navigate with unprecedented velocity. Notably, the responsibility framework deliberately omitted explicit reference to Quality Assurance (QA) or any manual participation in producing quality software.</p><p>The allure of an environment where developers can unfetteredly push software, unbridled by fears of defects and immune to disruptions in their pace, exclusively powered by an automated pipeline of stable and high-fidelity testing is enticing. But the stark reality for companies valuing both internal developer experience and external user experience (UX) is that such a utopian concept, while cute to imagine, can never — and perhaps more provocatively, <em>should</em> never — exist.</p><p>Peeling back the layers reveals the profound value of QA, often oversimplified as ‘manual testing’ of software. It dismantles the idealistic vision of achieving high-quality software solely through automation, challenging industry biases and pushing for a more holistic understanding of QA’s integral role.</p><p>I initiated my professional journey at Apple, entering as a Quality Assurance individual contributor after setting lofty and annoyingly limited goals to secure a SWE position in a FAANG company…and then constantly choking on the algorithm interviews (as one does with massive performance anxiety).</p><p>“<em>This is an easier entry-point to ultimately becoming a software engineer</em>” I rationalized, masking the perverted feelings of rejection and defeat. Venturing into the tech industry through the lens of a QA engineer left me grappling with a sense of failure. That vivid image of the enthusiastic Software Engineer I aspired to be clashed with the, in my mind transient, role of QA I found myself in. My commitment to leveraging this role as a stepping stone towards the more profound and respected software engineering position deepened and soothed my shame.</p><p>Curiously, the stigma associated with being a QA professional <em>naturally</em> existed despite no prior experience in the discipline.</p><p>The genesis of this seemingly innate bias surrounding QA isn’t rocket science. Let’s lean into the devil bias to illustrate how easily this can unfold: a single negative perception within the QA discipline can cast a wide shadow, leading individuals to make overarching judgments about the entire field. Take, for instance, the common association of QA with manual processes, often deemed slower than automation. In the fast-paced world where meeting the demands of eager, enthusiastic users and staying ahead of the competition is paramount, this perceived slowness becomes the very adversary we must urgently overcome. Speed in our processes becomes not just a <em>preference</em> but a <em>strategic imperative</em> for success.</p><p><strong><em>Why</em> would I want to join Apple as the very <em>thing</em> compromising its success?</strong></p><p>When decisions are influenced by these misconceptions, we inadvertently sacrifice a thoughtful balance between high-velocity progress and prioritizing developer speed while upholding top-notch software quality for users. It’s unjustified, yet the propensity to make sweeping generalizations is remarkably facile. What a paradox — the intentional practice of thoughtfulness, requiring time and consideration, frequently takes a backseat to the misguided prioritization of velocity, propelled by these ingrained biases.</p><p><strong>What are these QA misconceptions reinforcing biases that end up sabotaging our internal and external experiences, slowing everyone down while still producing buggy-code even with ✨automation✨?</strong></p><p>From my experience as an entry-level QA at Apple, a founding QA engineering leader at Robinhood, and the Head of Test at OpenSea, here’s my list of the major QA misconceptions compromising the velocity of the entire Software Development Lifecycle (SDLC) and leading to buggier code with lower-quality experiences for users:</p><h4>💥 <strong>QA equates exclusively to manual testing</strong></h4><p><em>I’m not going to talk about how these QA experts, oftentimes diluted to simple manual testers of software, can also wear SDET hats with impactful automation potential that take responsibility away from the builders and enable their focus on high-speed output without the personal thoughtfulness and accountability of their code-quality (it’s important to note I’m genuinely and fervently against the manual-QA-to-SDET-for-career-”advancement” pipeline— I’ll get into my opinions around that another time).</em></p><p>To reflect more accurately the biases that severely minimizes QA into manual testers— typically simplified even <em>more</em> dramatically into ensuring the company’s shipped features, living in a more stable state of maintenance with subtle updates, enhancements or bug-fixes, remain stable through predictable regression testing (<em>obviously</em> this devalues QA, repetitive testing like this requires automation otherwise a massive waste of human ingenuity)— it’s valuable to connect an analogy of Product Management, a discipline that demands inherent and ubiquitous respect in the industry.</p><p>ChatGPT describes product management as:</p><blockquote>…overseeing the entire lifecycle of a product, from concept to delivery. It involves understanding customer needs, defining a clear vision for the product, and collaborating with cross-functional teams like engineering and marketing to ensure its successful development and launch. Product managers act as the bridge between business strategy, user experience, and technical implementation to create products that meet both customer and business objectives.</blockquote><p>…which can also live as an accurate way to describe the complexities of QA who similarly obsess, not over the product fit in the market and to the target user demographic like product managers, but the quality of that software and the sentiment of the software’s users. For QA to effectively uphold these responsibilities, this role necessitates a deep understanding of the product’s diverse spectrum of customers and a nimble operational strength that fuses the shared championship of quality, again for ease of the user experience, across multiple stakeholders. QA manages this obsession of quality by bonding (1) Design and Product Management teams’ prototyping of the idea all the way through implementation of their vision to deliver the intended experiences to the users; (2) Engineering teams’ requirements from Design and Product to build those features and ensure with highest certainty code-quality throughout the SDLC; (3) Customer Experience and Marketing teams’ stability when handling the rollout and potential friction users may experience onboarding to the product; <em>and</em> providing these cross-functional teams the mentorship and tooling to properly steward quality <em>themselves</em> at each stage of the entire feature lifecycle, through and continuously <em>after</em> shipping to their users.</p><blockquote>̶P̶r̶o̶d̶u̶c̶t̶ Quality managers act as the bridge between business strategy, user experience, and technical implementation to create products that meet both customer and business objectives.</blockquote><p>The QA engineer has a stocked closet full of varying hats and are quick to swap out the worn fashion for whatever the feature-state requires with a strong interdisciplinary intuition to determine when that outfit change is critical. They test, yes, but their operational strategy requires a strong pulse on continuous quality of code and overall product experience for the users’ happiness (and ultimately the business bottom-line) entails so much more skill than the biased “manual testing” label denotes.</p><p>It’s also important to note there <em>are</em> some archaic organizations that focus solely on offshore QA, where teams merely verify existing feature quality by repetitively going through the same testing processes to ensure nothing has regressed. When I mention QA, I’m <strong>not</strong> talking about this particular approach.</p><h4>💥 <strong>The simplicities of manual testing can be fully replaced by automated testing</strong></h4><p>Though already detailing an argument around QA bringing more depth and value to an organization beyond manual testing, there does still exist an element of testing that requires an ingenious human professional to manually ideate complex coverage representing a product’s user and device configuration properly, execute that coverage to ensure the ideal user experience upon launch and drive the optimal strategy to maintain ongoing stability of that user experience following launch. This is manual in nature, but the industry’s obsession with automating everything ignores an immensely valuable market strength when obsessing over your <em>user</em>.</p><p>When prioritizing the quality of a completely new feature, where QA thrive and add the most value, QA must embrace ideating and prioritizing coverage of the diverse and complicated matrix of users’ platforms, devices, countries, identities, proficiencies, and interests. This should be done while upholding a meticulous and watchful attention to safety and security for the company’s diverse user base — uniquely catering to and addressing the specific challenges posed by the complexity and scale of each new feature.</p><p>QA valuably ideate this massive test coverage to comprehensively represent the company’s users and diligently dig to expose hidden and convoluted edge cases that don’t obviously exist without detective work. This responsibility, requiring that human QA to exert manual work, is clever in reaching the ultimate coverage strategy to sufficiently deliver a seamless UX. This strategy eventually prioritizes an efficient and thoughtful balance of automation and manual coverage, contingent on the complexity of the experience, without compromising either the launch date or the quality on launch. Without that human element the company willingly embraces an ignorance to the user and their complex matrix of usage, sparking friction to in the best case some isolated experiences and in the worst case entire classes of user types— all damaging the users’ sentiment toward the product and company.</p><p>Even this unrealistic automation utopia, in the devil’s advocate argument of a hypothetical organization having unlimited resourcing to achieve an idealistic state of expansive automation coverage running with stability and speed both locally and in CI/CD, <em>someone</em> must own leading the overall testing strategy to sufficiently advocate for the end users’ quality experiences with developer velocity consideration. The strength of QA engineering knowing the product and business requirements, bridging the working teams and championing a culture of quality, and advocating for the user they know almost personally remains a value-add.</p><p>It’s moot to argue in any case, this utopia doesn’t and shouldn’t exist.</p><h4>💥 <strong>QA generally compromises velocity</strong></h4><p>The pitfalls I’ve observed in companies over-indexing on automation being <em>the</em> solution to both overall feature shipping-speed and sustained product quality highlight an incredibly complicated approach to ownership: automated test <em>writing</em> ownership and automated test <em>maintenance</em> ownership. Without intelligent strategies for both, organizations are left with flaky and fragile automation and slow local or remote developer experiences that disrupts the entire company’s velocity. Assigning the automation implementation responsibility to any other separate internal team or external offshore team than the owning team who coded the original product requirement leaves a difficult-to-prevent knowledge gap from hand-off and onboarding disruption. Assigning the automated test maintenance once implemented by whoever, with the goal to keep the automated coverage high-signal and fast, to anyone other than the originally owning team ignites severely burdensome distractions that most always require interfacing with the owning team for guidance, <strong>costing substantial speed implications</strong>.</p><p>Let’s be clear: repetitive regression testing should <em>always</em> be automated across unit, integration and high-fidelity end-to-end testing and integrated in CI/CD to catch and block any obvious regressions from deploying to users. However, to prioritize even minimal automated <em>regression</em> coverage of a product’s most critical user experiences across the entire product surface of the supported platforms requires deliberate upfront engineering requirement planning and substantial development dedication during the SDLC to bring those requirements to fruition before launch.</p><p>Even if the cost of requirement-planning is acceptable, the resourcing alone for a team of developers to implement those automated test cases, verify their successful signal and integrate into the product’s CI/CD (while ensuring an ease of running locally, not just remotely in CI) requires developers with product experience and infrastructure experience, both. I of course argue that for sustainable product quality and stability when moving quickly as an Engineering organization, the priority of this resourcing for regression coverage is essential — but that allocation of resourcing to support a broad, complicated matrix of automated testing ultimately characterizing manual testing obsolete without any velocity impact is incredibly unrealistic, but also extremely risky and unpredictable.</p><p>There’s costly time and resourcing expenditure when over-engineering an excessive technical solution merely for the sake of <em>having</em> a technical solution as well as a massive user experience degradation when over-indexing on sole automated test coverage without integrating a thoughtful advocacy of the users’ wants and needs when interacting with the product.</p><h4>💥 <strong>QA technical competency is inadequate</strong></h4><p>Without applied Software Engineering skills and an ease when navigating complex algorithm challenges, QA often become categorized as non-technical individuals subsequently excluding them as genuine engineers. This breeds a toxic culture which separates Engineering and QA, leaving silos between the organizations which poisons the opportunity to integrate closely during the development process, cannibalizing speed of developer output while maintaining a productive quality concern. Without QA directly integrated into the SDLC <em>alongside</em> developers, naturally organizations fail to uphold the values of an Agile development methodology and mistakenly fall into a waterfall structure, handing finished pieces off to teams downstream. Waterfall development is a linear practice with less flexibility and adaptability, slowing teams down and costing overall speed (refer again to the busted velocity myth above).</p><p>Immersion within the Engineering organization fosters a deep technical competency that allows QA to excel in understanding intricate system architectures. This unlocks powerful integration closely within development teams, who can respect QA as true engineers speaking similar languages and working alongside to brainstorm comprehensively testing across the stack. QA utilize a profound understanding of the technical aspects of the product to ensure optimal functionality of the in-development feature.</p><p>Let’s use clearer examples of valued technical strength during the software development that QA can impact to save time while pushing for highest code quality. Prior to the user interface (UI) implemented for full end-to-end testing, QA can apply planned coverage on the database and API itself in isolation while encouraging which pieces should have automation coverage, making use of time during development without waiting for the entire product to complete before beginning their quality assessments. Or during defect reporting while QA tests new aspects of the in-development feature, QA’s technical strength can advise pin-pointing the exact problem within a developer’s code itself saving the developer time during the investigation and resolution of the defect.</p><p>This fiery technical proficiency gets smothered easily if QA becomes structurally isolated away from Engineering or even more subtly, culturally unacknowledged as an aspect of Engineering. The stereotype that QA just aren’t technical unfortunately fuels the smothering that organically devalues the discipline generally.</p><p>Devaluing QA unintentionally by over-indexing on automation being a faster and more effective solution compared to humans bringing their expert and creative advocacy for both the working interdisciplinary internal teams and external users the company serves only breeds unnecessarily complicated and inefficient internal operations that delivers degraded experiences to the population of customers whose sentiment directly correlates to a company’s stability and success. QA remain pivotal product quality and user experts, stewards of communication and champions of the UX across all disciplines.</p><p>Unraveling the stereotypes highlights why, despite my own initial biases when starting my career as a Quality Assurance engineer, I swiftly recognized that Apple’s product success was intricately tied to an unwavering commitment to quality with pursuit to launch with products as close to perfection as possible. The sentiment around my role shifted from a mere stepping stone to a more significant software engineering position, transforming into an invaluable, influential force dedicated to ensuring user happiness and striving for product excellence. Now 6 years into my career, advocating for a priority of quality as a culture, bashing these toxic stereotypes and maintaining a realistic balance of speed during feature development, has remained an integral piece of my continued leadership.</p><p>This isn’t sustainable, though.</p><p>The damage from stereotyping generally is quite obvious: they wield a profound impact on individuals and are often rooted in biases and misinformation limiting opportunities and equity in team dynamics. They foster discrimination, exclusion, and unfair judgments which also disrupts a profound approach to valuable thoughtfulness and consideration during the process of prototyping, building and shipping high-quality experiences to the very users supporting your company’s success.</p><p>The very pivotal QA engineers driving this unmatched concern that optimizes the UX undergo personal damage to their feeling of impact and value in an organization— we risk ultimate burnout and attrition of what is a deeply valuable addition to any Engineering organization. Burnout, a pervasive and tough-to-remediate poison, needs it’s own attention and I’ll dig into the destructive nature of this incredibly consequential reality that affects so many high-impacting, particularly support-facing, engineers.</p><p><strong>Let’s stop prioritizing the allure of an all-encompassing automation utopia over artful advocates of optimal internal and external experiences, connecting your users more closely to your product.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17a7c5c6cf27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/misplaced-musing/the-automation-utopia-is-a-mirage-17a7c5c6cf27">The Automation Utopia is a Mirage</a> was originally published in <a href="https://medium.com/misplaced-musing">Misplaced Musing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>