_The mind of a wandering software poet _is a piece trying to depict what the true creators of software think like. We all know there are many coders out there who think of themselves as good, but they are not artists and it is only the true artists in software development that create beauty through code, magnificence through design and otherwise make a true art out of the craft. Everyone else is just mindles peons bashing at their keyboards, making products people hate and despise.
Beautiful design, however, often goes unnoticed. People don't see the code, managers don't care for beauty and sexy, all they care about is productivity. This is why, with this piece of art, I sought to point out the clash between what a programmer wants and what they are forced into doing by circumstance. The roses depict seeking ultimate beauty while the small and scattered chrisantemes try to show how much random nuissance comes into play with development.
Scattering the pieces of paper with code amongst the beauty I tried to show the way a true programmer thinks - constantly scraping code that is less than perfect, constantly thinking in several threads, keeping wildly different parts of the project in their mind at all times. These papers then try to live amongst the petals in hopes of learning from them, in hopes of improving, of becoming as beautiful and perfect as The Rose.
The background is transparency, the foreground a computer GUI, these depict clairvoyance to see far ahead - predicting problems before they arise, and the basic tool of every programmer.
Good code is poetry.
Continue reading about The mind of a wandering software poet
Semantically similar articles hand-picked by GPT-4
- Software dev isn't just a logical process
- Heaven is where your code lies
- The code is not the goal
- Your code doesn't matter
- A quick quip
Learned something new?
Read more Software Engineering Lessons from Production
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 👇
Software Engineering Lessons from Production
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
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
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
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 ❤️