I used to think art required a certain mood.
The right lighting.
The right soundtrack.
A clear head.
That was a lie.
Art works the same way software does. You don’t wait until you feel ready. You start before clarity exists. The clarity shows up through friction.
When I draw now, I don’t aim for perfect. I aim for finished.
A finished sketch teaches more than a perfect outline that never leaves the canvas.
There’s a discipline to art that most people miss. It isn’t about inspiration. It’s about iteration. You draw something. You hate parts of it. You adjust. You redraw. Over time, your eye sharpens. Your hand steadies. Your standards rise.
That’s architecture. That’s performance tuning. That’s product craft.
When I work in SwiftUI, I care about startup time and memory.
When I draw, I care about line weight and restraint.
Both are systems.
Both reward patience.
Both punish ego.
Art also exposes something software hides: you can’t abstract emotion away. You either put yourself into the work or it looks hollow. There’s no compiler warning for that.
The biggest shift for me wasn’t technical improvement. It was accepting that discomfort is part of the process. The piece looks wrong halfway through. The proportions feel off. The shading fights you.
That middle stage is where most people stop.
Finishing is the skill.
The more I treat art like shipping, the more consistent it becomes. Small pieces. Public iteration. No dramatic announcements. Just work.
You don’t need to feel like an artist to make art.
You just need to sit down and finish something.
— Gary
⸻
If you want, I can also:
• Make a shorter, punchier version
• Make one more emotional and vulnerable
• Or make one more technical, tying it deeper into your dev identity