<?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 Ioana Serban on Medium]]></title>
        <description><![CDATA[Stories by Ioana Serban on Medium]]></description>
        <link>https://medium.com/@ioanasaysgo?source=rss-2af5c509e740------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PbtYElrOLHeU4LLYjvDVQw.jpeg</url>
            <title>Stories by Ioana Serban on Medium</title>
            <link>https://medium.com/@ioanasaysgo?source=rss-2af5c509e740------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:05:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ioanasaysgo/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[Taking the plunge]]></title>
            <link>https://medium.com/@ioanasaysgo/taking-the-plunge-c77cee3b8405?source=rss-2af5c509e740------2</link>
            <guid isPermaLink="false">https://medium.com/p/c77cee3b8405</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Ioana Serban]]></dc:creator>
            <pubDate>Fri, 27 Feb 2015 00:57:57 GMT</pubDate>
            <atom:updated>2015-09-23T02:18:27.742Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDBWP899T2ARmPqkSmmdDA.jpeg" /></figure><p><em>The true story of how I wrote my first conference abstract</em></p><h4>TL;DR</h4><p>This is a day by day breakdown of how I came to write my first conference proposal. I’ll talk about what happened and how my mood fluctuated during the process. If you stick till the end, there’ll be a shiny mood graph there!</p><h4>Day 1</h4><p>I’m at home sick with an awful throat infection. I’m working from home so I dial in to a call where a couple of my coworkers, <a href="https://twitter.com/ags313">Andrzej Grzesik</a> and <a href="https://twitter.com/fmsf303">Francisco Ferreira</a>, are trying to encourage more people to speak at conferences. We each write a practice abstract and it’s fun.</p><p><strong>Mood: </strong>tired of being sick, ready for a challenge (4/10)</p><h4>Day 2</h4><p>Possibly as a result of the fever, I find myself thinking: <em>“Hey, I can do this too! If only there were someone to help me out, I bet I could talk at a conference! Too bad the submission deadline for </em><a href="http://www.associationforsoftwaretesting.org/conference/cast-2015/"><em>CAST</em></a><em> has passed.”</em></p><p>Later that day, I’m on Twitter and I come across the <a href="http://speaking-easy.com/">Speak Easy</a> program. Started by two amazing ladies, <a href="https://twitter.com/charrett">Anne-Marie Charrett</a> and <a href="https://twitter.com/FionaCCharles">Fiona Charles</a>, Speak Easy promises to help inexperienced speakers like myself by pairing them with a mentor. And I could still submit a proposal for CAST through their program!</p><p>It takes me 2 minutes to fill in the online form. I’m terrified of public speaking. There are 4 days left before the deadline. I did not think this through.</p><p><strong>Mood: </strong>delusional and optimistic (6/10)</p><h4>Day 3</h4><p>I am assigned a mentor. His name is <a href="https://twitter.com/Carsten_F">Carsten Feilberg</a>. I do not know him personally, but I had read <a href="http://carstenfeilberg.blogspot.dk/2015/02/im-officially-mentor.html">his blog post on becoming a mentor</a>. It’s a great read and he talks about the how scary and unnerving it was for him when he first started speaking at conferences. I can relate to that and am excited to start working together.</p><p><strong>Mood:</strong> excited (7/10)</p><h4>Day 4</h4><p>A flurry of emails ensues. I pitch Carsten 3 ideas and we narrow it down to one to work on for the conference.</p><p><strong>Mood: </strong>happy, so far this is easy (8/10)</p><h4>Day 5</h4><p>I make a mind map of the key points of the presentation and send it over to Carsten. Then comes the part of translating that into an abstract to submit to the committee. We move the action to Google Docs. We talk over Skype chat about structure, length and what things to keep in mind. By the day’s end I have a first draft and I get my first round of feedback.</p><p>So far so good, right?</p><p>The problem is, although the feedback is constructive and sensible, I feel there is a disconnect. My mentor and I see the presentation differently. We argue over IM, as I try to explain better what it is I want to talk about. At the time, to me it feels a little like an angry rant. My mentor, however, thinks that the rant is more clear and passionate than the abstract.</p><p>Finally, I feel we are on the same page. We part on a high note: scrap the abstract, try again tomorrow! However, by now I feel mentally tired and doubt has started creeping in.</p><p><strong>Mood:</strong> conflicted (5/10)</p><h4>Day 6</h4><p>The abstract weighs heavily on my mind. It’s Sunday and it has to be ready by tomorrow when submission closes.</p><p>I do another rewrite and try to make it flow more like a story, as per Carsten’s advice. At this point, I’m neither confident I’ve done a better job nor am I really pleased with the new version.</p><p>I send it over to my mentor for more feedback.</p><p><strong>Mood:</strong> exhausted (3.5/10)</p><p>The feedback comes back. There’s plenty of good in it. The abstract is clearer and more readable. It just needs a little more work. However, by now my mind can only focus on the negative. I scan the feedback again and all my eyes zoom in on are the bad parts, taken out of context: <em>“too superficial”, “not enough detail”, “perhaps you want to boost your subject to a higher level than it actually is”, “reads too much like a list”, “too many </em><strong><em>I</em></strong><em>’s”, “not enough passion”.</em></p><p>I tell Carsten I’ll work on it some more.</p><p><strong>Mood:</strong> depressed (1/10)</p><p>I do not work on the abstract. Instead, I spend the next hour and a half having a complete meltdown. I feel like a failure. I wonder if the real problem is that my talk just isn’t good enough. I cry.</p><p>Finally the realization hits me. The reason I’m so miserable is that all this time I’ve been trying so hard to please my mentor, when I should have been focusing on writing an abstract that <strong><em>I</em></strong> was happy with. The whole reason I was writing this proposal was to talk about something that I am passionate about. Somewhere along the way I had forgotten that.</p><p>I write Carsten an email explaining how I’d been feeling and that I was going to <em>”take a break, go out for a burrito, come back, write an abstract I’m happy with, get a second opinion too while I’m at it”.</em></p><p><strong>Mood:</strong> determined (6/10)</p><p>I come back after my break, sit down and hammer out a new version of the proposal, incorporating my mentor’s feedback where I feel appropriate. I look at it and, for the first time, I am pleased.</p><p>I contact Carsten and tell him not to worry that I was so upset earlier, since it was not his fault. I present him with the latest version of the abstract and to my relief, he likes it! All that’s left is to hack it down to a smaller size.</p><p><strong>Mood</strong>: let’s do this! (8/10)</p><p>After some rephrasing and simplifying, and one last round of feedback the abstract is <em>finally</em> ready.</p><p><strong>Mood:</strong> elated, I do a happy dance around the house (10/10)</p><h4>Day 7</h4><p>And on the 7th day I rested. And sent in the abstract, thanked Carsten again for all his hard work and told him how lucky I was to have his support!</p><p><strong>Mood:</strong> accomplished (9/10)</p><h4>Takeaways</h4><p>Writing your first conference proposal is <strong><em>hard</em></strong>. Writing it in 3 days makes it even harder.</p><p>We tend to put a lot of pressure on ourselves and no matter how confident you start out, there is always room for self-doubt to creep in.</p><p>Working with someone you don’t know as a mentor is challenging. It’s hard to put your trust in a complete stranger while still remaining true to yourself. It is also incredibly rewarding and I have learned so much during the process.</p><p>Setting an ambitious goal and actually reaching it feels amazing. You feel like you can accomplish anything. <em>Hint:</em> I’ve written another abstract since! (Shout out to <a href="https://twitter.com/ags313">Andrzej</a> who helped me!)</p><p>Sometimes, you just need to take a break, go out and eat a burrito! That’s what marked the turning point right there on the mood graph on day 6.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xCI79dYG4KDXK4hu2HbM0g.png" /></figure><p>If you’ve made it this far, thank you for reading. Sometimes people make things look easy, so finding out that they are struggling too can be comforting. I hope sharing my experience is helpful and encourages others to take the plunge, and go for their goals.</p><p><strong><em>And just in case you happen to be a lady like me that wants to speak at an event, Carsten is a kick-ass mentor and I wholeheartedly recommend working with him and the </em></strong><a href="http://speaking-easy.com/"><strong><em>Speak Easy</em></strong></a><strong><em> team.</em></strong></p><p><strong><em>Edit:</em></strong><em> My abstract got accepted and there is actually a recording of my talk, Taking Control of Your Test Environment, that you can watch </em><a href="https://www.youtube.com/watch?v=ufZ4tDSgvv8"><strong><em>here</em></strong></a><em>. It has knights, castles and quests in it!</em></p><p><em>Also, if you enjoyed this post, please consider hitting the recommend button!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c77cee3b8405" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Resident Expert]]></title>
            <link>https://medium.com/@ioanasaysgo/the-resident-expert-a757e91c9565?source=rss-2af5c509e740------2</link>
            <guid isPermaLink="false">https://medium.com/p/a757e91c9565</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[experience]]></category>
            <dc:creator><![CDATA[Ioana Serban]]></dc:creator>
            <pubDate>Fri, 29 Aug 2014 17:07:38 GMT</pubDate>
            <atom:updated>2015-03-01T02:42:49.149Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*DZkLOpv1zwpvUqnJfMuPOQ.jpeg" /></figure><h4>What’s a “resident expert”?</h4><p>I came across the idea of a “resident expert” during <a href="https://twitter.com/testchick">Alessandra Moreira</a>’s excellent talk at Let’s Test – The DIY Guide to Raising the Test Bar (slides <a href="http://lets-test.com/?page_id=2035">here</a>). She was talking about the fact that you do not need to be an expert in order to share your experience. This sparked a discussion in which <a href="https://twitter.com/jamesmarcusbach">James Bach</a> made a point that really drew my attention. He talked about being a resident expert in this way (I’m grossly paraphrasing):</p><blockquote>If I am in a room with <a href="https://twitter.com/sbarber">Scott Barber</a> and you wanted the expert on performance testing, he’d be the expert. If I am in a kindergarten, and you wanted the expert on performance testing, I’d be the resident expert.</blockquote><p>Which is to say that being a resident expert does not necessarily mean that you are the ultimate expert at something, just that you are further along in the learning journey than others around you.</p><h4>How I became the resident expert for performance testing in my organization</h4><p>Just like a lot of people answer when asked how they came to be a tester, I sort of fell into it. When I joined Adobe as a tester, our project was young and didn’t have any clients in production. No one gave performance a second thought, it was all about adding new functionality. Performance testing was something viewed as a “nice to have” and was seldom done (usually in the form of JMeter scripts run by a dev against his local environment). It didn’t really fit anywhere in our Sprint. As for me, this was my first job out of college and I was basing my activities as a tester mostly on my manager’s expectations. I viewed performance testing, like the rest of my team, as something that other people did, not part of my responsibilities.</p><p>Of course, time passed and the project grew. Then one day disaster struck! A performance issue causing downtime in production! <em>Now</em> we need to do performance testing! And by the way, did we mention it needs to happen by the end of the week?</p><p>After 3 days locked in an office (to minimize distractions, not against my will!) with a shiny new load testing tool that no one had any experience with and a heap of online tutorials, I had cobbled together a test scenario that we used to reproduce the production issue. Then came a lot of focused work on performance tuning and, over multiple iterations, we managed to finally get out of the proverbial woods.</p><p>Rather than putting this experience behind us and waiting for the next catastrophe to strike, we chose to learn from our mistakes and incorporate performance testing into our work. One year later, our team runs performance tests every sprint on each release candidate, we run focused testing for specific features, we’re looking at new ways to trend performance.</p><p>Of course, in the beginning I spearheaded all performance testing efforts for our team since I was “the only one who knows what she’s doing”. Then came a training for the other testers in our org, a presentation for the whole campus, testing the new shiny architecture for our project’s move to Amazon and, recently, “consulting” work for one of our teams in the States to help them with their move to AWS. All this kind of cemented my reputation as “resident expert” within our organization.</p><h4>How resident experts can make a difference</h4><p>There are, of course, perks to being seen as the “resident expert” for something. For instance, being the sole engineer in a meeting with both the VP and Senior VP of your organization and being praised for your report afterward. I’m not going to lie, this kind of visibility feels good! Maybe sometimes you get to play the hero (identifying a key performance issue on a new feature early, in time to fix it before releasing it in production) or the villain (giving a NO-GO for a release that would impact performance). However, what feels really great is seeing how your work has made a difference.</p><p>In my opinion, there are 2 main ways in which resident experts can make a difference:</p><p><em>Spreading their knowledge</em></p><p>As “resident expert” you recognize that you have a looong way to go until actually <em>being </em>an expert. However, I feel it is your responsibility to help others around you who are just beginning their journey! Instead of hoarding the knowledge I’ve gained, I’m a big fan of an <em>‘If I can do it so can you! It’s easy! I’ll help you!’ </em>attitude that I think coaxes my fellow colleagues to overcome their initial anxiety about learning a new tool or skill.</p><p><em>Spreading their enthusiasm</em></p><p>A magical thing happens when you care a lot about what you do and are vocal about it. Slowly but surely, you get to infect other people! Right now not only am I not the only person running performance tests in my organization, but I am not the only person driving these efforts either! Managers are asking about performance testing! Developers are concerned with how their changes are impacting performance! Even the operations guys are peeking their heads out of their office to see what we’re doing! We’re getting closer to building an ecosystem where <em>everyone</em> is responsible for performance! I have confidence that even if I leave, the testing will go on!</p><p>Sure, you don’t get there overnight, but constantly engaging the team in conversations about an issue raises everyone’s awareness of the subject. And it can be as easy as going up to someone and saying: ‘<em>Hey! Wanna see something cool?’ </em>Then pull them over to your workstation and show them what you’re working on! A shiny graph or an insightful interpretation of some results that tells them something they don’t already know is usually enough to get the ball rolling!</p><p>So in the end, am I an expert on performance testing? — Certainly not. Am I any good at it? — Who knows? Have I made a difference? — Definitely! And I think that’s what really counts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a757e91c9565" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting a blog]]></title>
            <link>https://medium.com/@ioanasaysgo/starting-a-blog-b24eb1c99b25?source=rss-2af5c509e740------2</link>
            <guid isPermaLink="false">https://medium.com/p/b24eb1c99b25</guid>
            <dc:creator><![CDATA[Ioana Serban]]></dc:creator>
            <pubDate>Thu, 14 Aug 2014 16:22:15 GMT</pubDate>
            <atom:updated>2014-08-14T16:22:15.012Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nVmjro6BVLjEewIJXxt9Cw.jpeg" /></figure><p>Since going to the <a href="http://lets-test.com/">Let’s Test</a> conference and joining Twitter this year I’ve met a lot of wonderful people in the testing community and have greatly enjoyed following their tweets and reading the content they post online on their blogs.</p><p>So today, I’ve decided to take the plunge and open up a space for sharing my stories and insights about Software Testing.</p><p>For those who may not already know me, my name is Ioana Şerban, I live in Bucharest, Romania and I work as a Software Tester for Adobe. That’s about it!</p><p>I hope you’ll stick around for the ride! There’s an <em>actual</em> post coming soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b24eb1c99b25" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>