<?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 Bowery on Medium]]></title>
        <description><![CDATA[Stories by Bowery on Medium]]></description>
        <link>https://medium.com/@boweryio?source=rss-e2168c067e4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UN-IDnjbXl2GkN_fVDwnEQ.png</url>
            <title>Stories by Bowery on Medium</title>
            <link>https://medium.com/@boweryio?source=rss-e2168c067e4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:34:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@boweryio/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[Productivity Hacks from Top Developers: Kim MacCormack]]></title>
            <link>https://medium.com/@boweryio/productivity-hacks-from-top-developers-kim-maccormack-4c131d3bb231?source=rss-e2168c067e4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c131d3bb231</guid>
            <dc:creator><![CDATA[Bowery]]></dc:creator>
            <pubDate>Tue, 06 Jan 2015 15:50:24 GMT</pubDate>
            <atom:updated>2015-01-06T15:51:26.768Z</atom:updated>
            <content:encoded><![CDATA[<p>Developer productivity is not all about how many lines of code you can write in a day and it’s not about how fast you can complete a given task. In truth there’s no one trait or silver bullet that will help you become a more productive developer. It’s a combination of the practices, tricks and tools that you employ to improve software quality and delivery every day.</p><p>At <a href="http://bowery.io/">Bowery</a>, our goal is to enable stronger and more productive developers. So we set out to get advice from the most talented and productive developers we know on how they manage their time to stay on task and productive. In the second post in our series, we spoke with Kim MacCormack a Senior Software Engineer and Architect at IBM. Kim is not only a master software craftswoman, she’s also an Ice Hockey player (she plays on 3 teams a season!). See how she juggles it all and more below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-KRo6Wq6oEesoISXi7QYw.jpeg" /><figcaption>Kim is a rockstar engineer and Ice Hockey player</figcaption></figure><p><strong>What was your first engineering job?</strong></p><p>My first coding job was as a Webmaster (yes that’s how long ago it was) at a Telecommunications company. My first engineering job was as a Java developer on an import/export control system for the US State Department.</p><p><strong>What are three qualities that make you a strong developer?</strong></p><p>The three qualities that make me a strong developer are my strong organizational skills and passion for detail. I’m also very well-rounded in terms of the projects I’ve worked on and the problems I can solve. I have worked on over thirty web applications for various commercial, non-profit and government clients as both a Software Engineer and Technical Lead in varying domains. In addition, I have extensive experience with every aspect of the software engineering lifecycle including: requirements analysis, design, user interface design, code development, and quality assurance.</p><p><strong>What are some tactics you’ve developed that help you write really high-quality code?</strong></p><p>My most used tactics for create high quality code are writing tests, creating lots of generated sample data, studying design patterns, requesting code reviews, and working on a variety of projects across different sectors and with different deliverables.</p><p>I have worked on applications for various commercial, non-profit and government clients of varying domains such as a rebuilding of a 17,000 page site for the American Museum of Natural History, an import/export control system for the US State Department, a cloud marketplace for IBM, Salesforce integration project for a large networking company, an affiliate tracking tool for LivingSocial, a large HD video streaming web application, a tenant based tool for bookkeepers, multiple social networking and profile search engine applications, a data collection application for a government research institution, public and intranet sites for government agencies, and a multilingual website for a large telecommunications company.</p><p><strong>What are some best practices you’ve developed to work better with your team?</strong></p><p>I work best on a team where there is a culture of mutual admiration and respect. I’ve found that doing a great job is the best way to earn the respect and loyalty of your team. I also strive to be professional and publicly recognize teammates when deserved. My dedication to being organized and on top of my tasks has helped me earn the confidence and trust of all my teams I have worked.</p><p>On a weekly basis I publicly commit to what tasks I will do to contribute to the project, usually during a scrum meeting. If a situation arises where I can’t meet those commitments, I communicate this as early as possible so there are no surprises. I am always honest when I make a mistake or don’t know how to do or manage something. I provide status at the end of every day of what was accomplished and my plans for the next workday.</p><p><strong>How do you (how does your company) measure your own productivity or that of your team?</strong></p><p>I measure both my own productivity and that of my team, by how often we meet our commitments, with high quality software.</p><p>In terms of time commitments, I use my experience to accurately estimate my tasks and then meet or exceed the estimated completion date. Quality commitments are met by striving for 100% test coverage of my code.</p><p><strong>One frustrating thing for developers is often maintaining technical debt. How do you and your team manage proper maintenance of high-quality code in your app/project?</strong></p><p>I think the best way to manage technical debt is to commit to 100% code coverage. With that foundation, the team can feel confident that a refactoring effort won’t cause unexpected consequences. I treat refactoring as a feature that has a dedicated time frame every quarter and include it in the schedule and the product backlog. There is a constant need for security patches, updates, redesign, etc.</p><p><strong>What are some tools you and your team use to maximize productivity?</strong></p><p>I have found that some of simplest techniques help team maximize productivity. A daily scrum for the team to share and publicize each individuals personal commitment to the release. Group chat tools that allow for quick synchronous chats (such as SameTime, HipChat).</p><p>Make an attempt to automate anything you can with technology or templates. I am always looking for areas to automate or improve the speed at which changes can be made to an application by the client themselves.</p><p>Automating the integration of code between developers where every push to a source code repository is verified by an automated build and a test suite is done with Cruise Control on our local servers or a hosted continuous integration solution such as Semaphore. We then automate the notifications of any problems to our chat tool, such as HipChat.</p><p>Wherever possible I build an “administrative dashboard” so that clients can not only change their data themselves, but also allows for immediate time to market without having to wait for a release deploy.</p><p><strong>What is a big challenge that you overcame in your engineering career?</strong></p><p>The biggest challenge in my engineering career was insecurity and confidence issues. I overcame this by surrounding myself with successful, positive engineering role models who were very supportive in helping me step outside my comfort zone to gain the confidence I needed.</p><p>Pair programming is an excellent way to expand your comfort zone and gain confidence as a developer. I started out by choosing two engineers who I not only respected from a technical standpoint but who understood how nervous and shy I was about the process. Once I got comfortable sharing my technical skills in that supportive environment, I branched out to pair programming with people I didn’t know personally. I believe this effort helped me grow leaps and bounds as an engineer, not only in adding to my knowledge base, but most importantly feeling confident voicing my opinions.</p><p>For more productivity tips, follow Bowery on Twitter <a href="https://twitter.com/boweryio">@Boweryio</a></p><p><a href="http://bowery.io/blog/">← Back to Blog</a></p><p><em>Originally published at </em><a href="http://bowery.io/blog/posts/2014/12/23/developer-productivity-kim-maccormack.html"><em>bowery.io</em></a><em> on December 23, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c131d3bb231" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Preparing for Your First Tech Interview Part II: Do Your Research]]></title>
            <link>https://medium.com/@boweryio/preparing-for-your-first-tech-interview-part-ii-do-your-research-f92ef68d5251?source=rss-e2168c067e4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f92ef68d5251</guid>
            <dc:creator><![CDATA[Bowery]]></dc:creator>
            <pubDate>Fri, 19 Dec 2014 19:12:18 GMT</pubDate>
            <atom:updated>2014-12-19T19:14:55.753Z</atom:updated>
            <content:encoded><![CDATA[<p>Interviews are challenging for everyone — not just technologists. “Hiring companies have unique technical interview styles,” says Jovena Whatmoor, co-founder at <a href="http://www.clutchtalent.com/">Clutch</a>, a talent agency based in New York City specializing in Technical Recruiting. “Interviewing is a skill that improves with time, exposure, and practice.” The more interviews you do, the easier it will get over time. But if you don’t have much experience interviewing you won’t know what you’re getting into. In <a href="http://bowery.io/blog/posts/2014/12/09/preparing-for-your-first-tech-interview-part-i.html">part I</a> of our Tech Interview series, we outlined the key skills that will help you stand out in an interview. In this post, we’ll help you do your background research to help you impress recruiters and hiring managers make an informed decision about where you start your career.</p><p>First and foremost, interviews don’t need to be scary. An interview is a two-way-street. Interviews are an opportunity for you and a company to learn more about one another, which means you also have to come to the table with a critical eye. “Remember,” says Kevin Winnery, Head of Developer Education at <a href="http://www.twilio.com/">Twilio</a>, “that you are interviewing them as well.” Take this approach and you’ll find yourself more prepared for your interview and confident that you can tackle challenging problems in your future career.</p><p>In your two-way interview process, having background knowledge about the company and how you will fit in can be a huge asset. Whatmoor says that failure to convey adequate enthusiasm for a future position is one of main ways candidates fail in an interview, second only to disparity of skills and experience. “This can prohibit a candidate from putting their best foot forward, disabling their ability to convey enthusiasm or properly prepare for the interview.”</p><p>In our second post about technical interviews, we will put you through interview bootcamp to prepare you for your first phone screen. Your main prerogative: learn everything you need to know about the company to show them why you’re a great catch.</p><h3>Get to know your Future Employer</h3><p><em>A candidate may come across unprepared and unenthusiastic if they have little knowledge about the product and team, no specific company related questions, or opinions about the product.</em></p><p>Since you know everything you need to ace the <a href="http://bowery.io/blog/posts/2014/12/09/preparing-for-your-first-tech-interview-part-i.html">technical portion</a>–if not read <a href="http://bowery.io/blog/posts/2014/12/09/preparing-for-your-first-tech-interview-part-i.html">Part I</a> — of your interview based on your skill-building and years of studying computer science and math, now you need to fill your gaps in other areas. “Many college students underestimate how much they should actually prepare for an interview,” says Whatmoor. “A candidate may come across unprepared and unenthusiastic if they have little knowledge about the product and team, no specific company related questions, or opinions about the product.” This is a simple problem to avoid. Do your due diligence and learn everything you can about the company before you take an interview or phone screen.</p><h4>Who They Are</h4><p>Kevin said it best “If possible, do some homework on the people you’ll be interviewing with — not to get ammo for the interview, but to learn what unique knowledge they might have that you can ask them about. Even if you don’t get the job, you will have learned something from the process.” Similarly, Jovena suggests researching the “company, product, team members, founding story, culture and visit company and individual team member blogs”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xCrLDR_DzAQq184dfTbnbg.jpeg" /><figcaption>Wikimedia Hackathon 2013, Amsterdam by <a href="https://www.flickr.com/photos/ter-burg/">Sebastiaan ter Berg</a></figcaption></figure><p>This is great advice for two reasons. 1) It shows you have done your research and are putting in work to get the job and figure out if it’s right for you (remember, it’s a two-way street). 2) This will flatter your interviewer, no matter who they are. Remember, your interviewer has a day job and most of the time, they are taken out of an entire day of work in order to interview you and other students (this prevents <a href="http://www.joelonsoftware.com/articles/fog0000000022.html">context switching</a>). Show them that you know a little bit about what they work on; it will make you stand out among other candidates.</p><h4>What They Value</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esf9qN1O07z7qk5CgFw8Pw.jpeg" /><figcaption>I<a href="https://www.flickr.com/photos/prestons">mage by Preston Smalley</a></figcaption></figure><p>If you’re joining a great company, they will have a very clear mission and vision for what they are working to accomplish. Airbnb is very clear about their mission, who they are and what they value. Not every company has a strong, externally facing brand like Airbnb, so it’s likely you will have to do some digging in each case in order to you understand what they think is useful and important not only for the company but in each employee’s life. I recommend reviewing <a href="http://www.glassdoor.com/">Glassdoor.com</a>, a site for crowdsourced company reviews and salaries, which will give you a better understanding of the working environment and culture. This helps with the two-way street: you can more clearly articulate why you’ll be a good fit at the company and you can determine whether or not the company is a good fit for you.</p><h4>What they’re building</h4><p>You should try to use their product before you do an interview or phone screen. Having a user-facing perspective of the product will help you as you talk through the type of technical questions that come up during the interview. Take the extra step and see what active open source projects they maintain on Github. Take a look at the code base and see what types of problems they are trying to solve. This will give you a holistic view of what you will work on if you join and will better prepare you to solve the problem questions they’ll ask in the interviews.</p><h3>What Not to Do</h3><h4>Don’t overthink it</h4><p>This is very important and something that everyone does so they feel prepared. You’ve learned everything you need to know through practical experience and years of studying math and computer science. You’re not going to become a better programmer or problem-solver by cramming in a ton of information from an O’Reilly Sysadmin book the night before your interview. Instead of feeling prepared you will instead feel tired, nervous and frustrated.</p><p>Technical interviews are challenging for a reason– hiring managers use them as a way to weed out the the wheat from the chaff. Some of the questions they ask will be intentionally difficult. “If the job is worth it,” says Andrew Noonan, a Developer Advocate at Twitter. “You won’t be able to answer every question they ask you in the interview.”</p><p>Great engineers are problem-solvers. They don’t have all the answers, but they can figure out the best way to find that answer if given a few variables. Show that you aren’t scared of what you don’t know, but rather that you thrive in areas of uncertainty and are excited about new problems.</p><h3>Next Steps</h3><p>To wrap up, here are your next steps</p><ul><li>Look up all the companies you are interviewing with on <a href="http://www.glassdoor.com/index.htm">Glassdoor</a></li><li>If possible, find out who you are interviewing with and do some background research on who they are and what they do</li><li>Read their company blogs and check out their Github to get insight into their mission and what problems they are trying to solve</li></ul><p>Now you’re all set! Remember, don’t be nervous. It’s a two-way street and you’re doing your part to put your best self forward. Get some sleep and get excited!</p><p>In our next posts, we’ll give you some advice on building your resume and salary negotiation. Have something else you want to hear about? Let us know on <a href="https://twitter.com/boweryio">Twitter</a> or <a href="https://www.facebook.com/bowerysoftware">Facebook</a>.</p><p>For more productivity tips follow <a href="https://twitter.com/boweryio">Bowery</a> on Twitter.</p><p><a href="http://bowery.io/blog/">← Back to Blog</a></p><p><em>Originally published at </em><a href="http://bowery.io/blog/posts/2014/12/15/preparing-for-your-first-tech-interview-part-II.blog.html"><em>bowery.io</em></a><em> on December 15, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f92ef68d5251" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productivity Hacks from The Experts: Charity Majors of Parse]]></title>
            <link>https://medium.com/@boweryio/productivity-hacks-from-the-experts-charity-majors-of-parse-71284a6f2783?source=rss-e2168c067e4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/71284a6f2783</guid>
            <dc:creator><![CDATA[Bowery]]></dc:creator>
            <pubDate>Wed, 17 Dec 2014 17:14:24 GMT</pubDate>
            <atom:updated>2014-12-17T17:15:24.124Z</atom:updated>
            <content:encoded><![CDATA[<p>Developer productivity is not all about how many lines of code you can write in a day and it’s not about how fast you can complete a given task. In truth there’s no one trait or silver bullet that will help you become a more productive developer. It’s a combination of the practices, tricks and tools that you employ to improve software quality and delivery every day.</p><p>At Bowery, our goal is to enable stronger and more productive developers. So we set out to get advice from the most talented and productive developers we know on how they manage their time to stay on task and productive. To kick off the series, we spoke with <a href="http://bowery.io/blog/posts/2014/12/16/twitter.com/mipsytipsy">Charity Majors</a>, a Production Engineering Manager at <a href="https://parse.com/">Parse</a>, a mobile app platform for developers which is now a part of <a href="https://code.facebook.com/">Facebook</a>. Charity has a ton of experience deploying large systems at scale and she also happens to be one of the funniest people in DevOps–no easy feat. After working at a small startup and transitioning to Facebook, Charity has great advice for how to stay productive and work better with your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*n4BIcEHnf1PmzCI55WZX0Q.jpeg" /><figcaption>Charity Majors is a Production Engineering Manager at Parse</figcaption></figure><h4>What is your title?</h4><p>I am currently a Production Engineering Manager at Parse, which is now part of Facebook. Parse provides a fully featured backend as a service for mobile developers, and Production Engineering at FB is like a hybrid Software Engineering and Ops role. Before the Parse acquisition I was the first Site Reliability Engineer hired at Parse. I have also been called a Sysadmin, a Systems Engineer, a Release Engineer, a DBA, a Data Monger, and a really shitty software engineer.</p><h4>What was your first engineering job? What’s the one thing you learned there that you look back on today?</h4><p>My first engineering job was running systems and networks for the University of Idaho when I was 17. I felt <em>so </em>unqualified and was so terrified of being “found out” that I worked five times harder than I needed to. I would pound away on a problem all night instead of asking for help, which was frankly dumb and held me back.</p><p>Now I <em>love </em>asking dumb questions! Especially now that I’m managing a team.</p><h3>I love modeling an environment where it’s okay to ask dumb questions and not know all the answers. It’s really okay, nobody else knows what they’re doing either.</h3><h4>What are three qualities that make you great at your job?</h4><p>I am stubborn as hell. I am hardly the best computer scientist in the world, but if I decide to fix a thing or figure out a thing it will get done.</p><p>I’m really good at firefighting and staying cool in the middle of a crisis. I never panic or freak out and make bad decisions, even under extreme pressure.</p><p>I think technology is inherently hilarious. The internet is held together by spit and baling wire and unicorns and dreams and ridiculous bugs and it’s amazing that it ever works at all. We’re just monkeys pushing bits around. Ops can be really stressful and high pressure, and remembering how ridiculous everything is can help you keep your sanity and perspective.</p><h4>What are some tactics you’ve developed that help you manage systems effectively?</h4><p>There are the obvious things, like automate everything. Treat your infrastructure as code. Treat your services as naively as possible. Care about as few things as possible. Build resiliency into every layer. But everybody knows this by now.</p><p>Honestly I feel like engineers tend to answer every problem with more software. Have a problem? Let’s write more software! I think this is completely backwards. By adding more software you are adding more opportunities for failure, more things you have to understand and debug and be an expert in. I believe in using as little software as necessary to solve the problem, and reusing solutions as often as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*jlOTzObpfO7KNuAl6oJAWw.jpeg" /></figure><p>Sometimes your problem really is a special snowflake and you need to write custom software to solve it, but this should be a last resort, especially for anything that isn’t your absolute core business.</p><p>Also? Take vacations. Make your people go on vacation. We call vacation time “chaos monkey for humans” and it really is the only way to make sure your human systems are redundant and refreshed.</p><h4>What are some best practices you’ve developed to work better with your team?</h4><p>Software is mostly terrible, and ops is where design meets reality. We don’t run services; we build architecture, and empower developers to run their own services.</p><p>I feel really strongly that developers should deploy their own code. The person who wrote the code will always have the most context on what changeset is going out, what the dependencies are, and which graphs to watch. Developers write better code when they are exposed to the production impact of the changes they are making. Deploying and alerting create a virtuous feedback loop that both empowers developers to move quickly and educates them on the consequences of their code.</p><p>We practice blameless post mortems. In addition to post-morteming any production impacting event, we have a weekly meeting where we run through any open followup tasks and figure out why they haven’t been closed out yet. Are there blockers? Is it outside the scope of a followup task? Is it something we actually don’t need to do? This meeting has been highly effective at getting people to complete their followup tasks because <em>nobody </em>wants to go to yet another meeting.</p><p>Speaking of which: minimize meetings, for the sake of all that is unholy. Make meetings optional. If you don’t feel like a meeting is worthwhile, don’t go! <em>Vote with your feet!</em></p><h4>How do you (how does your company) measure your own productivity or that of your team?</h4><p>Every six months we set aggressive goals for ourselves as a team. And then we hold ourselves accountable for reaching those goals six months later. We don’t expect to hit all of our goals — things change all the time! It’s more important to be flexible and focus on impact than to hold yourself to accomplishing what you thought was going to be important six months ago.</p><p>“Focus on impact” is one of Facebook’s big catchphrases but I actually think it’s really valuable. If an engineer writes some elegant framework that doesn’t solve a real problem, or nobody else wants to use it, that is way less valuable than if they wrote five ugly lines of bash that remediates some problem that keeps waking engineers up at 2 am.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Z6K6SNV-CiT6drcjD2CAw.jpeg" /><figcaption>Parse was acquired by Facebook in 2013 and is now one of Facebook’s core developer tools. Photo of Mark Zuckerberg at Parse Developer Day. <a href="http://venturebeat.com/tag/parse-developer-day/">Photo Credit: VentureBeat</a>.</figcaption></figure><p>Setting goals is about figuring out all the things you are going to say no to. Any time you choose to do a thing, you are implicitly choosing not to do twenty other things with that time. You can either get really ruthless and explicit about choosing what not to do, or you just slide into constantly reacting to events. Not saying no is the best way to get trapped in a state of constant firefighting and burnout and never reaching your goals.</p><h4>One frustrating thing for developers is often maintaining technical debt. How do you and your team manage proper maintenance of high-quality code at Parse and Facebook?</h4><p>We do a lot of cross-functional code reviews and system design reviews with the backend software engineering team. There’s a lot of skill set overlap, but generally speaking they push us on code quality, unit tests, and safely handling data. We push them on building maintainable and scalable systems.</p><p>But culture has a HUGE role to play here. Do you have a culture of calling out and rewarding the people who do the dogged, unflashy work of tracking down hard bugs, cleaning up old code, responding to customers, keeping unit tests green and the build pipeline rolling? Or do you only praise and promote people for shipping shiny new features? You need to sing out and recognize your heroes.</p><p>At Parse we have a Tiara of Technical Debt and a Wand of Developer Satisfaction that we periodically award to engineers when they go way beyond the call of duty in cleaning up old code or responding to challenging customer complaints. Everything is better when you make a game out of it.</p><p>Most “productivity tools” are terrible time sinks. I personally prefer a notebook and sparkly pens for my todo lists but I reluctantly concede that this solution does not scale.</p><p>We use <a href="http://github.com/">Github</a> and <a href="http://phabricator.org/">Phabricator</a> for code reviews, which everyone is pretty happy with.</p><p>For task tracking and project management, we use the <a href="http://www.quora.com/How-does-Facebook-track-tasks-internally">Facebook Tasks</a> tool a lot. It’s similar to Asana (Asana was founded by former Facebook employees and “Tasks” engineers.) It’s a very simple, stripped down minimal set of features for collaborating with other engineers and teams. Task tracking tools are mostly good insofar as they increase transparency and ambient awareness of what’s going on.</p><p>I feel like the most important productivity tool of all is cultivating a consciousness of what it takes for you do your best work, and creating that environment for yourself. Like, I can’t take interruptions when I’m writing code. The context switching is incredibly expensive for me, so I’ll find a quiet room, log out of chat, or work from home. You have to be aggressive in carving out the space and time you need to be successful. Nobody’s going to do that work for you.</p><p>One trick I use is, I have different Pandora channels devoted to different types of work. I have one channel that I only listen to while writing code, another for digging in to systems problems, another for working on slides or docs or presentations, another for writing emails. It’s a cue that helps me slip into the right frame of mind and brings me back to what I’m supposed to be focusing on.</p><h4>What is a big challenge that you overcame in your engineering career?</h4><p>Lately my biggest challenge has been learning how to be effective at a big company. It’s a totally different skill set than being effective at a startup. I have avoided large companies my entire career, but when Parse got acquired I went from working at a 25-person startup to an 8000-person corporation. The culture shock was intense. Working at a large company requires so many more intangible people skills like negotiating, marketing your projects internally, representing your team and your product in a way that benefits them and gains them recognition, etc. There’s so much more overhead just to keep everyone working together smoothly. But there are some goals that only big companies can tackle, so I do think it’s a skill set worth learning. We now have access to some of the best engineering resources in the world if we can just figure out how to leverage them.</p><p>I’m also super proud of the work I did on the early days at Parse. When I started on Parse I had never used AWS, Chef, MongoDB, Redis, Ruby &amp; Rails, Cassandra — basically all the core technologies the company was originally built on. They took a risk and hired me just because I had a track record of rapidly scaling systems. Learning everything at once was exhilarating, like getting plunged into a deep cold pool of I-don’t-know-how-the-fuck-anything-works. It was amazing. Definitely an experience I want to repeat.</p><h4>Have you ever had a mentor at a new job? Has that helped improve your skills or your productivity over time?</h4><p>I’ve never had an explicitly mentor-type relationship, but I’ve been fortunate to work with some world-class engineers, and some really introspective leaders who have helped me understand and unpack my own needs and strengths and weaknesses.</p><p>At <a href="http://www.lindenlab.com/">Linden Lab</a>, part of our company mission statement was “Do it with style.” I love this so much. If a thing is worth doing, it’s worth doing with flair. Why would you ever want to just show up, do the task, be a cog in the machine and go home? It’s worth pouring a bit of your self and your heart into your work and putting your own personal stamp on it. It builds a culture where people are valued for the whole selves that they bring to work. And for me personally, I find that if I don’t feel like doing something with style, it’s a good signal that actually I don’t really want to do it at all and I won’t do it very well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*IMxTkcpELW_C6D-ZyOBAhQ.jpeg" /><figcaption>Follow Charity on Twitter: @MipsyTipsy</figcaption></figure><p>For more useful and hilarious tips from Charity, follow her on Twitter <a href="https://twitter.com/mipsytipsy">@mipsytipsy</a>.</p><p>Want more productivity tips? Follow us on Twitter <a href="https://twitter.com/boweryio">@boweryio</a>.</p><p><a href="http://bowery.io/blog/">← Back to Blog</a></p><p><em>Originally published at </em><a href="http://bowery.io/blog/posts/2014/12/16/developer-productivity-charity-majors.html"><em>bowery.io</em></a><em> on December 16, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71284a6f2783" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Preparing for Your First Tech Interview]]></title>
            <link>https://medium.com/@boweryio/preparing-for-your-first-tech-interview-bbaebb7e6f1b?source=rss-e2168c067e4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbaebb7e6f1b</guid>
            <dc:creator><![CDATA[Bowery]]></dc:creator>
            <pubDate>Wed, 10 Dec 2014 20:58:08 GMT</pubDate>
            <atom:updated>2014-12-10T21:00:54.695Z</atom:updated>
            <content:encoded><![CDATA[<h2>Part I: Sharpen Your Skills</h2><p>It’s a busy time for many computer science students: it’s interview season. After attending career fairs and info sessions you have picked out a number of great companies, both big and small, where you will start your career. This is a very exciting time for you! You’re graduating from college and moving on a new stage. But before you get excited, it’s time to get ready for the interview!</p><p>If you are a Computer Science or Math student, you’ve likely learned everything you need to know for the technical portion of the interview, but you might not have the practical expertise to solve basic programming problems. “In interviews, college students may fail if the company is evaluating problem solving and practical skills based upon experience, and the candidate simply has not had enough exposure.” Says Jodi Jefferson, founder of recruiting agency <a href="http://www.clutchtalent.com/">Clutch</a> based in New York City. “To do well, they may need to have done substantial internship work and personal projects. It’s difficult to gain this sort of knowledge just in the classroom.” Don’t fret, there’s a few ways to get that experience even if you don’t have any work experience. In this first post in our series on preparing for your first tech interview, you’ll learn how you can build up the technical skills so you remain ahead of the pack during the interview process.</p><p><strong>From Theory to Practice</strong></p><p>As a student, it helps to take initiative and build your own project outside of class. “Don’t wait for your school to teach you how to design and program they might never get around to it” advised <a href="http://www.kegel.com/academy/getting-hired.html">Dan Kegel</a>, “Most programming courses don’t provide the kind of experience that real programming gives, and real employers look for real programming experience.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xCrLDR_DzAQq184dfTbnbg.jpeg" /><figcaption><a href="https://www.flickr.com/photos/ter-burg/8812567121">Photo Credit: Flickr</a></figcaption></figure><p>Getting a job as an engineer involves turning the theory you learned into practical techniques and skills. For example, while you might have studied operating systems in college, you might not have built an operating system before. Well, what are you waiting for? Go ahead and get started!</p><p>Ok, fine, we’re not all <a href="http://en.wikipedia.org/wiki/Linus_Torvalds">Linus</a>, but it’s important to take the ideas you learn in school and work on real projects. Here are a four steps that will help you get there.</p><p><strong>Learn how to use Git</strong></p><p><a href="http://git-scm.com/">Git</a> is a version control system that allows you to collaborate with others and manage your project as you write and commit code. While you might not be required to learn Git in school, every employer will require that you learn to use Git–or another version control system like Subversion–once you’re on the job. According to research done by Rebel Labs, over 91% of organizations use version control for quality control and collaboration. Git is one of the most widely used and easily accessible version control systems right now, so it’s wise to become familiar with Git and the ecosystem. If you’re interested in using Subversion–this is the version control system of choice amongst Google developers–you can <a href="http://svnbook.red-bean.com/en/1.7/svn.intro.quickstart.html">try a tutorial</a>.</p><p>The first thing you should do is sign up for <a href="https://github.com/">Github</a>, a social sharing site for code which uses Git to manage the storage and versioning of your code. If you don’t have a Github account, go sign up and then download and get started with Git. Github has a very thorough overview of how to <a href="https://help.github.com/articles/set-up-git/">set up</a> with Git on their website. If you want additional help, try taking a <a href="https://www.codeschool.com/courses/try-git">Git course on Code School</a>. Once you have everything running, sign up for Github’s Student Developer Pack as well which offers students developer tools for free.</p><p><strong>Start a Project</strong></p><p>If you’re a computer science or math student, you need to put your skills to work. The best way to do this is to start a project. Try by building something you or someone you know might need. For example, do you find yourself doing the same mundane task over and over again? Try automating it by building a simple command-line script. If your friend needs a website for their next event, figure out how to build one. The opportunities are endless and you can use these projects on your resume and in your interview as proof of what you can build in the future.</p><p><strong>Hack, Hack, Hack</strong></p><p>Hackathons are a fantastic way to try out new technology, build on your existing skills, work with a team and build a fun project. If you are at a large college or university, check out your computer science club to see if there are upcoming Hackathons open for competition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UvpPdcirtZR3OGLz9YWm_g.jpeg" /><figcaption>HackNY Fall 2012 Hackathon</figcaption></figure><p>If not, check out the <a href="http://mlh.io/">Major League Hacking schedule</a> for Hackathons coming up at other universities in your area. You’ll be giving up your weekend, but it’s a great way to make friends and win awesome prizes for your hacks!</p><p><strong>Participate in Open Source</strong></p><p>Participating in open source is very important in building up your engineering skills. When you are use open source software, you leverage the corpus of knowledge built by project maintainers and other users. Understanding how to ask questions and find answers to your issues through the web will make you a much stronger programmer over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*VN0CRt5ha6FrRdwrkzQm_A.jpeg" /><figcaption><a href="https://www.flickr.com/photos/jalbertbowdenii/5682524083/">Source: Flickr</a></figcaption></figure><p>To start, start using an open source programming language, like Python, Ruby, Go or Node.js for your first project. Subscribe to the appropriate user forum and IRC and get involved in conversations. Ask questions and help others figure out answers. Believe it or not, these are the tactics that software engineers use every day to solve problems at work. You can do it from your dorm room and you’ll find it fun and rewarding!</p><p>If you want to make more progress, try contributing to a popular project. Contributing to open source is not an easy feat. It involves solving complicated problems and working with a team, often remotely, so it looks even better on your resume! The first step here is finding a project. We recommend looking at <a href="https://www.facebook.com/notes/alok-menghrajani/getting-your-first-commit-in-an-open-source-project/10150780161673947">Alok Menghrajani’s post on getting your first commit in an open source project</a> and checking out <a href="https://openhatch.org/">Open Hatch</a>, a nonprofit dedicated to getting people involved in open source development, to find projects based on your interests.</p><p>Now, you’re putting your knowledge to work. But don’t stop there. As an engineer, you have a tremendous talent: you can be a builder, and you can continue to create. So don’t view this as a checklist, view it as a place to jump off! If you need help jumping off on one of your first projects, give <a href="http://bowery.io/start/">Bowery</a> a whirl, and get your development environment set up in less than 30 seconds.</p><p>This should help you get on your way to building up hard skills to land your first job. In our next post, we will take you through interview bootcamp so you can research and prepare for your first interviews and phone screens!</p><p><a href="http://bowery.io/blog/">← Back to Blog</a></p><p><em>Originally published at </em><a href="http://bowery.io/blog/posts/2014/12/09/preparing-for-your-first-tech-interview-part-i.html"><em>bowery.io</em></a><em> on December 9, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbaebb7e6f1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Gems to Increase your Rails Productivity]]></title>
            <link>https://medium.com/building-bowery/4-gems-to-increase-your-rails-productivity-a6f7875a97fa?source=rss-e2168c067e4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6f7875a97fa</guid>
            <dc:creator><![CDATA[Bowery]]></dc:creator>
            <pubDate>Tue, 05 Aug 2014 14:11:31 GMT</pubDate>
            <atom:updated>2014-08-05T14:11:31.521Z</atom:updated>
            <content:encoded><![CDATA[<h4>1. Zeus</h4><p>Zeus is a gem that drastically decreases the time it takes Rails commands to run. Depending on the size of the program, this could make a substantial improvement on productivity. The super quick run time also gives you instant feedback when you run tests. It is meant to work outside of bundler, though, so make sure to keep it outside of your Gemfile.</p><p><a href="http://railscasts.com/episodes/412-fast-rails-commands">http://railscasts.com/episodes/412-fast-rails-commands</a></p><p><a href="https://github.com/burke/zeus">https://github.com/burke/zeus</a></p><h4>2. Passenger</h4><blockquote>“Phusion Passenger makes deployment of Rails applications a breeze.”</blockquote><p>Passenger provides a place to host your applications for both development and production environments. It works really well if you are working on multiple applications at a time and need an environment other than localhost.</p><p><a href="http://railscasts.com/episodes/122-passenger-in-development">http://railscasts.com/episodes/122-passenger-in-development</a></p><h4>3. Gritter</h4><blockquote>“This Ruby on Rails gem allows you to easily add Growl-like notifications to your application.”</blockquote><p>Gritter is a quick way to pretty-up your flash notifications. It comes with a few different types of default notices to suit your needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*sNYKhIettYSlpBHfF2fPmA.png" /></figure><p><a href="https://github.com/RobinBrouwer/gritter">https://github.com/RobinBrouwer/gritter</a></p><h4>4. Faker</h4><p>Faker is a gem that populates your database with fake data. This one is great for viewing how your application would look if it was in widespread use. It supports quite a number of data types, including names, addresses and even Bitcoins, rendering the data in a realistic format. Just define how many of each data type you would like, and Faker does the rest for you.</p><p>Here is an example of Faker in use:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*qE_g8mGxC3yMTsUX4lVkHw.png" /></figure><p>As you probably noticed, it generates realistic names and addresses.</p><p><a href="https://github.com/stympy/faker">https://github.com/stympy/faker</a></p><p><a href="http://railscasts.com/episodes/126-populating-a-database">http://railscasts.com/episodes/126-populating-a-database</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6f7875a97fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-bowery/4-gems-to-increase-your-rails-productivity-a6f7875a97fa">4 Gems to Increase your Rails Productivity</a> was originally published in <a href="https://medium.com/building-bowery">Building Bowery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The State of Developer Productivity]]></title>
            <link>https://medium.com/building-bowery/the-state-of-developer-productivity-e5a006f7b724?source=rss-e2168c067e4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5a006f7b724</guid>
            <dc:creator><![CDATA[Bowery]]></dc:creator>
            <pubDate>Wed, 30 Jul 2014 15:52:46 GMT</pubDate>
            <atom:updated>2014-11-20T20:36:17.604Z</atom:updated>
            <content:encoded><![CDATA[<p>When measuring developer performance, it’s hard to find an appropriate metric to use that doesn’t rely too heavily on anecdotal evidence. That’s why we at <a href="http://bowery.io/">Bowery</a> were excited by <a href="http://zeroturnaround.com/rebellabs/download/?token=80eb432c1d5edfc886f91ad2169c139196a99127&amp;utm_medium=email">Rebel Labs’ Developer Productivity study</a>, a 40-page report on what tools and practices developers employ in their daily life. In order to provide a report that gets at the gist of what “performance” really entails, Rebel Labs weighed the effect of different practices and tools on both the <em>quality</em> of the software and the <em>predictability</em> of its release.</p><p>Here are some of the practices the study measured:</p><ul><li>Taking care of technical debt</li><li>Monitoring and fixing code quality issues</li><li>Automated Testing</li><li>Pairing up</li><li>Reviewing Code</li></ul><p>Implementing all of the above practices would yield some increase in software quality, but at what monetary and time cost? That’s where the measurement of predictability comes into play. By measuring these practices against the likelihood of software being released as scheduled, we have a fairly solid metric for viewing whether the time spent improving quality helps developers meet deadlines.</p><h4>Dealing with Technical Debt</h4><p>Technical debt refers to work that is pushed off in favor of other tasks. Most tasks that are deferred are not necessary to deal with in the moment, but the failure to handle those tasks may lead to further issues in the future.</p><p><strong>Conclusion: Technical debt needs to be occasionally addressed. Fixing technical debt all the time has a small but insignificant improvement over fixing it in smaller doses.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*v4VC_z_5l-22qpGWmrU8fg.png" /></figure><h4>Monitoring and Fixing Code Quality Issues</h4><p><strong>Conclusion: Fixing code quality leads to significant improvements in quality and predictability of software releases, likely because doing so leads to engineers addressing underlying structural issues in an application.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*FuYBGQEYFS8YqJI-8BHxxQ.png" /></figure><h4>Automated Testing</h4><p><strong>Conclusion: Using automated testing 100% of the time is better than partial test coverage, but no automated test coverage is slightly better than partial automated test coverage—likely because those engineers are testing their code manually.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*mU9gLts_LeSwWbmeA_KYIA.png" /></figure><h4>Pairing up</h4><p><strong>Conclusion: Pair coding (having one person review code as the other one writes it) has a significant effect on software quality.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*XN_J9kCgUNb7aQnZtiIQTw.png" /></figure><h4>Code reviews</h4><p><strong>Conclusion: Reviewing code appears to have a significant impact on predictability but a minimal effect on quality. This practice likely helps developers detect major issues in design and direction but not smaller problems like bugs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*ByGOzRE8jNo-5GT4v3jYVw.png" /></figure><p><a href="http://zeroturnaround.com/rebellabs/download/?token=80eb432c1d5edfc886f91ad2169c139196a99127&amp;utm_medium=email"><strong>You can read Rebel Labs’ full report here.</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5a006f7b724" width="1" height="1" alt=""><hr><p><a href="https://medium.com/building-bowery/the-state-of-developer-productivity-e5a006f7b724">The State of Developer Productivity</a> was originally published in <a href="https://medium.com/building-bowery">Building Bowery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>