{"id":8113,"date":"2014-07-08T10:00:18","date_gmt":"2014-07-08T15:00:18","guid":{"rendered":"http:\/\/www.mrc-productivity.com\/blog\/?p=8113"},"modified":"2014-09-15T10:21:47","modified_gmt":"2014-09-15T15:21:47","slug":"5-simple-tactics-to-boost-development-productivity","status":"publish","type":"post","link":"https:\/\/www.mrc-productivity.com\/blog\/2014\/07\/5-simple-tactics-to-boost-development-productivity\/","title":{"rendered":"5 simple tactics to boost development productivity"},"content":{"rendered":"

\"Education\"Summary: What is a “productive developer,” and how do you become one? If you’re a developer, or if you run a team of developers, this article defines the term and offers some actionable tips to improve development productivity.
<\/em><\/span>
\n<\/a>
\nDoes your development team deliver applications slowly? Do you wish they completed projects in hours or days instead of weeks or months? Or, if you\u2019re a developer, do you wish you could complete development projects more efficiently?<\/p>\n

Today, let\u2019s explore a few simple tactics that will help boost development productivity. <\/p>\n

But first, let\u2019s define the term. What is a \u201cproductive developer?\u201d <\/p>\n

Does a \u201cproductive developer\u201d finish projects quickly? Not necessarily. A fast developer isn\u2019t always productive. If you create poor quality applications quickly, does that make you productive? No. That makes you a bad developer.<\/p>\n

I believe productivity is measured by speed plus quality. Productive developers know that the job doesn\u2019t end when they deliver the application. They understand the importance of creating easily maintainable applications that adapt to changes.<\/p>\n

So, how can you improve development productivity. While the list could go on, here are 5 key tips:<\/p>\n

1. Avoid task or context switching<\/h3>\n

Some people brag that they can \u201cmulti-task.\u201d Some companies even put \u201cthe ability to multitask\u201d in their job requirements. <\/p>\n

The only problem: It\u2019s physically impossible.<\/p>\n

\"photo
photo credit: dierk schaefer<\/a> via photopin<\/a> cc<\/a><\/figcaption><\/figure>Studies<\/span><\/a> have shown time and time again that our brain can only focus on one task at a time. What we call \u201cmulti-tasking\u201d is simply \u201ctask-switching.\u201d We\u2019re not doing two things at once. We\u2019re jumping from task to task.<\/span><\/p>\n

The problem with task switching: Your brain requires about 12 minutes to fully re-focus on a new task. <\/p>\n

What does this mean for developers? You\u2019re most productive when you\u2019re not jumping from task to task, or from program to program. <\/p>\n

\n\u201cIf possible, find an editor that allows you to work on multiple technologies effectively (ie. CSS, HTML, JS, Server Side Languages),\u201d says Matthew Marksbury<\/span><\/a>, a Sr. Software Architect and Entrepreneur. \u201cSwitching between environments (context switching) can derail focus and drop productivity.\u201d\n<\/p><\/blockquote>\n

On a similar note, actively eliminate distractions. Turn off email notifications. Don\u2019t jump into social media when your applications are compiling. You\u2019ll end up wasting time trying to refocus on your initial task.<\/p>\n

\n\u201cSocial Media sites like Facebook and Twitter can be a big draw for developers waiting for files to copy or application to compile,\u201d says Marksbury. \u201cMore often than not however, you’ll end up spending more time on the social media sites than if you had waited for the task to complete. Once on a social media site, we tend to give up more time than we had originally intended.\u201d\n<\/p><\/blockquote>\n

2. Begin your day with the end in mind<\/h3>\n

In his best-selling book, The Seven Habits of Highly Effective People<\/em>, Stephen Covey explained the importance of beginning with the end in mind. Effective people have clearly defined life goals and values, and shape all of their decisions around them. <\/p>\n

This is easily translated to web development. Rather than blindly rushing into your day, begin each day with specific development goals. What do you need to accomplish that day? As explained below, this approach better focuses your day and increases productivity.<\/p>\n

\n\u201cMost of the tactics we rely on are based around maximizing a developer’s time within a specific project on any given day,\u201d says Nick Pavlak, founder and creative director at Babl Media<\/span><\/a>. \u201cSince we are an agency that work on many different clients’ projects at a time, it is extremely important for our developers to have clearly defined goals to start the day. Every morning each person selects their specific goals for the day based on the projects we’re working on, so they know exactly what is expected out of them. These goals are also limited to only one or two projects each day, as we’ve found that the single largest time sink for a developer is when they have to switch between different jobs.\u201d\n<\/p><\/blockquote>\n

3. Do things right the first time<\/h3>\n

\"Why<\/a>
Why duct tape is not a good way to attach a bumper<\/figcaption><\/figure>When you look at almost any problem, you see two potential solutions: The fast way, and the right way. Sure, you could duct tape that bumper to your car (as someone attempted in the image on the right), but you\u2019ll just have to do it again…and again…and again. <\/span><\/p>\n

The same is true for web development. Sure, you could throw something together that works at the moment. But, think about future maintenance. The quick hacks lead to more wasted than if you had done it correctly the first time.<\/p>\n

\n\u201cDo things correctly the first time,\u201d says Rob Lyall, Front-End Developer for Sirportly<\/span><\/a>. \u201cIt’s tempting to leave all the worst items until last, or to write sloppy code to save some time, but if you’re working on a codebase that needs to be maintained, or worked on by other people, doing things right the first time is always the best option. You may be a little slower now, but you’ll save you and others around you a lot more time in the future. Utilise tools like SCSS Lint for your Sass and JS Lint\/JS Hint\/Karma tests on your JavaScript.\u201d\n<\/p><\/blockquote>\n

4. Stop hammering nails with a screwdriver<\/h3>\n

It\u2019s a common problem that kills productivity on a daily basis. Companies provide their developers with inadequate tools (or none at all), just to save money. <\/p>\n

It\u2019s like telling a carpenter to pound nails with a screwdriver because hammers are too expensive.<\/p>\n

The problem with this thinking: It doesn\u2019t save money. The productivity lost with inefficient tools far outweighs any cost savings gained. If purchasing the right tools will cut your development time in half, how much is that worth over a month? Over a year? You might be surprised.<\/p>\n

\n\u201cThe most productive developers understand the importance of good tools,\u201d says Tyler Wassell, Software Development Manager at mrc<\/span><\/a>. \u201cThe right tools will not only eliminate repetitive coding tasks, they will also fill gaps in their skillset–letting them accomplish more than they could coding from scratch.\u201d\n<\/p><\/blockquote>\n

5. Rethink your schedule<\/h3>\n

\"photo
photo credit: photosteve101<\/a> via photopin<\/a> cc<\/a><\/figcaption><\/figure>When are you most productive? For some, it\u2019s the morning. For others, it\u2019s late at night. Everyone is different. The problem is, most developers are forced into the same 9-to-5 schedule. Why is that a problem? We\u2019re seeing increasing amounts of research<\/span><\/a> indicating that this may actually hamper productivity.<\/span><\/p>\n

\n\u201cIn my experience, web developers tend to be late night people,\u201d says Chloe Carmichael<\/span><\/a>, a Clinical Psychologist. \u201cAs extremely quick thinkers with high IQ, they are always interested in ways to boost or maintain productivity. I often find that developers forcing themselves to adhere to a 9-5 schedule, deliver sub-optimal results and start having a lower self-perception as they start believing that they are simply not productive. To enhance productivity, I recommend giving themselves the freedom to arrange their schedules around the times they are most productive. Once they let go of the 9-5 idea, they can identify their own peak hours and create their own schedule accordingly, even if it is from 10 pm to 6 am. This often re-connects them with many of the facets of the 9-5 lifestyle that they actually did like – such as an established routine and a sense of when to call it a day.\u201d\n<\/p><\/blockquote>\n

So, what do you think? Is there anything you would add to this list? If so, please share your thoughts in the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: What is a “productive developer,” and how do you become one? If you’re a developer, or if you run a team of developers, this article defines the term and offers some actionable tips to improve development productivity.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-global-header-display":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","slim_seo":{"title":"5 simple tactics to boost development productivity - mrc's Cup of Joe Blog","description":"Summary: What is a \"productive developer,\" and how do you become one? If you're a developer, or if you run a team of developers, this article defines the term a"},"footnotes":""},"categories":[8],"tags":[15],"class_list":["post-8113","post","type-post","status-publish","format-standard","hentry","category-education","tag-web-development"],"_links":{"self":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/8113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/comments?post=8113"}],"version-history":[{"count":9,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/8113\/revisions"}],"predecessor-version":[{"id":8372,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/8113\/revisions\/8372"}],"wp:attachment":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/media?parent=8113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/categories?post=8113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/tags?post=8113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}