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.
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)
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.
- Become a better programmer (abdulapopoola.wordpress.com)
- Education Needed for Computer Programming (thinkup.waldenu.edu)
- The opportunity cost of a broad skillset (rc3.org)
- Taking the Drudgery Out of Software Development With a New Set of Tools from the ReDSeeDS project (prweb.com)
- Software Superstitions (avdi.org)
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 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. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️