Pro Developer - Optimize Your View

For anyone who spends a lot of time writing user interface code, optimizing the view immediately conjures up images of windows, clever little UI gadgets, usability issues and a long string of design meetings with excitable and over-caffeinated programmers. The fact that these little get togethers may very well involve airborne white board erasers traveling with great velocity and purpose is just another testament to the passionate importance we place on how our software is presented to our customers.

Indeed, the portal through which the user peers into the depths of our code often seems to define the software itself, at least in the eye of the beholder. Consequently, we acknowledge that user interface issues are not just a matter of putting on a pretty face, but in fact define the boundaries within which our users will operate. Put a clunky view on a good piece of software and you end up with a clunky piece of, well, software.

However, those of you who have already fired up your programmer’s editor and called in your order for a pepperoni pizza in anticipation of yet another exciting session of coding are probably getting a little ahead of the game. We’re not here to talk about the bits and bytes of coding. We’re here to talk about something much more important – your future as a professional software developer. So, you won’t be needing that programmer’s editor for the moment. The pizza’s probably still a good idea, though. Some traditions should never be changed.

Setting Priorities

If we’re not going to talk about functions and objects and squiggly little lines of incomprehensible text, then what on earth are we here for? What could possibly be more important to a developer than the details of writing code? The answer is both obvious and elusive in the same breath. The most important thing to programmers everywhere is not writing code, but rather delivering quality software.

Did you just stop, shake your head and read that last sentence again? You’re not alone. Almost universally, good programmers reflexively equate writing code with delivering software, as if they were one and the same thing. They are not. In fact, it is this very view that is largely responsible for release disasters worldwide.

If you don’t know what a release disaster is, you’ve led a charmed life. Take two donuts out of petty cash and go back to what you were doing. The rest of us are all too familiar with the details of good releases gone bad, including arbitrary deadlines, endless overtime, high stress levels, short tempers and monitors flying out of fifth floor windows, all for a product that gets shipped long before it’s ready due to market pressures. When your software hits the streets with more bugs than a cheap motel and less stable than a maintenance programmer who hasn’t slept in a week, are the technical details of coding really the guilty party? Not likely. I can assure you, some of the worst software releases I’ve seen were the product of absolutely brilliant technical minds. Let me present that thought once more, for emphasis. Poor quality software releases are almost never due to a lack of technical skills.

So, if the project you’re working on is greeted by the user community with those two immortal words dreaded by programmers everywhere ("it sucks!"), then who’s the culprit if not the code? The programmers, of course. Hey, you didn’t think you were going to get off the hook that easily, did you?

The Usual Suspects

I’m beginning to see some glazed eyes in the back of the room. If bad releases aren’t caused by poor technical skills, then how can it be the fault of the programmers? Well, in fact, we’re going to invoke a little pretzel logic here. Not the straight, matchstick sized ones that are also good for stirring your drink, but those twisty, winding type pretzels that take a lot of turns but always end up right back where they started. We’ll start by rounding up all the usual suspects, but trust me, in the end it’s all going to come home once more to rest right in our own laptop filled little laps. Pretzels are like that.

In fact, many of the veterans here have already made a list of the parties responsible for screwing up a perfectly good project, and have even made suggestions regarding exactly which wall they should be placed against when the revolution comes. Some of the more seasoned among you may have even suggested that the lawyers must wait their turn, or use another wall.

Who are these villains, these people powerful enough to override the capabilities of even the most brilliant coder? Marketing and management are certainly the first to come to mind, often known as Weasels and Suits when programmers are hanging out by the cappuccino machine late at night. When turned loose on an unsuspecting software development team, the results inevitably include vague and shifting requirements, arbitrary deadlines declared with no concept of the technical realities, scope creep, crisis driven management, complete lack of a professional testing department and in the end, software that was released long before it should have been.

It’s Not My Job

What’s that you say? I’ve just clearly proven that it’s not your fault? Nice try. And pass me a pretzel, will you? Projects fail for an unbelievably simple reason. Extremely intelligent and otherwise talented programmers time and again make the naïve assumption that if it’s not about the code, it’s not their job. In modern air to air combat, a jet fighter pilot who finds himself close enough to his opponent to fight it out with machine guns has already missed critical opportunities to solve the problem from a safe distance with long range missiles. And so it is with programmers. If you find yourself in Overtime City with a guaranteed release disaster right around the corner, you screwed up long before then by failing to control your situation before it controlled you. Ouch. Can I say that? Well, maybe I should at least have offered you a pretzel first.

Your view of the software development process dictates what you do, and do not do, in the course of your work week. If you believe that everything beyond coding is "not my job", then you and your project will without question fall prey to the strong and illogical forces that sweep through the corporate world. However, the follies of marketing and management can both be minimized by the savvy programmer. For every bone headed thing that these rocket scientists can throw at us, there is a counter. Manage the problems early enough in the game, and your release disaster instead becomes a release party. They’ll probably even spring for the pizza.

The Road Ahead

You don’t have to have an MBA or be a sales weasel to effectively manage these problems. You just have to expand your view of the software development process to include anything that might effect your release, and do what’s necessary to protect the code you’ve worked so hard to create. Granted, this isn’t always as sexy as writing a flashy UI in the cool language of the day, but when it’s 4 AM, you haven’t slept in 3 days, and poor management decisions all but insure that tomorrow your product will ship in less than perfect shape, nothing’s sexy.

It’s time for programmers to regain control of the software development process. Learning sneaky and not so sneaky tricks to deal with all the non-coding issues that threaten our programs, our free time and our sanity is what we’ll be doing in the months ahead. Step by step, issue by issue, we’ll look into ways of seeing disaster before it strikes and taking preemptive steps. The end result will be more time doing what you really love – writing cool code that becomes the next Killer App. And isn’t that really what you signed up for when you chose this profession?


Category: business Time: 2002-12-03 Views: 0

Related post

  • Pro Developer - Improve Your Career in Any Economy 2002-11-23

    Like many other areas of business, the tech industry has weathered the occasional slump over the past few decades. It's only natural that the fate of techies is closely linked to the tides of the business. However, in any economy, weak or strong, som

  • Pro Developer - Creating Your Dream Project 2002-12-10

    Some guys have all the luck. You know the type. He's got a wide screen flat panel monitor on his desk that you could use for the screen at a drive in movie. The computer tucked under his expensive oak desk has more processing power than the WOPR out

  • What are the pros and cons for having a dedicated T-SQL developer on your team? 2012-09-28

    Our T-SQL developer just gave his two weeks notice. We have been asked if our team of four developers would like an additional developer. We are offered to do our own T-SQL / Entitiy Framework development or we could get another dedicated T-SQL devel

  • Cold, neutral attitude to programming languages - sign of a pro developer or not 2013-05-25

    A profesional developer Zed Shaw says this: Which programming language you learn and use doesn't matter. Do not get sucked into the religion surrounding programming languages as that will only blind you to their true purpose of being your tool for do

  • Methodologies/tools for when developing on your own 2011-09-29

    Suppose you have to develop a medium+ sized software, fully on your own. Like if it was a personal project you want to accomplish. What methodologies/tools would you use to define what needs to be developed, learned and have a global idea of what the

  • Convert your views into a custom module 2012-12-06

    A while back I read an article how you can take your views and put it in your "custom' module folder (granted you've set this up for custom theme functions). I haven't had much need for it lately, but recently I've been doing a lot of work for a clie

  • Optimize your Web Copy 2001-11-05

    Do you have trouble getting your message across? Do lengthy sentences and rambling paragraphs reduce your impact? This is the Web, and it's no place for overly-delicate expression. Get to the point and your readers will thank you. Skirt around its ed

  • How Google Really Wants You to Optimize Your Site 2009-03-07

    Does Google care for SEO? Yes, it does: from Google's SEO Starter Guide (pdf) to help provided in the Google Webmaster Help Forum, the search engine is pretty transparent when it comes to how it prefers you to optimize your site for inclusion. We'll

  • If you optimize your PC should you expect faster website load times? 2010-02-04

    Let's say that you recently ran one of those PC optimizer programs. I think it's fair to expect faster boot times, and faster application load times. But, is it fair to think that your websites should load faster or have a better experience browsing

  • What is your view using mac pro 8 core 8 GB system for software development? 2011-03-20

    I have never used Mac system before but I am considering switching to Mac Pro 8 core 8 GB model. Currently I am using Linux box based on Dell Core 2 Duo with 4GB ram (that is maximum it can have). I am running into performance issues and sluggish app

  • Using the Battery Status API to Optimize Your Development 2015-12-01

    Imagine if you could program your app to adapt to the end user's device - such as turning off certain processes if the user's device has a low battery status. Well, you can. The Device APIs Working Group is a series of specifications drafted to provi

  • 30 Screen Capture Tools for Sharing Your View 2010-01-05

    Yesterday, I wrote about the possibility that you will need some way to provide remote support for clients when you work virtually, even if it's just on an occasional basis. I touched on three of the ways you can provide these support services beyond

  • Form development optimization 2011-10-26

    Like many web developers I do forms all the time. I found myself doing the same all the time: placing input fields, assigning a name to each, ajax the form, then create the PHP which involves to assign a PHP var to each $_REQUEST['var'], escape and v

  • Pro Developer - Throwing Money Out the Window 2002-12-16

    It's common knowledge among programmers that most of the ills of the software industry, and most particularly the companies where we work, could be solved by simply letting the technical people make the technical decisions. In fact, that sounds so ob

  • Pro Developer - This is Business 2003-02-24

    I've been paying the rent as a professional software developer since the 80s. I've also worked both full time and part time as a musician for longer than that. In my travels, I've come to recognize a great many similarities between programmers and mu

  • Save Some Cash: Optimize Your Browser Cache 2008-12-18

    There are many factors to consider when optimizing the download time of your web page. The one golden rule, however, is to minimize the number of HTTP network requests made by the browser. Those HTTP requests (and responses) are resource intensive, s

  • What's your view on the direction of GIS? 2011-12-13

    I am a long standing GIS developer and consultant. I am often asked, is there still a place for Desktop GIS, to which I, currently, answer, of course; if there are jobs specific to individuals, you shouldn't be developing enterprise solutions for the

  • Beginners guide to developing optimization software 2011-12-21

    I am novice in "serious" programming i.e. applications that deal with real-life applications and software projects that go beyond school assignments. My interests include optimization, operations research, algorithms and lately i discovered how

  • Add more drive capacity to MacBook Pro an optimize for performance 2012-05-28

    I have a MacBook Pro (MacBookPro6,1) that came with a 500GB Seagate 7200rpm disk (ST9500420ASG) Having already maxed out the RAM to 8GB now I want to: optimize drives for performance add more capacity a backup plan I decided to ditch the optical driv

iOS development

Android development

Python development

JAVA development

Development language

PHP development

Ruby development


Front-end development


development tools

Open Platform

Javascript development

.NET development

cloud computing


Copyright (C), All Rights Reserved.

processed in 0.916 (s). 13 q(s)