Recently I began to wonder how the Pareto principle applies to web development when it comes to the "knowledge VS salary" equation.
Have you ever heard of it?
for many events, roughly 80% of the effects come from 20% of the causes Vilfredo Pareto
Can you answer these questions?
- What is, in Web Development, the 20% of the knowledge that makes the 80% or our salary?
- Is it worth to learn the other 20%?
Keep It Simple 🙂
In this post I DON'T take into account personal satisfaction and self actualisation. That would be way to complicated and personal to discuss.
Let's just focus on how "knowledge that YOU OWN" relates to "money that YOU MAKE".
Here is my story:
2006 :: 100 coins/month
2016 :: 160 coins/month
HTML5, CSS, Sass, Less, PHP, NodeJS, ReactJS, Angular2, responsive design, TDD, BDD, Git, GitFlow, SCRUM, Docker, high availability, micro-services, mobile development, browser performances, server side performances, memory profiling, team management, project management, invoicing, architecture, best practices, statefull / stateless services, development patterns, web components, MySQL, PostgreSQL, MongoDB, CouchDB, Redis, RabbitMQ, data flow patterns, event emitters, reactive programming, ...
Hence my understanding of it:
...after 10 years of running web projects (both successful and not), tons of hours invested in self-development, money invested into conferences, having moved to another country to follow my dream career, 1.5 new languages learned (English, Swedish), and more...
in 2016 I make barely 60% more than when I started 10 years ago!
... and while I was expanding my knowledge, the cost of living grew too!
(That so called inflation)
According to the average european inflation over the last 10 years my salary would probably have grown up to 130 coins/month even if I didn't move my knowledge forward.
So my knowledge impact on my salary accounts for only 30 coins / month over a period of 10 years.
Hence my questions for you:
- is that ok?
- is that a lot?
- is that worth the effort?