What can developer learn from taking art classes
Tags: career, discuss, art, learning
Published: 2019-02-08 14:05:56

---
title: What can developer learn from taking art classes
published: true
description: 
tags: career, discuss, art,learning
cover_image: https://images.unsplash.com/photo-1503409098-1e546aa1af1e?ixlib=rb-1.2.1&auto=format&fit=crop&w=1567&q=80
---

  Hello guys :wave:, a few months ago I decided to try something new and start attending an academic drawing class. I was always impressed by stunning artworks, but I never tried to do something by myself. 
My last drawing attempt was back in the school days and I never thought I will do it again :smiley:.

  For me, it all started from reading classical [Hackers and Painters](https://www.amazon.com/Hackers-Painters-Big-Ideas-Computer/dp/1449389554) book by [Paul Graham](http://www.paulgraham.com/). In one of the chapters, the author drew a clear parallel between art and "hacking", and bring solid statements that developer work in most cases is closer to art than science field. 

I decided to check it on my own and after all that time communicating with artists and exploring this field I found that mostly mindset of a creative person not much different from a techie. Even more, we share lots of common ways on how we think about a problem and solve it. So here are some key notes I made so far.

# Master fundamentals :books:

<img src="https://instagram.fdnk1-2.fna.fbcdn.net/vp/ceff6739a57919a00d2b48d324637db5/5CE6B26F/t51.2885-15/e35/32788416_791106627766187_1868360251783249920_n.jpg?_nc_ht=instagram.fdnk1-2.fna.fbcdn.net" width="350px">
 
  This may seem obvious on first place but think about all these new shiny technologies and tools coming every month or even weeks. It is easy to get lost in the hype, but mostly, they all share common underlying concepts.

  Any good artist firstly starts by exploring simple shapes, to form a solid foundation and only after that progress to make some harder objects as the most complex ones are just well-formed groups of simple primitives. 

  This is truly relevant to programming, instead of learning new trendy framework etc. try to think about what concept it implement and what underlying research was made.

# Ignore details on first stages :point_up:

<img src="https://thepracticaldev.s3.amazonaws.com/i/nn1cqj9k0ypzzraqu2ba.JPG" width="350px">

When you try to draw some shape, it is easy to forget about the whole object while you focus on a single thing. My teacher always tells that well-formed object even with some nuances lost, will always look better that one that has lots of details but not solid grouped form. 

Now think about making software project, adding details (unnecessary dependencies, pre-mature optimization, complex abstractions) on first phases will add danger to it. Instead, try to come with some "just working" solution, even if it is not too pretty yet. 

> *"Premature optimization is the root of all evil (or at least most of it) in programming." (c) Donald Knuth*

Strive for progress, not perfection. A project will become more complex over time, so adding unnecessary stuff on first steps can potentially make it not scalable. That why in my opinion [KISS](https://en.wikipedia.org/wiki/KISS_principle) is the most important concept to follow. 

# Recognize common patterns :clipboard:

<img src="https://instagram.fdnk1-2.fna.fbcdn.net/vp/735fe9e2629ef871680edba112133818/5CE67846/t51.2885-15/e35/39304319_2146269228780130_3597159771825766400_n.jpg?_nc_ht=instagram.fdnk1-2.fna.fbcdn.net" width="350px">

  For example, look at this drawing, it is a pretty classical diaper fold. From the first look, it may be hard for a novice to understand where to start from, but if we look closer we can see that mostly this complex shape consists of simple primitives like cones, with smooth transitions between them. Identifying these patterns is very important for an artist.
 
  This is a great visual demonstration of why studying [design patterns](https://sourcemaking.com/design_patterns) is crucial for a good engineer. Knowledge and, even more important, ability to correctly detect and apply them on your project, will make your code robust and easier to follow.


# Conclusion
<img src="https://instagram.fiev10-1.fna.fbcdn.net/vp/2e2bcf5999390f973c3fdfd9871f1671/5CEE06C6/t51.2885-15/e35/49933482_1025602667563468_1841351465186509710_n.jpg?_nc_ht=instagram.fiev10-1.fna.fbcdn.net" width="350px">

After my short "experiment" I can confidently say that it is very useful to explore new fields and look on known things from different angles. Studying new skills, even that are not directly relevant to your profession, could make you a better problem solver and give you a fresh view on common problems.

Thanks for your attention :pray:

PS. What are some fields besides software development, you are currently exploring 🤔?  Share in comments. :point_down: