<?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 Chelsea Baltierra on Medium]]></title>
        <description><![CDATA[Stories by Chelsea Baltierra on Medium]]></description>
        <link>https://medium.com/@cbaltier?source=rss-42c616b35b14------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HveLzsF4ADFhCao1fbaRpw.jpeg</url>
            <title>Stories by Chelsea Baltierra on Medium</title>
            <link>https://medium.com/@cbaltier?source=rss-42c616b35b14------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:15:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cbaltier/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[3 Secrets for Upgrading your Grace Hopper 2016 Experience]]></title>
            <link>https://medium.com/salesforce-engineering/3-secrets-for-upgrading-your-grace-hopper-2016-experience-3ffa5a6887d0?source=rss-42c616b35b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ffa5a6887d0</guid>
            <category><![CDATA[ghc-2016]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[grace-hopper-2016]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[grace-hopper-conference]]></category>
            <dc:creator><![CDATA[Chelsea Baltierra]]></dc:creator>
            <pubDate>Mon, 10 Oct 2016 05:39:27 GMT</pubDate>
            <atom:updated>2016-10-12T21:23:47.995Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fbd3MP0pCIH4dvhMPOnvg.png" /><figcaption>“Grace Hopper Pro”</figcaption></figure><p><strong>Grace Hopper is only a week away</strong>. That’s right, <strong><em>one week</em></strong> until the amazing shenanigans are kicking off (where did time go?)!</p><p>I recently spoke at one of the regional Systers Pre-GHC meetups last week and the amount of excitement and enthusiasm everyone had for making the most of Grace Hopper was amazing. Whether you’re on the hunt for a new job, eager to network, or yearning to learn something new at one of the many talks spanning 8 clusters, here are some tips on making the most of your time at GHC 2016.</p><p><strong>1. Decide on a specific mission for why you’re attending</strong></p><p>With so many networking events, tech talks, career discussions, and invite-only parties, it can certainly get overwhelming when trying to decide what to participate in. That’s why I suggest deciding on your own personal mission that you want to achieve while there. What ultimately brings you to the conference? Are you there to meet new friends who share a similar experience as fellow women in tech? Are you there to find that next job? Are you there to learn new skills about communication in the workplace? Are you there to reconnect with old friends? One of the common things I hear from post-GHC attendees is that they wish they “could have attended more tech talks,” or “would have networked more.” Frankly, it’s very difficult, if not near impossible, to attempt to do effective networking, life-changing career discussions, meaningful mentoring, and finding the next dream job at this scale, all very thoroughly in just three days. <strong>Deciding on a specific mission is a great way to filter out what events will likely move you forward on that mission.</strong> Plus, you’ll be more likely to achieve success with a very specific mission in mind, rather than having regrets about participating in all the things.</p><p><strong>2. Use QR Codes to Make Networking Seamless</strong></p><p>One of the keys to effective networking is making connections that last. Often after meeting someone you want to formalize a connection, whether that involves exchanging contact information, passing along a business card, or adding them on LinkedIn. One of the common ways attendees do this is by writing their information down on a notebook, piece of paper, or phone and then asking their newfound connection to do the same. Afterwards, the hope is that the attendees will store that information somewhere more permanent or act on that information to reinforce the newly created connection. Why wait till after the conference and make it seamless? Create a QR code using one of the many QR code generators available online and use a link to your LinkedIn, GitHub, or website. Then simply print it out and attach it to your badge, save it to your phone as an alternative, and voilà! Instant connecting in minutes and no more post-GHC lists of contacts to go through and add manually to your LinkedIn!</p><p><strong>3. Take time to reflect</strong></p><p>I once had someone ask me after sharing this tip if I was “one of those mindfulness people.” Not only was I amused, but I began to question myself about whether this actually worked for others (it certainly seemed to work for me). However, according to recent research by the <a href="http://hbswk.hbs.edu/item/learning-by-thinking-how-reflection-improves-performance"><em>Harvard Business School</em></a>,</p><blockquote>“Why do reflection efforts generate an improvement in problem-solving capacity? We propose that the link between learning-by-thinking and greater performance is explained by self-efficacy, or a personal evaluation of one’s capabilities to organize and execute courses of action to attain designated goals…”</blockquote><p>That’s right, reflection isn’t just a mindfulness technique. <strong>It’s also a proven way to evaluate what you’ve learned by reframing those newly learned skills and experiences into actionable steps.</strong> Reflection doesn’t all have to be the same, though. To some, it may mean having coffee in between sessions with a friend and discussing what they’ve experienced; to others, it could mean blogging their thoughts, while others might take some quiet time to write and simply think through the wealth of information. Whatever practice you’d like to use, reflecting is a crucial yet often overlooked step to making the most of your GHC experience. After all, what good would the GHC experience do if there weren’t ways to put these new ideas and innovations into actions?</p><p>Do you have any Grace Hopper upgrade tips you’d like to share? Feel free to leave a comment. Looking forward to yet another incredible Grace Hopper Conference, see you next week!</p><p><em>Originally published at </em><a href="http://womanomaly.com/3-secrets-for-upgrading-your-grace-hopper-2016-experience/"><em>Womanomaly</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ffa5a6887d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/3-secrets-for-upgrading-your-grace-hopper-2016-experience-3ffa5a6887d0">3 Secrets for Upgrading your Grace Hopper 2016 Experience</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Quality Engineering a Dying Art?]]></title>
            <link>https://medium.com/salesforce-engineering/is-quality-engineering-a-dying-art-d75fab1963d9?source=rss-42c616b35b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/d75fab1963d9</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[trust]]></category>
            <dc:creator><![CDATA[Chelsea Baltierra]]></dc:creator>
            <pubDate>Tue, 23 Feb 2016 13:01:01 GMT</pubDate>
            <atom:updated>2016-04-07T21:41:00.588Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9qGFK0jjigADvy4BF_PZ_A.jpeg" /></figure><p>The first question on my interview phone screen was this: “What’s the difference between quality engineering and testing?”</p><p>Having taken the only two-unit college course in software testing that was required for my Computer Science degree, I froze. Was there actually a difference? Was testing really the standardized mean by which we determine code is “successful” or not?</p><p>The interviewer went on to explain: “Testing often seeks a binary answer: pass or fail. The code under test works, or it doesn’t. It meets these objective, measurable standards, or it doesn’t. Quality engineering goes beyond testing. It involves making judgment calls that a simple pass or fail test won’t make for you. Quality engineering helps us determine whether a product is actually useful to the customer and is designed in a visually appealing, performant way. It also helps us to ultimately determine how to be a voice for the customer when there are competing interests, limited resources, and various design options in a feature.”</p><p>Leading up to that interview, I had always thought that quality engineering and testing were one and the same. I thought that the phrase “quality engineering” was just a more appealing way to brand the role. Besides, it’s no secret that quality engineers and testers have sometimes been seen as a vestigial role from older software development models.</p><p>I already had my misconceptions of quality engineering challenged, and I hadn’t even joined Salesforce yet! After hearing my interviewer’s perspective, I quickly realized quality engineering is much more than a fancy marketing tactic. Testing is more methodical and structured, and perhaps that’s why engineering organizations have embraced it more often. It produces logical, reliable, measurable results. Quality engineering, on the other hand, embraces testing, but involves a much broader realm.</p><p>It’s understanding a customer’s motivation to use a new feature. Rather than translating acceptance criteria into tests after the product is built, quality engineers are there on the front lines to question and refine requirements <em>with</em> the product owner and user experience teams. It goes beyond making a product work, to making a product beautiful, seamless, and convenient for the customer.</p><blockquote><em>In many ways, quality engineering is an art that unifies development, product ownership, and user experience with the ultimate goal to benefit the customer .</em></blockquote><p>I was recently at a Lean Quality discussion consisting of mostly quality engineers in the Salesforce Seattle office. The group was formed to bring together a community of Quality-minded software engineers across teams and product “Clouds”; share the ways that quality engineering is surviving and thriving within Salesforce; and, gather proven methods and fresh ideas to tackle the common obstacles we face.</p><p>At first, the quality engineers focused on the programmatic testing aspect by raising questions such as, “What metrics are we gathering about test health?”; and, “Has your team explored other continuous integration solutions?”. As the discussion continued, the meeting evolved into subjects such as “How are we gathering further customer insights?”; and, “How can we better measure product health in addition to test health?”. This transition served as a testament to our ever-growing quality engineering culture–one where testing, customer focus, and being agile aren’t mutually exclusive.</p><p>We know, at the end of the day, automation alone is not going to tell you if a customer is happy with using your product. Rather than treat quality engineering as an obstacle to faster product development cycles, we’ve integrated each skill required into our agile process–providing design feedback; clarifying expectations between the developer and product owner; and, providing test harnesses that developers and quality engineers can simultaneously use on a product.</p><p>At Salesforce, we are elevating this misunderstood role. We are embracing the power and art of quality engineering. While quality engineering and its similar roles have been seemingly challenged by the industry, we’ve worked hard to reinvent an engineering culture where Trust is the #1 value and product quality is everyone’s concern. Our quality engineers are looking beyond programmatic testing and pursuing thoughtful, strategic, and visionary approaches to delighting our customers. Hearing the empowered voices and genuine interest of the quality engineers at this meeting was a refreshing reminder that, while testing in the traditional sense may be slowly decaying, quality engineering as a redefined culture and movement is very much alive here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d75fab1963d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-engineering/is-quality-engineering-a-dying-art-d75fab1963d9">Is Quality Engineering a Dying Art?</a> was originally published in <a href="https://medium.com/salesforce-engineering">Salesforce Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>