<?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 Rui Da Costa on Medium]]></title>
        <description><![CDATA[Stories by Rui Da Costa on Medium]]></description>
        <link>https://medium.com/@uxrui?source=rss-13eaad1f5564------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*BA5HlsdpVCeBKEL1.png</url>
            <title>Stories by Rui Da Costa on Medium</title>
            <link>https://medium.com/@uxrui?source=rss-13eaad1f5564------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:27:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@uxrui/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[6 ways CX testing can yield higher revenue]]></title>
            <link>https://medium.com/@uxrui/6-ways-cx-testing-can-yield-higher-revenue-e7a43058ae2a?source=rss-13eaad1f5564------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7a43058ae2a</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[cx]]></category>
            <dc:creator><![CDATA[Rui Da Costa]]></dc:creator>
            <pubDate>Wed, 10 Feb 2016 18:59:54 GMT</pubDate>
            <atom:updated>2016-02-10T19:01:16.153Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Testing throughout the CX process ensures success</h4><blockquote>This post was originally published on <a href="http://www.catalystinc.com/crm/6-ways-cx-testing-can-yield-higher-revenue/">Catalyst Inc.</a></blockquote><p>Since I last wrote about <a href="https://medium.com/@uxrui/killing-the-spec-9cddfef5ad31">killing the spec document</a>, I’ve been thinking a lot about the customer experience design process. It amazes me that even with all the access to technology that marketers have, we still don’t test things as much as we should.</p><p>When I talk about testing, I’m not just talking about doing quality assurance testing. What I’m talking about is all the other testing that marketers should be doing to deliver the best experience to the customer.</p><p>There are many different testing methods. I’m going to talk about a few of the most critical, when you should use them and why.</p><h4>Baseline Testing</h4><p>This method of testing is usually done at the beginning of the CX life cycle. It requires looking at various types of users and how they interact with an existing system. If you are tracking users, a lot of that information can be used in your baseline testing. What you’re really looking for are consistent themes. Are users frequently performing the same actions? How long do certain actions take? Data gleaned from these tests can help determine potential enhancements, or even which features need to be removed or added.</p><h4>Navigation Testing</h4><p>We usually call this IA (information architecture) testing, but in most situations it really comes down to how users navigate through an interface. If you are noticing specific breaks in how users are getting to your content, it could be that they aren’t sure how to get there. By doing navigation testing, you can see how users traverse your site, how they perceive the meaning of your labels and ultimately, how they expect to get to the content they’re looking for.</p><h4>A/B Testing</h4><p>This is probably one of the most common tests that can be performed, and it makes sense: Do users respond better to concept A or concept B? The most important thing to think of when doing an A/B test is the desired outcome. You could have a test when one variant has a better response rate, but has an increased cost, while the other variant yields a better ROI.</p><h4>Design Testing</h4><p>When you start digging into the graphic design phase of a project, it is important to do some design testing to discover what users will have a better emotional reaction to. Yes, this may mean adding more up-front cost, but a better CX index score is directly related to revenue. So unless you want lower revenue, test your designs!</p><h4>Prototype Testing</h4><p>After you have started to develop a prototype or demo, it is unbelievably important to test. The earlier you test a prototype, the more insight you will have about how your methodology is being interpreted by users. Testing early also allows you to spot potential problems before you get further along in your process. When testing, it is also imperative to test with actual users, not internal resources. Actual users do and see things differently and won’t cloud your results.</p><h4>Acceptance Testing</h4><p>Sure, you have a finished product now, but does it meet all of your goals? Your users’ goals? Acceptance testing allows you to make sure you are accomplishing your goals. Make sure your UX team is in sync with your development team throughout the entire CX process. If you work together from the beginning, you can ensure that the end product meets your goals without having to do a bunch of rework.</p><p>There are other testing methods I didn’t cover (QA testing, unit testing, etc.), but these methods are the most critical to the CX design process. You may not use all of these in your process, and that’s okay. Regardless of how many testing methods you’re currently using, remember this: Test early, test often, and most important, test with <strong>real users</strong>. That’s how you get accurate data and that’s how you get better results.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7a43058ae2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Killing the Spec]]></title>
            <link>https://medium.com/@uxrui/killing-the-spec-9cddfef5ad31?source=rss-13eaad1f5564------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cddfef5ad31</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Rui Da Costa]]></dc:creator>
            <pubDate>Thu, 23 Jul 2015 17:04:34 GMT</pubDate>
            <atom:updated>2015-07-28T15:48:35.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JppD5HEnNaJ-kZ7bNqsZSg.png" /></figure><p>The spec(ification) document is an awful thing. It’s large. No one reads it. Even when developers read it, they still ask questions. All the while you’re just hoping that when you put everything together you haven’t missed something important and it all makes sense.</p><p>So how do we do it? How do we kill the dreaded spec document? The answer: build. Prototyping has the potential to make the spec document almost irrelevant. I say almost because we still need a spec; it just doesn’t need to be as big as it used to.</p><p>Let’s say you have a complicated web application that needs to be built — we’re talking dozens of pages with dynamic elements. Writing specifications for each page, each element, each interaction could be 100 pages or more if you include screenshots.</p><p>Now what happens when you build out a prototype? You can define and see all of the pages, elements and interactions. You can show this to clients and end-users for testing … all as you work tightly with your developers to refine things in real-time. This lowers the barrier for understanding how things will look and react … in tandem while getting sign-off from your client.</p><p>You may be asking, “but what about the complex interactions? or interactions you can’t see?” This is what the spec will become. It doesn’t need to define all the interactions in the prototype — just some of the more complex ones and the stuff that goes on behind the scenes: database calls, integrations, business logic, etc.</p><p>In order for a prototype-heavy process to work, you need to do 4 things:</p><blockquote>#1: Don’t overdevelop</blockquote><p>A prototype is still a prototype. You can spend a lot of time refining it and making it function like your end product but if you can get it 80% there and can explain the rest with a paragraph, that’s all you need.</p><blockquote>#2: Always be testing</blockquote><p>You can learn more from a few users and a basic prototype than if you just built something based solely on business input. This seems pretty basic but some people still don’t do it and they’re just throwing away good data.</p><blockquote>#3: Embrace the failures</blockquote><p>Through testing you will experience some quirks: an interaction you weren’t expecting; a process you didn’t account for; maybe a logic flaw. Fix or add the missing things in your prototype but remember, don’t overdevelop!</p><blockquote>#4: Show. Iterate. Repeat</blockquote><p>Just like you should always be testing, you should also be refining while you test. It’s easier to make small adjustments as you build instead of creating a complete prototype and then having to make lots of adjustments.</p><p>I know what you’re thinking, “I still have a spec document, don’t I?” You do, but not like you used to. Instead of a monstrosity of a document that is difficult to digest, you have a lean and mean document accompanied by something even better: a prototype.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cddfef5ad31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to prepare for the StartupBus]]></title>
            <link>https://medium.com/@uxrui/how-to-prepare-for-the-startupbus-800f4760d8f2?source=rss-13eaad1f5564------2</link>
            <guid isPermaLink="false">https://medium.com/p/800f4760d8f2</guid>
            <dc:creator><![CDATA[Rui Da Costa]]></dc:creator>
            <pubDate>Wed, 19 Feb 2014 03:51:25 GMT</pubDate>
            <atom:updated>2014-02-19T03:51:25.591Z</atom:updated>
            <content:encoded><![CDATA[<h4>Well…mostly.</h4><p>Congrats! You’ve been accepted to the <a href="http://startupbus.com/">StartupBus</a> because you’re probably awesome. Now you need to figure out what the hell you should bring. Here’s a quick guide to help you out.</p><h4><strong>Be clean and comfortable</strong></h4><p>You know that guy at the office that smells a bit funny? Now imagine being stuck with him on a bus for 3 days. Not fun. Don’t be that guy.</p><p><strong>Clothes<br></strong>Don’t be naked for the whole trip, it gets cold. Bring something you can be comfortable in on the bus, something for when it’s cold, something for when it’s hot, something to go out in public and something to cover you if it’s raining. If you want to be clean, bring enough shirts and underwear for each day. Lastly, flip-flops. Once you get to Texas…flip-flops are a must.</p><p><strong>Eyewear<br></strong>Contacts, glasses, sunglasses, gunnar optiks: bring whatever you need to keep your eyes relaxed enough to maintain a steady stare for 3 days.</p><p><strong>Toothbrush and toothpaste<br></strong>Also a no-brainer. You’re going to be in close proximity to a lot of people. Talking a lot. Keep your breath fresh. Brush your damn teeth.</p><p><strong>Deodorant<br></strong>Kind of a no-brainer. Easiest way to mask your stench is by literally ‘de-stenching’ yourself.</p><p><strong>Febreeze/air freshener<br></strong>There are a few long days on the bus and perfume or cologne can be nauseating to others. Sometimes just a quick spritz of Febreeze is enough to hold over the smell. These buses do have toilets…and they sometimes get a little ripe. Be a dear. Spray when you can.</p><p><strong>Baby wipes/wet naps<br></strong>The bus moves and so does everything in it. Having a set of these is nice in case you spill anything on yourself or anyone else.</p><p><strong>Water bottle<br></strong>Sometimes you might want a break from whatever caffeine, energy drink or “beverage” you’re pumping into your system. Water is a great alternative…</p><h4><strong>Bring your tech</strong></h4><p>If you don’t bring a laptop, you don’t understand how a hackathon works. That being said, there are a few other things that you can bring to make your life a lot easier.</p><p><strong>Laptop<br></strong>I guess you COULD bring a desktop PC, but that might be a little counter-intuitive.</p><p><strong>Power strips<br></strong>While this might be a dancing move, it is also a great way to make friends. People like power, so give them what they want.</p><p><strong>Chargers<br></strong>I want to emphasize this: <strong>Don’t forget your chargers. </strong>Yes there will likely be other people you can borrow power from, but bring your own charger so they can charge their stuff and you can charge yours.</p><p><strong>Wifi/Mifi/Tethered device/router<br></strong>You’re going to be driving. Signal can be pretty wonky in spots. Bring a backup internet-connected device if you need it. A router can be helpful if you just need a local connection and don’t need to worry about the interwebs.</p><p><strong>Flash drives<br></strong>Once again, the internet can be pretty fickle on the road. Transferring files between devices can be much quicker with a simple flash drive.</p><p><strong>Documentation<br></strong>This is something you don’t think about too much, until you’re on the road, with no connection, trying to remember a function call or class name or whatever you might need. I highly recommend looking at <a href="http://kapeli.com/dash">Dash</a>. Lets you pick and choose from a gigantic list of APIs and documentation.</p><p><strong>Multiple devices </strong>Bring an extra phone or iPod or tablet. Last thing you need is the phone you put your demo on to die and you’re left with no alternative.</p><h4>Other stuff</h4><p>There are some things that you just need to have on you. Not condoms, but this other stuff. Maybe condoms too.</p><p><strong>Funds<br></strong>You will need to pay for stuff so don’t forget cash, cards, bitcoins or gold. Gold always works.</p><p><strong>Identification<br></strong>Bring a photo ID just in case you forget who you are or need to tell someone else who you are. If you’re crossing a border, don’t forget your passport. That could suck.</p><p><strong>Camera<br></strong>It’s nice capturing the whole experience. You might think you don’t have time, but you’re making memories, so take a few snaps when you can.</p><p><strong>Paper/writing utensils<br></strong>Why do I need to travel back to 1997? Trust me, having a pen and paper is pretty helpful to do brainstorming. Plus, you can make paper airplanes…</p><h4><strong>Don’t forget your wits</strong></h4><p>Yes, you’ve made it so you’re probably pretty smart. I’m here to tell you to not get cocky. There are 29 other people on your bus that are just as smart, if not smarter than you, so don’t think you’re better than any of them.</p><p><strong>Ideas<br></strong>If you plan on pitching, one of these could be useful. Take note: judges aren’t just looking for an app or a website, they’re looking for a solution to a problem. Think big and be ready for those “where do you see this going” questions.</p><p><strong>Flexibility<br></strong>You may have a great idea that you think would crush everyone, but no one wants to do it with you. That’s ok. The point of this trip is to work together with other people to make something great. Find another project that you can be passionate about and roll with it.</p><p><strong>Tolerance<br></strong>There is a fine line between being a devil’s advocate and being a dick, so know when to stop and when to push back. I’m not saying to be a wuss, but don’t let arguments stop you from making something awesome.</p><p><strong>Camaraderie<br></strong>Sometimes it’s nice to help somebody else out; you never know when you might need some help too. Keep in mind, we’re all in this together.</p><p><strong>Fun<br></strong>Ultimately, this is a life-changing experience for anyone who does it, don’t forget that. Sure you might be trying to build the next Facebook or Twitter or something equally ridiculous in 3 days, just remember: have fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=800f4760d8f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My life with the StartupBus: Part 3]]></title>
            <link>https://medium.com/@uxrui/my-life-with-the-startupbus-part-3-ee4a0d8eb5bf?source=rss-13eaad1f5564------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee4a0d8eb5bf</guid>
            <dc:creator><![CDATA[Rui Da Costa]]></dc:creator>
            <pubDate>Fri, 07 Feb 2014 21:02:47 GMT</pubDate>
            <atom:updated>2014-02-07T21:32:21.944Z</atom:updated>
            <content:encoded><![CDATA[<h4>Write on my face.</h4><p><em>Continued from “</em><a href="https://medium.com/p/bb7c2e66f3bc"><em>My life with the StartupBus: Part 2</em></a><em>&quot;</em></p><p>There we all were, semi-finals done, ready to celebrate CareerMob’s win and we’re told “no beer on the bus” by our driver. Naturally we did what we knew: we decided to work on another project on the way to Austin.</p><h3>The idea</h3><p>A team came up with the idea for <a href="http://cloudspotting.co/">Cloudspotting</a> and we all thought about other ways to use the same concept. “What about writing on drunk people?” someone said. And thus, <a href="http://drunkspotting.com/">Drunkspotting</a> was born. I opened my laptop and started working on a logo, a homage to the Cloudspotting logo. We had a bunch of code from the Mexican team (or so we thought) and started working on a native app. This wasn’t like the rest of the trip. We had the entire New York bus, a bunch of the Mexican bus, and a few stragglers from the Chicago bus all working on just this one thing.</p><h3>The Hilton</h3><p>Once we got to Austin, we <a href="https://www.youtube.com/watch?v=NJiCNL8NlbQ">setup shop in the Hilton lobby</a>. It didn’t seem that weird because it was SXSW, everyone was going to be on their laptops, but not like us. We had 30+ people working on design, development, marketing, business dev and press. Within the first day we had a <a href="https://www.youtube.com/watch?v=c9swFyRY6tI">TV crew from PBS do a quick interview with us</a>, <a href="https://www.youtube.com/watch?v=Q5Lt5j9oVdE">another with Leo Burnett</a>, t-shirts, a donations campaign and we were incorporated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfE0SHOrDntvWpcmn3fdTQ.jpeg" /><figcaption>Drunkspotting HQ</figcaption></figure><h3>The finals</h3><p>In the midst of all the Drunkspotting stuff, we still had the StartupBus finals in a couple of hours. Deliverish had just assumed that we hadn’t made the people’s choice vote, so we kept hacking away on Drunkspotting. The phone rang and we were told to be ready for the finals. We weren’t prepared. We hadn’t done any work on our demo, so we decided to wing it.</p><h3>The aftermath</h3><p>After a bunch of coding and partying, it was time for me to head back home. I was a little sad. Not only had I had an awesome time building some cool stuff, I had met a whole new crew of people and now I was leaving them. I soon realized that I wasn’t really leaving anyone. We all stay in touch and I consider of bunch of my bus-mates as pretty close friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WAqAdHRlJ1Afwt8QDqxQgg.jpeg" /><figcaption>Yes. That’s Robert Scoble.</figcaption></figure><h3>The experience</h3><p>Being on the bus was one of those things that has changed my life. I’m more confident now. I respect the community even more. Hell, I’ve taken some of the things I’ve learned and applied them to my day job.</p><p>If you’ve never done a hackthon or a startup competition and have been thinking about it, <a href="http://northamerica.startupbus.com/apply/">apply for the StartupBus</a>. It just might change your life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee4a0d8eb5bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My life with the StartupBus: Part 2]]></title>
            <link>https://medium.com/@uxrui/my-life-with-the-startupbus-part-2-bb7c2e66f3bc?source=rss-13eaad1f5564------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb7c2e66f3bc</guid>
            <dc:creator><![CDATA[Rui Da Costa]]></dc:creator>
            <pubDate>Fri, 07 Feb 2014 21:02:12 GMT</pubDate>
            <atom:updated>2014-02-07T21:28:22.152Z</atom:updated>
            <content:encoded><![CDATA[<h4>On the road again…</h4><p><em>Continued from “</em><a href="https://medium.com/p/a33a4d0505d5"><em>My life with the StartupBus: Part 1</em></a><em>&quot;</em></p><p>I had partied all night with buspreneurs from my bus and from the Alumni bus. Luckily enough for me I didn’t have a hangover, I was just sore from sleeping on a random hotel room floor. My phone alarm went off in the bathroom and I realized that I might be late. I got my shit together and rushed to the meeting spot. Good news, there were a few people who were running even later than I was.</p><h3>The introductions</h3><p>We finally got everyone on the bus and started our trip. The conductors let us know how things were going to work: go to the front of the bus, tell us who you are, what you do, and if you have any ideas you want to work on. I got up, gave my spiel and hoped that somebody would like one of my ideas. No one did and I internalized a little bit of sadness, but that’s ok. If people had liked my ideas, I wouldn’t have met my team.</p><h3>The team</h3><p>One of the girls introduced herself and pitched her idea: a peer-to-peer delivery service. She wasn’t focusing on just the app or the website, she was thinking about the bigger picture of local logistics. I thought, “This is it. This is the idea I’m going to work on.” We re-introduced ourselves and I got acquainted with the rest of the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*R3t3p9A_M0eM1gllURaz9Q.jpeg" /><figcaption>Erica, Me, Wicky, and Allen. Where is Gandalf?!</figcaption></figure><p><strong>Erica Swallows:</strong> business development, slave driver</p><p><strong>Wicky Mendoza:</strong> user experience, post-it notes keeper</p><p><strong>Gandalf Hernandez: </strong>back-end developer, wizard</p><p><strong>Allen Lafuerte: </strong>graphic designer, sleep-hoarder</p><p><strong>Rui Da Costa (me): </strong>front-end developer, crazy t-shirt wearer</p><h3>The journey</h3><p>About an hour into the trip, I got nauseous. I never get nauseous so it must have been a combination of adrenaline, lack of sleep, driving and nerves. We started brainstorming and came up with the name: Deliverish. We purchased the domain and got cranking on the rest. From there it was a cycle of arguing, coding, designing, re-thinking and eventually sleeping for 2 or so hours at a time. We stopped along the way to pitch our ideas to the other teams and various “mystery guests.” By the time we hit Texas we had a working web-service, demo, presentation, and business strategy. We felt pretty good about everything…and then we pulled into San Antonio.</p><h3>The judging</h3><p>We were met at Rackspace HQ by a crowd of people, clapping and cheering us on. I felt like a rockstar, but we still had to present. We had a few kinks to iron out so we were hoping for one of the later time slots with the judges and we got it: 3rd-to-last. This meant we could finalize a few things, work on our presentation, shoot a Vine video, and relax. When it was time, we rocked our presentation and the questions the judges had for us. We were flying high.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VKOoXXnHBASTql_7Ke51_w.jpeg" /><figcaption>The crew at Rackspace ready with high-fives.</figcaption></figure><h3>The semi-finals</h3><p>The funny thing about flying high is that you crash pretty hard. When they announced the semi-finalists, we were pretty bummed that we didn’t hear our name. We were already preparing for the semi-finals as if we were a sure-thing, so we did what anyone would do: we rooted for our friends and booed the “enemy.” There was one team that we couldn’t boo though, and that was the team from Cloudspotting. The entire New York bus went a little crazy after that...</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb7c2e66f3bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My life with the StartupBus: Part 1]]></title>
            <link>https://medium.com/@uxrui/my-life-with-the-startupbus-part-1-a33a4d0505d5?source=rss-13eaad1f5564------2</link>
            <guid isPermaLink="false">https://medium.com/p/a33a4d0505d5</guid>
            <dc:creator><![CDATA[Rui Da Costa]]></dc:creator>
            <pubDate>Fri, 07 Feb 2014 20:52:08 GMT</pubDate>
            <atom:updated>2014-02-07T21:27:03.283Z</atom:updated>
            <content:encoded><![CDATA[<h4>What am I getting myself into?</h4><p>Last year I had the good fortune of being accepted into a group of miscreants known as buspreneurs, that is to say I was selected to join 29 other people to travel on the New York <a href="http://startupbus.com/">StartupBus</a>. The premise is simple: build a startup in 3 days on a bus heading to Texas. Why would anyone want to do this? Because it’s awesome, that’s why.</p><h3>The application</h3><p>I can’t remember what it was that drew me to the site, but once I saw it I had to submit my application. While I filled it out I was incredibly nervous and second guessing myself. “Is it too late? Am I good enough? How am I going to manage this?” If you’re wondering these things too, <a href="http://northamerica.startupbus.com/apply/">apply for the bus</a>. The worst that could happen is you don’t get in, but plan for the best and it <em>might</em> happen.</p><h3>The interview</h3><p>I made it! …to the interview phase. More butterflies, more nerves, and more second guessing but that was ok. My conductor made me feel at ease when he told me that I was in. He warned me that I might have to step out of my comfort zone and code a bit more on the back-end. This didn’t matter to me, I was in.</p><h3>The lead-up</h3><p>The application and interview process happened pretty quickly. I sent my stuff in and within a week I had been accepted and given my marching orders. Now I just needed to figure out how the hell this was all going to work. With a job, a daughter, a girlfriend, a life, I wondered how I would balance everything. Did I mention that this was my first foray into any kind of hackathon or startup competition? I was worried.</p><h3>The calm before the road trip</h3><p>My worries soon melted away. My boss was all about me having a great experience and maybe learning something new. My daughter’s mom and I sorted out the week I would be away. My girlfriend knew this was something I needed to do. My life? That was waiting for me on the bus.</p><h3>The happy hour</h3><p>I got to New York the day before we were supposed to leave and headed over to <a href="http://twilio.com/">Twilio</a> HQ for the meet-and-greet happy hour. This is where I met my conductor and a bunch of the other buspreneurs. All of the anxiety that I had was gone. I was here with other people who had the same thoughts as me. Who wanted to build awesome stuff, like me. I was pumped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*nr5q5jc11I4gWQWjckk7vQ.jpeg" /><figcaption>There is nothing quite like air-guitaring while scooching yourself across the floor on your back.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a33a4d0505d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>