Swizec Teller - a geek with a hatswizec.com

    Software dev isn't just a logical process

    Mito Art Tower by Arata Isozaki

    A very cool post by Jason Rudolph entitled How to Level Up As Developer made the rounds around the internet today. The basic premise was that defining progress for programmers and/or developers is a very difficult thing. Many good points in there, but I have a small bone to pick with this part:

    And as logically-minded developer types, the lack of a well-defined route can make for a daunting journey from novice to master.

    This perception of developers is something I've noticed a lot pretty much everywhere. People almost invariably think of developers as these logical people who like to keep things orderly, always categorize everything and are generally displeased with things that aren't very engineering-like.

    It sucks!

    That kind of perception paints programmers as boring people, some kind of real-world Vulcan almost.

    Granted, this might be true of the sort of programmer who uses Java with love, works in a cubicle farm somewhere and simply has never been exposed to the true joy of programming. The artistic side of it all. (and I feel very sorry for them indeed)

    I've argued in the past that programming is more akin to writing poetry than it is to this rigorous discipline we like to call engineering. Some have even likened programming to tending a garden.

    Art is the product or process of deliberately arranging items (often with symbolic significance) in a way that influences and affects one or more of the senses, emotions, and intellect.

    Wikipedia clearly states that art is about arranging abstract things into something new that makes us feel something, or just makes us think. A very broad definition, but software development fits the bill perfectly.

    I'm guessing a lot of people do actually approach software development as a rigorous discipline where you take a problem and chip away at it with the available tools until it is solved. In some cases, like real-time systems, this is probably a good thing too.

    For me, that approach has never really worked. I like to take a more artistic approach to solving hard architecture and algorithmic problems.


    Inspiration is key.

    I find that writing code from a more inspired perspective produces results that are much more beautiful to behold, that work better, sometimes even work faster, and are most of all more pleasurable to come up with. It sometimes even lets me come up with solutions completely unachievable through a series of logical steps.

    A lot of great ideas come to people when they are busy doing something else and just let their mind wander. This is why many claim that they get the best ideas under the shower, or on the crapper, a certain man was also known to get a lot of ideas while pushing papers as a patent clerk ... it's all about disengaging yourself from the problem, thinking about it somewhere in the back of your head and waiting for inspiration to strike.

    Thing is, by lumping programmers into this Logical People (tm) group and thinking of software development as a Logical Process (tm) you are actually making a great disservice to pretty much everyone. When developing software we aren't just solving a problem through a series of logical steps.

    We are creating solutions!

    Software development is an inherently creative process and I think it should be considered as such. Perhaps then there would be more beautiful code in the world. There would be more happy developers. And the world would be a better place to be as a result.

    If software development was seen as a more interesting funtastic field, perhaps we wouldn't be seeing declining freshman enrollment into studying what is essentially the most important industry of our time since it runs pretty much everything.

    Enhanced by Zemanta

    Did you enjoy this article?

    Published on August 10th, 2011 in Companies, development, Java, Programmer, Programming, Software developer, Software development, Uncategorized

    Learned something new?
    Want to become an expert?

    Here's how it works 👇

    Leave your email and I'll send you thoughtfully written emails every week about React, JavaScript, and your career. Lessons learned over 20 years in the industry working with companies ranging from tiny startups to Fortune5 behemoths.

    Join Swizec's Newsletter

    And get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.

    "Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"

    ~ Ashish Kumar

    Join over 14,000 engineers just like you already improving their careers with my letters, workshops, courses, and talks. ✌️

    Have a burning question that you think I can answer? I don't have all of the answers, but I have some! Hit me up on twitter or book a 30min ama for in-depth help.

    Ready to Stop copy pasting D3 examples and create data visualizations of your own?  Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization

    Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.

    Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created bySwizecwith ❤️