<?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 Aaron Henshaw on Medium]]></title>
        <description><![CDATA[Stories by Aaron Henshaw on Medium]]></description>
        <link>https://medium.com/@aaronhenshaw?source=rss-5a629b6f1666------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kc_wH7P1g2m8SClY_iJEtg.png</url>
            <title>Stories by Aaron Henshaw on Medium</title>
            <link>https://medium.com/@aaronhenshaw?source=rss-5a629b6f1666------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:05:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aaronhenshaw/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[Continuous Delivery the easy way (Part 1)]]></title>
            <link>https://medium.com/@aaronhenshaw/continuous-delivery-the-easy-way-part-1-e7de4a4e4081?source=rss-5a629b6f1666------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7de4a4e4081</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[tutum]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Aaron Henshaw]]></dc:creator>
            <pubDate>Thu, 24 Sep 2015 15:34:44 GMT</pubDate>
            <atom:updated>2015-09-24T15:34:44.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ztEmiR_U2Vhlpt4kIoPiSQ.jpeg" /></figure><p><strong><em>Or: </em></strong><em>How using Docker &amp; Tutum enables you to set up a simple application server that automatically builds and deploys when you perform a Github push without doing a ton of work.</em></p><p>While I was tinkering with a side project, I realized while continuous delivery has made me a better developer, it has ruined me at the same time. I can’t live without it. I now *need* a fast, automated and easy way to push to production after committing my code.</p><p>The problem is when I am working on a side project, I don’t get a DevOps department to build tools and infrastructure to manage this process. So what does a single developer or small team to do when working on a little side project?</p><p>I started poking around for automated continuous delivery solutions. There are a bunch of these out there but somehow I landed on <a href="https://www.tutum.co/">Tutum</a>. Their beta product is a Docker + GitHub + Cloud Services connector. Meaning they have built a solution that will build, deploy and manage your applications in the cloud. All you have to do is click a couple buttons. (Ok, maybe its not quite that easy. But its close.)</p><h3>Setting up my first Dockerfile</h3><p>Docker is a platform for building, shipping and running distributed applications. It uses instruction files (Dockerfiles) that can build on top of other pre-built Dockerfiles files, all so you can quickly deploy these little VMs called containers to wherever you want. For example, if you wanted to create a <a href="https://hub.docker.com/r/reinblau/lamp/~/dockerfile/">LAMP Dockerfile</a> you would pick a base image, say Ubuntu, and then issue a bunch of apt-get install commands for php, mysql, and apache. You then package this into a new image.</p><p>When deploying changes, build + deploy speed is everything. The cool thing is, if you do it right, deploys won’t need to re-install Ubuntu, it has that already. It doesn’t even need to install LAMP again. You can design it so that the deploy only installs your latest code and starts the server.</p><p>Cool. But how does it actually work? At first I really wasn’t sure so I figured the best way to find out is to build some Dockerfiles myself. My goal was to create a file that first installed <a href="https://grails.org/">Grails</a> on top of Ubuntu, then pulled my private repo and finally started the application so it could be accessible via https.</p><h4>Docker Base + Grails Install</h4><p>With Ubuntu Trusty as a base I used apt-get to install some dependencies, installed <a href="http://gvmtool.net/">GVM</a> (this is a Groovy environment manager), and lastly installed Grails. Having a local install of Grails is necessary to either build or run the application. Running <em>grails -v</em> downloads some common grails components.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc8a0ec2b61e9d831185224710609f48/href">https://medium.com/media/cc8a0ec2b61e9d831185224710609f48/href</a></iframe><h4>Pull my private GitHub repo</h4><p>In a separate Dockerfile, that I start from a base of the Ubuntu + Grails Dockerfile I created above, I install ssh keys (not so sure this is the most secure thing but it works for now) and added github.com to the list of known hosts. Then I clone my repo into my project directory.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c5ecaa3187f075b730a1c82d708c288e/href">https://medium.com/media/c5ecaa3187f075b730a1c82d708c288e/href</a></iframe><h4>Start Grails application</h4><p>Now that I have my project pulled locally, I just need to clean the app and start it using the CMD Docker command. You can put a ton of different <a href="http://grails.github.io/grails-doc/2.0.4/ref/Command%20Line/run-app.html">grails</a> or <a href="https://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionX.html">Java</a> parameters when starting your grails app but for now I only have it set to enable https.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9387ce079361967d169f7137670cf587/href">https://medium.com/media/9387ce079361967d169f7137670cf587/href</a></iframe><p>The first time I did this I put all of the instructions in a single file and deployed that. It took ~18 minutes to build. After separating it into two files, it now takes about 2–3 minutes to build and deploy. Once I got the build working locally that quickly, I decided it was time to automate builds to something in the cloud.</p><h3>Setting up Tutum</h3><p>I have to admit that I have only scratched the surface of using Tutum and Docker together. I will be writing a follow-up post that explains adding nginx and MySQL in a stack that properly orchestrates deploys of the app. But even what I have setup so far is pretty cool and useful.</p><h4>Setup a Tutum Repository</h4><p>This is really straightforward. All you do is create a repository on the Tutum side and then tell it which one of your Github repos you want to sync from. That repo just needs to have your deploy Dockerfile at the root.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*s1giQThGwWM9sTBU8U9YMw.png" /></figure><p>Setting auto-build means that every time you push to your selected branch (in this case master) your app auto builds and deploys.</p><h4>Docker Node + Service</h4><p>Next you link your Tutum account with your favorite cloud hosting solution. I used Amazon EC2 and created two nodes. Then create a service, select the Repo you set up earlier and edit any environmental variables you want to.</p><p>After you do this, you just launch your Service and boom — It takes the latest build from your repo and deploys that container to that Node you created. As long as you expose the right ports, you can immediately access your application from a browser. And any time you push to github, your app will auto-build and deploy so you can see your changes right away.</p><h3>Whats Next?</h3><p>Now that I have this working I would like to set up a simple 3 node stack that looks something like this:</p><ol><li>Nginx</li><li>App Server(s)</li><li>MySQL Server</li></ol><p>I want it so when I do a git push, the App Servers all auto-deploy and then both the nginx routing to the app servers and the app servers connections to the MySQL servers are all swapped and reconnected correctly. From what I gather, Tutum does this with <a href="https://support.tutum.co/support/solutions/articles/5000539711-12-service-stacks">Stacks</a>. But I don’t really know yet :-) More to come next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7de4a4e4081" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Same fight, different round]]></title>
            <link>https://medium.com/product-etc/same-fight-different-round-a1c9908ae984?source=rss-5a629b6f1666------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1c9908ae984</guid>
            <category><![CDATA[allen-iverson]]></category>
            <category><![CDATA[acquisition]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Aaron Henshaw]]></dc:creator>
            <pubDate>Mon, 10 Aug 2015 19:09:10 GMT</pubDate>
            <atom:updated>2015-08-10T19:09:10.499Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UM5Z3SZBywb5PpyUax36TQ.jpeg" /><figcaption>Allen Iverson: Arguably the best pound for pound basketball player we have ever seen.</figcaption></figure><p><a href="http://espn.go.com/nba/story/_/id/13301540/allen-iverson-poignant-nbpa-players-awards-speech-worth-remembering">Allen Iverson recently gave a humbling speech</a> where he talks about life and its ups and downs. He compares life to a title fight, where each phase is a different round. This made me think a lot about starting Grand St. and selling to Etsy.</p><p>In his speech, Iverson says, “Some days you gonna get knocked down and some rounds gonna be good, some gonna be bad. But the only thing that matters is getting back up and fighting again”.</p><p>When you start a company, it is really important to keep reminding yourself of that. It’s all just one big fight and you have to get up, over and over again, regardless of the situation.</p><h4>Round 1: Take the jump</h4><p><a href="https://twitter.com/joelallouz/">Joe</a> and I had a plan on how to quit our jobs. Instead we got fired.</p><p>With no cash and no job there was no time to lose — we got to work right away. Having our plan blow up could have sucked. But getting fired was one of the best things that happened to us. We had been gifted a forcing function: there was no turning back, no real options but push forward into the unknown world of starting a company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2BkianvI8d98zeuuhHcmiA.jpeg" /><figcaption>“Good luck exploring the infinite abyss.”</figcaption></figure><p>We had an idea for a website that would sell cool electronics. Maybe. Or maybe we would take on the used furniture vertical within craigslist. Thankfully, we decided to go with the first one. <a href="https://grandst.com/">Grand St.</a> was born.</p><p>It wasn’t easy, but we scraped together some money and made the beginning work. 401ks were cashed in and friends and family were asked to be part of our journey.</p><h4>Round 2: Launch, Raise a seed round</h4><p>We managed to launch and close our seed round on the same day. It was so much fun but it was also a grind. Staying focused on the product while continuously adapting our pitch was a challenge. At this stage its not so much about the initial implementation as it is about the dream. And we dreamed really big.</p><p>All the wires came in on time and our launch was a success. This round was a win. It was really hard, but it was fucking awesome.</p><h4>Round 3: First business model, more fundraising</h4><p>Our initial business model was event-based commerce. Fab in its early days is the best example. We took inventory, we had a warehouse. It was all about the customers end-to-end experience.</p><p>Sounds nice right?</p><p>Then came inventory risk. At certain points we had hundreds of thousands of dollars tied up in inventory. At an early stage and with only a modest seed round raised, it was a mistake to allocate capital in such an illiquid way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*GuBV4XSXHTow_dxhfAOhMw.jpeg" /><figcaption>Mayweather is 48–0.</figcaption></figure><p>We managed to do over a million dollars in revenue our first year but given the comps at the time, that wasn’t good enough to raise money. As an entrepreneur, this is devastating. But we couldn’t give up so we got back up.</p><h4>Round 4: Pivot to marketplace, launch (again)</h4><p>Venture debt bought us enough time to build a marketplace focusing on early hardware — specifically Beta and Pre-Order products. From everything we learned about innovative hardware products, it felt like a good move. And it was.</p><p>Long nights and weekends were spent re-writing and re-structuring our entire business. We did it in under 3 months with a very small team.</p><p>Launching was certainly a high. Our team came together and accomplished something awesome. And it looked really good :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xsguR_54n524UmdqET90Wg.png" /></figure><h4>Round 5: Raise on our sweet pivot</h4><p>Grand St. now had buyers and sellers interacting without inventory risk or logistics support. We went out to get some more money. Signs were positive, but we didn’t have a ton of data yet.</p><p>At the same time, we heard from all the usual big tech companies, potentially looking for us to join them. We didn’t love the way that would shake out — breaking our team apart and spreading through a bigger org. We indirectly initiated these conversations. Since they weren’t looking at the business this taught me a valuable lesson —</p><p><strong><em>Companies are bought, they are not sold.</em></strong></p><p>In the end, we got a venture term sheet for our new marketplace. We still believed in the vision and the team and were going to take the funding.</p><h4>Round 6: Selling to Etsy</h4><p>Out of nowhere, Joe met with Randy, the VP of Design at <a href="https://www.etsy.com/">Etsy</a>, and quickly was on the phone with Kellan, the CTO, negotiating an offer. The deal they offered was unlike any of the others. They loved the marketplace work we had done. They wanted us to come to Etsy and do the same type of product development work there,<strong> as a team</strong>.</p><p>We weighed the options and went for the acquisition. This started the hardest three months of my professional life. Closing was insane. It almost didn’t work out. Many times. And all the while you have peoples lives hanging in the balance. But we did it.</p><p>It was ~2 years from getting fired to selling. A serious ride of ups and downs. But one I wouldn’t give up for anything. I learned more in that 2 years than I did in all my other professional and schooling experience combined.</p><h4>Round 7: Welcome to Etsy</h4><p>The announcement came and we showed up at this relatively big company, ready to take on some awesome problems. But it was a slow process. Trying to figure out how and where we fit took some time.</p><p>I learned a lot during this time. One big takeaway from the acquisition was:</p><p><strong>You can’t force people to change overnight.</strong></p><p>The management taught us this valuable lesson in giving us the space and time to figure our shit out; to figure out how we fit at Etsy.</p><p>Taking our knowledge of early hardware and crowdfunding, we launched our first product here — <a href="https://www.etsy.com/fund-on-etsy">Fund on Etsy</a> in June 2015.</p><p>We realized our experience put us in a unique position where we are good at building new and innovative products, with some inherent risk and uncertainty. So we established the Maker Innovation team to do exactly that.</p><h4>Round 8: ????</h4><p>Whats next? I don’t really know. We have nearly doubled the size of our team (tripled engineering) and are working on some really exciting products. There is still a lot to learn and cool things to build.</p><p>Every change is an opportunity to grow, to learn something and to do great work. We never let any ups or downs stop us. Like Iverson says, whatever happens, you have to always, always, get back up and keep fighting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1c9908ae984" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-etc/same-fight-different-round-a1c9908ae984">Same fight, different round</a> was originally published in <a href="https://medium.com/product-etc">Product, etc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recipes for successful team culture]]></title>
            <link>https://medium.com/product-etc/recipes-for-successful-team-culture-e71d52ee76dd?source=rss-5a629b6f1666------2</link>
            <guid isPermaLink="false">https://medium.com/p/e71d52ee76dd</guid>
            <dc:creator><![CDATA[Aaron Henshaw]]></dc:creator>
            <pubDate>Sun, 26 Jul 2015 22:33:50 GMT</pubDate>
            <atom:updated>2015-07-26T22:33:50.993Z</atom:updated>
            <content:encoded><![CDATA[<p>Culture is an essential part of any team or company. And it goes hand-in-hand with the processes they use. All of it adds up to the type of team or company you are. It’s part of your identity and the main influence on happiness and performance.</p><p>On the Maker Innovation team at <a href="https://www.etsy.com/">Etsy</a>, we constantly work on our culture and processes. Below is a list of what we do on our team for product development and culture, and why we find them useful.</p><h4><strong>1:1s (One on ones)</strong></h4><p><em>Frequency: 30 min-1 hour Weekly</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CV_fgbqnEh-UHu3iaIsLXQ.jpeg" /><figcaption>1:1s are not for fighting</figcaption></figure><p>In order for 1:1s to be effective, regardless of the size of the team/company, the entire crew needs to be onboard. Otherwise they don’t work.</p><p>Our team does two types of 1:1s — Direct report 1:1s and cross team 1:1s.</p><p><strong>Direct Report 1:1s<br></strong>Initially I was skeptical of having to meet with every person on my team once a week. But I quickly came around. It is a great way to build trust with the people on your team. The meetings can focus on anything. Common subjects are inter-company issues, career and personal development. Technical discussions are generally off the table — we do that all day already.</p><p>1:1s make sure that information is always flowing up and down through the organization. If someone on my team encounters an issue that I can’t resolve on my own, there is a maximum of a week before I have scheduled time with my manager to surface that issue. Same goes in the other direction.</p><p>I have been informed of personal issues, hidden underneath what appeared to be slacking or general unhappiness. Once, an 1:1 exposed a UX problem where our teams work was in conflict with another teams product plan. 1:1s have surfaced problems with title and salary. In all these situations the 1:1 identified and helped to quickly resolve an issue before it got worse.</p><p><strong>Cross Team 1:1s</strong><br>Cross team 1:1s are meetings that we have between engineering, product, design, marketing and program management. They happen at all levels and they are focused on three things:</p><ul><li>Collaboration: We often schedule 1:1s between design &amp; engineering or product &amp; engineering to talk through product decisions and discuss direction. This is usually a designer and an engineer walking through a product making tweaks and sweating the details.</li><li>Strategy: Sometimes shit hits the fan. 1:1s at the leadership level are instrumental in providing time to discuss strategy on how to handle organizational problems that come up.</li><li>Alignment: Etsy is a growing company — the leaders on our team deal with different internal stakeholders from other parts of the company. By making sure that we meet often we are able to provide a consistent message across the organization.</li></ul><h4>Weekly Fuck-ups</h4><p><em>Frequency: 1x/week</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S9KCGuyIU0HDg09gqpmp3w.jpeg" /><figcaption>We give two of these flags out every week to whoever fucked up the worst.</figcaption></figure><p>Once a week, everyone on the team discusses their biggest failure that week, and as a team we vote for who fucked up the most. The person who “wins” has to keep a flag at their desk for the week.</p><p>People get the flag for things like taking down a page in production, pushing bad code, or missing meetings. They also are given for personal fuck-ups like getting lost and missing their best friends birthday party. For more about fuck-ups, check out Kuan’s post called <a href="https://medium.com/product-etc/trust-the-creative-process-a11facb03095">“Trust the Creative Process”</a>.</p><p>It is playful but its really about owning up to your mistakes, admitting them and learning from them. Accountability is something that we take very seriously on our team and this is a fun way of making it part of our culture.</p><h4>All Hands</h4><p><em>Frequency: Weekly<br></em>At the end of the day on Monday we have a stand-up meeting focused entirely on feelings. No work talk is allowed. You can feel good about work or a project, but nothing can be said about the specifics of what you have done or are going to do. Mostly people talk about their weekends, or about things they are excited about.</p><p>The important thing here is that we are all people. Work is not life, it is just a part of life. Creating opportunities for empathy and a shared understanding of how everyone is feeling, and why, sets everyone up for a better week.</p><h4><strong>JIRA &amp; Milestone planning</strong></h4><p><em>Frequency: Milestones/sprints every 2–3 weeks &amp; interact with daily</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SbbrnjE8bpHcyPXXx-9iKw.png" /><figcaption>“Oh, oh, and I almost forgot. Ahh, I’m also gonna need you to go ahead and come in on Sunday, too…”</figcaption></figure><p>When it comes to software development, you can’t grow a team past a certain size without using some sort of project management software. Nobody likes tracking software development, but unfortunately it’s necessary. To make it work for our team, we are open about not liking heavy-handed project management. We focus on iterating, always searching for the right balance of process and autonomy.</p><p>Our team recently completed and launched <a href="https://www.etsy.com/fund-on-etsy">Fund on Etsy</a>. Because we were building directly into a complex eco-system that needed consistency across 6 platforms we created a lot of feature tickets, sometimes one per platform per feature. They were very specific with requirements and implementation details embedded.</p><p>Product-wise, it worked well. People-wise, not so much. It was too heavy-handed for our team. It removed a lot of the decision making away from the individual engineers. Seeing that, we decided to take a different approach for our next project.</p><p>We refocused all of our project planning on short, result-driven milestones. At the end of a 2–3 week milestone the team has something new that is demo-able. The whole team works on smaller, discrete pieces, and every engineer is challenged to think through product problems.</p><p>Sometimes it feels chaotic. But that chaos is awesome. It is real collaboration. You can see the energy, excitement and engagement that everyone has when the team is all working together.</p><h4><strong>Milestone Demos</strong></h4><p><em>Frequency: At ends of milestones, every 2–3 weeks<br></em>At the end of a milestone, we plan an internally open demo where we present the work the team has done to anyone who is interested.</p><p>Our team demoed the first milestone to product, design and technical leads and everyone was blown away. What our team was able to build in only two weeks was remarkable. Creating tangible goals and realistic deadlines, where the team is accountable to stakeholders outside the team, is pretty powerful.</p><p>It was especially cool to see everyone rally in a way that was similar to a more public release, a couple days before our demo. We had a day or two of all hands on deck bug fixing and clean-up. We even had a code freeze.</p><h4>Objectives &amp; Key-Results (OKRs)</h4><p><em>Frequency: Set quarterly, discuss monthly</em><br>We have started using OKRs on our team. There is a <a href="https://www.youtube.com/watch?v=mJB83EZtAjc">great deal</a> <a href="http://firstround.com/review/How-to-Make-OKRs-Actually-Work-at-Your-Startup/">of info</a> <a href="http://eleganthack.com/the-art-of-the-okr/">out there</a> for OKRs. I can’t say if they are right for us but we are going to try them and see what happens.</p><p>To start, everyone set their own OKRs for the quarter and went over them with their manager. So far its awesome. The objectives are diverse but they all build to a successful project or to individual development. They range from <em>“Provide technical leadership for the team”</em> to <em>“Obtain a mastery of data and analytics reporting for products”</em> to <em>“Learn to run meetings more effectively”</em>.</p><p>The goal is to push people in a way that aligns objectives between project work, team success and individual development. The part that appeals to our team the most is that the key results are measurable.</p><p>For example, <em>Obtain a mastery of data and analytics reporting for products”</em> has a key result of <em>“Make sure our Q3 project has 100% event tracking coverage”. </em>We can concretely measure success for that. The individual engineer, if successful, will get a new skill for their career. And it isn’t just important for them individually. It will impact the success of our project.</p><h4>Field trips</h4><p><em>Frequency: Every month or two</em><br>Every month we take a day off and do something fun around NYC — it is important to remind ourselves that we have relationships separate from work and to create opportunities to form new bonds. Oh, and its just fun. We have done things like <a href="http://www.museumhack.com/">Hack the MET</a>, <a href="http://www.moma.org/visit/calendar/exhibitions/1380?ref=binfind.com/web">The Rain Room</a>, <a href="http://www.movingimage.us/">Museum of Moving Image</a>, <a href="http://www.cooperhewitt.org/">Cooper Hewitt</a> (yes lots of museums), beer gardens, <a href="http://ny.eater.com/2014/5/8/6228339/you-guys-mission-chinese-at-frankies-457-totally-rocks">Mission Chinese Pop-Up</a>, <a href="http://giphy.com/gifs/spring-breakers-james-franco-ru9ckt3ZvF7j2">movies</a>, and <a href="http://newyork.seriouseats.com/2011/02/flushing-sannakji-live-octopus-at-sik-gaek.html">eating live squid</a>.</p><h4><strong>Design Weekly</strong></h4><p><em>Frequency: 1x/week</em><br>This is my favorite. Our designer, <a href="https://twitter.com/kuanluo">Kuan</a>, created a meeting every week that is focused on creative energy and design. We stretch. We do improv. We talk about the specific products and UIs we are working on.</p><p>We do brainstorming sessions: once we broke into pairs and did individual UX research on how the other person liked to receive gifts. At the end of the exercise we had designed a gifting process specifically for that other person, tailored completely for their needs. Earlier on in building Fund on Etsy, Kuan brought color markers and paper to a design weekly, and we all sketched out different screens for the product.</p><p>We discuss design and product inside and outside Etsy, trends, typography, and much more. Once we learned about <a href="http://desktoppub.about.com/od/glossary/g/Kerning-Pairs.htm">kearning pairs</a>. Or the <a href="http://mindgruve.com/blog/advertising/typeface-vs-font-whats-the-difference">difference between a font and a typeface</a>. It gives Kuan an opportunity to provide context around how she thinks about product design. And like everything else we do, its an opportunity for people to learn and grow.</p><p>Sometimes we do product demos. Individual engineers are encouraged to present their individual work to our team. We have recorded those demos and provided feedback on presentation skills. It allows everyone to work on getting better at things we don’t do every day as engineers. And who doesn’t love a good demo??</p><p>Overall, this is a great way to share, learn and give everyone an opportunity to be engaged in a design-focused way that doesn’t happen every day.</p><h4>Team off-sites</h4><p><em>Frequency: 1–2x/year</em><br>Taking a trip away from the office once or twice a year is very good for a team. Trips can focus on a work goal or they can be purely social. One off-site we had two new team members. Over the next two weeks, they became just as much a part of the team as anyone else. During off-sites focused on work we performed like a well-oiled machine. But whatever the focus was the team building was the important part.</p><p>Off-sites can seem excessive, but they aren’t. Do them. Effective off-sites are well worth the cost.</p><h3>“Recipes not blueprints”</h3><p>I came across <a href="http://blog.devopsguys.com/2014/07/19/devops-defining-devops-its-a-recipe-not-a-blueprint/">this article about how DevOps is a recipe and not a blueprint</a>. Just like with DevOps, what works for one team is not necessarily right for another. The company, the business, the project, the teams role and the personalities of different teams will determine what works. What is really important is that you design your culture and your processes for the specific needs and wants of a team or company. And that you reflect on the changes you make and continuously adapt them, always trying to make your team or company as great as it can be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e71d52ee76dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-etc/recipes-for-successful-team-culture-e71d52ee76dd">Recipes for successful team culture</a> was originally published in <a href="https://medium.com/product-etc">Product, etc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First 24 Hours of Google Glass]]></title>
            <link>https://medium.com/14-days-of-glass/first-24-hours-of-google-glass-4bfe138b5a7a?source=rss-5a629b6f1666------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bfe138b5a7a</guid>
            <dc:creator><![CDATA[Aaron Henshaw]]></dc:creator>
            <pubDate>Thu, 02 May 2013 15:48:08 GMT</pubDate>
            <atom:updated>2013-05-02T17:27:41.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UrdevQMsfe1E4b5E.jpeg" /></figure><p>Last week I got an email from Google informing me that I would be one of the first people to get Google Glass.</p><p>I had been anticipating this moment for years. We started hearing rumors of Google Glass a few years ago, but it wasn’t until last May, at <a href="http://www.theverge.com/2012/6/27/3121164/project-glass-demo-io">Google I/O</a>, that we saw people wearing them. And we all saw <a href="http://news.cnet.com/8301-17852_3-57565018-71/brin-wears-his-google-glasses-on-nyc-subway-um-why/">Sergey Brin sitting on the subway</a> five months ago. They were being spotted in bars and around NYC and SF with greater frequency. Finally the day had come when I would get to bring mine home.</p><p>I had the opportunity to play with a pair at a Google event in February. But I was really curious about what it would be like to actually have them on my face out in the wild: on subway rides, first dates, at the office, and in bars.</p><p>This post isn&#39;t about the metaphorical discussions around Glass and its impact on the future, however interesting those debates might be. I also want to avoid giving my insights, at least yet. It&#39;s just about wearing Glass. Here&#39;s a recap of my first 24 hours of wearing Glass (sports and sleeping not included).</p><h3><strong>Holy Shit, Today is the Day</strong></h3><p>At 3pm on April 25, Dustin (my plus-one) and I headed over to the 8th floor of Chelsea Market — a gorgeous, sun-filled loft. It felt nothing like previous Google events I’d attended, which were crowded but modest. Two young, friendly Glass-wearers took our IDs and showed us inside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HWZzCMb-ZuS7TuL8.jpeg" /></figure><p>We were escorted into a beautiful lofted space, with windows and mirrors everywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1SsIxiOFCNIaG1j-.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SfqkM2Ix71kQgVx6.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0OaHN1PQYjZx9Xm4.jpeg" /></figure><p>After Marina, our Glass Guide, greeted us, we sat down to get set up. We accepted free champagne because nothing says day drinking like momentous and historical advances in personal computing. Then she took us over to a wall to try on all the different color options that Glass is available in (teal, orange, shale, charcoal and white).</p><p>These days, so much emphasis is placed on the unboxing experience, and this one certainly did not disappoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hm7Roq9zzuz1kf4H.jpeg" /></figure><p>Setup is painless. I downloaded the Android app, synced the Glass and my Android phone together, and was ready to go. My first text message, to my colleague Amanda, said, “hi from the glasses.”</p><p>I know, not very creative. But cmonnn. I was able to text Amanda simply by speaking a few words. And the amazing thing is — it worked. No fussing, no fucking up. It sent her what I wanted to say, and then Glass faded into my periphery.</p><p>After another glass of champagne, it was time to go out into the wild.</p><h3><strong>Stop #1 — The Office</strong></h3><p>We work in an amazing office with some great companies: <a href="http://www.branch.com/">Branch</a>, <a href="http://medium.com/">Medium</a>, <a href="http://abacus.com/">Abacus</a>, and <a href="https://www.thinkup.com/">ThinkUp</a>.</p><p>They all knew what Google Glass was, but most have never seen it, so everyone immediately <a href="http://youtu.be/uyHKqyfW8VU">everyone gathered around</a>. I passed them around so everyone could give them a try.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k5zZjPsSMOT5ZVhD.jpeg" /></figure><p>This was fun, but the day was over, and it was time to head back out into the world.</p><h3><strong>Stop #2 — The Subway</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WqUuO9sTrSHYczCx.jpeg" /></figure><p>We hopped on the L train into Williamsburg. We were a group of four, two of whom were wearing Glass. So we got a lot of curious looks and stares, but no questions or interactions.</p><p>Walking the streets of New York was much more interesting. One guy almost tripped over the sidewalk doing a double/triple/quadruple take of us. It was hard not to laugh.</p><p>Some hipster girl on a bike yelled “FUCK YOU AND YOUR GOOGLE GLASS!”</p><p>A nice, young couple came up to us and asked us some questions on the street while we were waiting for a friend and then asked to take a picture.</p><h3><strong>Stop #3 — Meatball Shop</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R_tdR9-qOqLuPOU0.jpeg" /></figure><p>We walked into the Meatball Shop and put our names down for a table. After we sat down, the waitress asked what was on our faces. When we explained what it was — a computer, but for your face — she said, “Weird,” and walked away.</p><p>The conversation was a total dud. I realized that explaining this thing to people who have never heard of it was going to be a process.</p><h3><strong>Stop #4 — Brooklyn Bowl</strong></h3><p>We went to a concert of Killer Mike and Big Boi that night at Brooklyn Bowl. Inside the venue people were looking but not really saying anything.</p><p>The moment the music started was one of Glass’s finest moments. I recorded 720p videos of song clips and the entire rendition of <a href="http://www.youtube.com/watch?v=Sti_HfKxzvc">”The Whole World,”</a> and captured photos — and I didn’t have to take my phone out once. Although you do have to try and keep your head still, the content I captured was beautiful, and the sound and video quality are ridiculous.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YtpnZ9TD5ECZCqHZ.jpeg" /></figure><p>The next stop was One Stop Beer Shop, my local bar. The first bartender, Michelle, said, “You are an idiot, what are you doing with that on your face?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*djXjlg88MAqFSuCs.jpeg" /></figure><p>The other bartender, Claire, said “OMG!!! You have those!!! Wowwww!”</p><p>A couple of other regulars were curious, and we chat about it until around 1am.</p><h3><strong>Stop #5 — Prospective Office Space, Chinatown</strong></h3><p>We are looking for new office space, so a few of us went to check one out in Chinatown.</p><p>I had never been to this building before, so when I got off the subway I asked Glass to take me to the address.</p><p>Navigating with Glass is unreal. A Google maps navigation comes up on the screen, showing where you are and where to go. As you walk, it updates in your eye, so you only have to glance at it occasionally to see where you are going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PMmMjUGIMll3csko.png" /></figure><p>Again, it just worked. I believe I had to speak the address twice for it to get it right. But it got me right to the door from the subway with no fuss. The direction of the arrow was correct for the direction in which I was walking, and I made it there without running into any piles of garbage or old fish.</p><p>Not everyone in the company could come to check out the space, and as a result, I took some photos and video with my Glass and shared them then and there to all of my colleagues via Google+. After watching the video, they felt they didn’t need to go see the space themselves.</p><p>The cool part about shooting video with Glass is that wherever you look, you are filming. You don’t really need to think about where the camera is, as it’s just your field of view.</p><p>You can activate it by asking Glass to “record a video” or “take a picture,” or you can click a shortcut button on the top of the device to do either. I find myself using both ways, but definitely the button shortcut more.</p><p><strong>Stop #6 — Red Egg</strong></p><p>After checking out the office, we stopped at Red Egg for some dim sum.</p><p>We sat down, ordered food, and finished our lunch. Nobody really noticed or said anything, but Glass was on the whole time.</p><p>Then one of the waitresses came over.</p><p>“What is that?”</p><p>“Google Glass.”</p><p>“Shes like is it a microcomputer on your head?”</p><p>“Yeah exactly… Do you want to try it?”</p><p>“Can I?”</p><p>“Yeah sit down and we will show you.”</p><p>We played the video we took of the office space and had her place it on her head. And all she had to say was:</p><p>“WOOOOOOOWWWWWWWW!”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bfe138b5a7a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/14-days-of-glass/first-24-hours-of-google-glass-4bfe138b5a7a">First 24 Hours of Google Glass</a> was originally published in <a href="https://medium.com/14-days-of-glass">14 Days of Glass</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>