Learning & Software Development. Multi-skilled Developer
Join the DZone community and get the full member experience.Join For Free
you are having your first project. in the beginning, you know almost nothing about programming languages, business domain, development process, efficient practices and other good things. in the beginning, you know almost nothing about political games, external factors, progress reporting, human stupidity, fear of mistake, boredom and other bad things. you can’t do your job effectively. suddenly, in 10 years, you are becoming a great software developer. or you buried by mediocrity and never ride the wave. why? what should you do to advance or just survive?
i think one of the most important factor is perpetual, passion learning. learning is the most important thing that drives software development forward. learning is the most important thing that drives you, as an individual, forward. it drives your team, as a group of people, forward.
source: ashiro’s labzone
i believe, learning is a key attribute of a good software development process. process that empowers learning will work, process that impede learning will fail.
basically there are three levels of learning. first, you learn as a person. then you learn as a group of people. finally, you learn as a whole organization. this post focuses on a personal learning.
i have own vision on software development. most likely it is caused by my personal background and products i’ve worked on (all of them web-based).
software developers solve problems. to solve a problem in a cool way, you need to be a multi-skilled professional with quite solid knowledge from as many related disciplines as possible. only this will give you a complete vision of the best possible solution.
deep specialization vs. broad knowledge
we are stepping on a slippery ground of deep specialization vs. broad knowledge. my belief is that on the current stage broad knowledge is better. why? i can provide some analogies that prove nothing, but still interesting.
software development is a young discipline. it has its own properties that are not fully understood by most people. you can’t apply mass-production to software development so far, since you can’t formalize it enough. you can’t write product specification, create design and generate complete application from uml diagrams (yes, i am aware about model-driven development, but it is not even close to mass-production).
look, there are so many related topics, from psychology to programming languages, from toc to pair programming. there is no best way to write software so far. if you can’t apply mass-production to software development, you can’t do it efficiently with people who has very narrow specialization. you can’t put it on a conveyer.
let’s take science and look back for 300 years. we will see that many
discoveries were made by generalists. let’s check wikipedia.
- isaac newton: physicist, mathematician, astronomer, natural philosopher, alchemist, and theologian.
- galileo galilei: physicist, mathematician, astronomer and philosopher
- christiaan huygens: mathematician, astronomer, physicist, horologist, and writer of early science fiction
- rené descartes: philosopher, mathematician, physicist, and writer
it was common 200-300 years ago. in modern science you can’t discover anything without deep specialization. there are people who has broad knowledge, but it is rare these days. more often you will find people like:
- barton zwiebach: string theorist
- max tegmark: cosmologist.
- david joseph bohm: quantum physicist
there are rare exceptions for sure, like this one:
- stephen wolfram (born 1959): physicist, software developer, mathematician, author and businessman.
what is the point? software development is not a science obviously neither ‘tangible’ industry, so all such analogies don’t prove anything. but i think software development is somewhere at 17 century in comparison with science and in 19 century in comparison with usual industry.
taken this speculation into consideration,
team of generalists with some specializations can create a better software than a team of highly specialized people
. it is not obvious and we need to evaluate this assertion. i can throw some arguments:
- architecture . developer may know nothing about testability. as a result he creates hard-to-test solution. high specialization can lead to local optimizations, but weak architecture as a whole. if no one understands how does it work as a whole — it’s a bad sign.
- fragility . highly specialized team hardly pass a “bus test”. if one of the key persons will be hit by the bus, development will stop.
a multi-skilled software developer
i believe in multi-skilled software developers. the right question to
ask is “how much skills should i have and how deep?” it really depends,
but here are the skills/domains/attributes every great web developer
should have. the list is sorted by priority and i put hours that should
be spent on formal education:
- curiosity and passion
- self-reflection / problem solving
- user experience (1000 hrs)
- programming (oop/ood, tools, practices, etc.) (8,000 hrs)
- testing (200 hrs)
- “sense of beauty” (graphic design, visualization, etc.) (200 hrs)
i insist that these skills are very important for any really great web developer , but they may vary depending on software development type. i expect questions like “ why the hell you put user experience before programming? ” the reason is that ux is an important part of problem solving. it is more important than implementation itself. ux gives developer a right perspective and affects solution highly. without ux you can beautifully implement a crappy solution and 90% of existing software does exactly that is exactly that. they are crappy, unusable and bloated with unnecessary features.
great developer should have a “sense of beauty”. it’s hard to formalize, but in general he should be able to say “this button is ugly” and “this menu is beautiful”. “sense of beauty” is a very important property, it affects everything: visual design, documentation, architecture, source code. everything. you can (and should) train it.
in the next post i will share my vision on learning as a team.
Published at DZone with permission of Michael Dubakov, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.