DEV Community

Cover image for How I became a senior javascript developer with personal projects
Afonso Pacifer
Afonso Pacifer

Posted on

How I became a senior javascript developer with personal projects

Everything can be summed up in short words

One of the best decisions in my developer career was to go beyond just using tools.

I decided to create my tools, not for commercial propose, but to know how these technologies actually work and to improve my tech skills.

This is a short story about how this decision changed my life.

My first big challenge with a personal project

I've always been the CSS guy. In 2015 my passion for CSS took me quickly to the status of "reference" in my country (Brazil).

At this time, inspired by my friend Raphael Amorim, I accepted the Write Code Every Day challenge. Basically I worked in open source projects every day for 1 year.

My github profile with 367 days of coding

Okay, but in my first days of coding, my javaScript skills were extremely limited.

Everything has changed when I received an invite to talk in Front in Valle (a big front-end conference in my country) that I could talk about any topic. So I had an idea as naive as it was brilliant. I decided to learn about javascript creating my own CSS preprocessor.

Banana CSS

Banana CSS logo

🍌 The Brazilian CSS superset.

In 2016 I created the CSS preprocessor called banana CSS, the objective of this project was to learn javascript, but I ended up learning about Node.js, how to creating CLIs, lint, unit tests, JSDocs, continuous integration, data structures, AST, how to create gulp plugins, and more.

Preprocessor example with flexbox

Link to Banana CSS project.

Going deep in front-end development.

Okay, at this point I felt the necessity to learn more about javascript in the browser, so I thought about the main tool I daily use and came to the conclusion that it was React.js.

So...

millenium.js

In 2017 I created a project called millenium.js, the description for this project is:

millenium.js logo

A javascript library for creating Functional Stateless Components and render with Virtual DOM. Ideal for creating ultra-light and fast applications with Redux.

Or my favorite description:

🚀 Render your front-end in less than 12 parsecs.

In this project, I learned about performance, good practices for creating front-end libraries, algorithms, JSX, and more. Of course, I kept all the good practices from the old projects.

Example with Redux

See an online DEMO with Redux.

Link to millennium.js project.

Using my passions to explore new things

In 2018, after I watched the Ready Player One movie, I left the movie theater determined to create a game with javascript.

Creating a game with javascript is relatively simple, you can choose among a lot of tools, read the docs, experiment, and it’s done.

But, the natural decision (for me) was: Creating a new tool for creating games.

For this project, I decided to define some funny rules:

  • Don't use Canvas/WebGL.
  • Use only CSS to render animations.
  • Write a functional code.
  • Try to write the maximum of isomorphic/universal code as possible.

burnout.js

Finally, I created the burnout.js:

burnout.js logo

🎮 The 2D game engine for manage collisions.

In this project, I learned more about functional programming, DOM performance, algorithms (for calculating the elements collisions), and much more.

Game example

Link to burnout.js project.

Again, of course, I kept all good practices like unit tests, unit tests, unit tests, hum...

Triggers for projects from projects

At this point, I had a revelation:

OMG, why did I never think of creating my automated testing tool?

So...

N.O.M.s

🔮 Universal/isomorphic javascript unit tests for witches.

While working on burnout.js I built the N.O.M.s (my testing tool) and wrote 100% of the burnout.js unit tests using the N.O.M.s library.

What were the goals of creating my test library?

  • It should work in the browser and Node.js (isomorphic/universal).
  • Create all assertions in pure Javascript (not using browser APIs or Node.js modules).
  • Use Emojis.
  • Don't use a custom CLI for run tests.

Unit test example

Curiosity: I used mocha to write the N.O.M.s unit tests. Ironic but funny 😅!

Link to N.O.M.s project.

Was it worth reinventing the wheel?

After these personal projects (and a lot of others), in 2019/2020 I spend my time working on corporate products, creating complex Front-End applications, and leading a full-stack development team.

For my surprise, in the last years of open source development, I’ve improved my technical level a lot and I had no problems with implementing complex architectures using React.JS, immutable.js, web components, flux, tests, PRPL pattern, back-end APIs (node.JS/python), MongoDB, and a lot of tools/good practices for web applications!

Conclusion

I finish this blog post complementing the first paragraph:

One of the best decisions in my developer career was to go beyond just using tools, I decided to create them.

Thanks a lot for reading my first English blog post.

If you liked this content, follow me on Github and/or Twitter 💜.

Cheers.

Top comments (65)

Collapse
 
felipefialho profile image
Felipe Fialho

This is an amazing story! The best thing about it is because you make these projects, have studied and improved your skills without a natural pressure in a day a day of work.

You are one of the most brilliant Developer that I have a pleasure to know and your passionate about open source and personal development inspires I and a lot of another developers to improve too! ❤️❤️

Collapse
 
afonsopacifer profile image
Afonso Pacifer

YOU inspire me!
From Cartman's drawing to FrontEndBR community.
It's an honor to have you as a personal friend ❤️

Collapse
 
33nano profile image
Manyong'oments

" One of the best decisions in my developer career was to go beyond just using tools, I decided to create them"

  • That right there is golden
Collapse
 
afonsopacifer profile image
Afonso Pacifer

I'm very happy to read that <3

Collapse
 
matveyclark profile image
Matthew Clark • Edited

Awesome, thanks for sharing this. I think the key to progressing and learning as much as possible in this crazy industry of ours is constantly being proactive. We may not get a chance to work on some complex and interesting things at our full time jobs (especially in more junior roles), while side projects can help 'force' you to learn certain topics which later pay dividends.

The hardest part for me is the initial idea 😅

Thanks again

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Thanks for this amazing feedback :)
"side projects can help 'force' you to learn certain topics" - Perfect
Learning interesting things, regardless of your job is awesome for your personal growth!

The initial idea is coming hehee

Collapse
 
caiangums profile image
Ilê Caian

Awesome article! I knew it'll be good when I read:

"One of the best decisions in my developer career was to go beyond just using tools. I decided to create my tools […]”

But it keeps getting better and better as I'll reading it! I really believe in that way of think about things! 😄

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Amazing way of thinking ;)
Thanks for this comment <3

Collapse
 
klikas profile image
theodoros klikas

Very inspiring story Afonso! Its great to see your progress.

Are there resources that you used initially in your journey and while you progressed? What are some of the books/blogs/documentation you learned from?

I get it wasn't just about javascript but about structuring a complex project, software engineering in general etc.

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Greate questions!
I learn a lot using the W3C docs, all community posts, youtube videos, etc...
I basically search for "How you create a [complete here]"..

PS: I published a new post about my "gold rule" for learning new things:
dev.to/afonsopacifer/5-ideas-for-p...

<3

Collapse
 
jdnichollsc profile image
J.D Nicholls

Hey Afonso, thanks for share your story, this is very nice!
About Games, I was wondering if you can help me to add more interesting resources in this list about JS Games github.com/proyecto26/awesome-jsgames
Best,
Juan

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Wow...
Awesome project, I`ll try to contribute :)

Collapse
 
helderberto profile image
Helder Burato Berto

Awesome!

It's great to see people growing and sharing the ways did to do that.

I really appreciate Brazilians (like me) going deeper and catching a next level as a professional.

Congratulations to all your efforts, it isn't so easy to keep the consistency like you did very well.

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Wow, thanks for this awesome comment bro!
Let's show the Brazilians power for the world <3

Collapse
 
kellykels21 profile image
Marke'l Spellman

This is dope but scares me because I'm not this dedicated to coding.. dont get me wrong I love to code and have a passion project im slowly chipping away at but.. recreating tools seems so beneficial but not so interesting. What keeps you motivated ?

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Hello!
My motivation to recreate tools comes first from my interest in learning. Okay, but to stay motivated, I show progress with friends or other developers
(in my case through tach talks about the concepts).

Another cool tip to keep you motivated is: “Use projects to create other projects”. For example, you can create your personal website using your new front-end library. This motivates a lot, for bug fixes or improvements, because you are the user and at the same time the maintainer of the dependencies.

In the end, having a good answer when someone asks, "What tool did you use to do this?" It's priceless and it's amazing <3

Collapse
 
khizerrehandev profile image
khizerrehandev

Hey! Afono, I really want to be good JS developer I dont think I am very good in Dev. How to become master? where to take start? Thanks

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Hello!

A tip to get started is to focus on building a solid base!!

I recommend the books:

  • JavaScript: The Definitive Guide - David Flanagan
  • 14 Habits of Highly Productive Developers - Zeno Rocha
  • You Don't Know JS Yet (book series) - Kyle Simpson

:)

Collapse
 
khizerrehandev profile image
khizerrehandev

Thank you so much!

Collapse
 
matiasdandrea profile image
Matias D • Edited

Finally, Thank you! "Don't reinvent the wheel" it's a waste of time only for companies or if you are running a business. If you wanna learn "reinvent the wheel" is the best way, and, if you(when you) get stuck you can simply see how great developer already solved the problems you are facing on.

P.s. I'm not an English native and I'm learning it, please feel free to correct me, thank you :)

Collapse
 
afonsopacifer profile image
Afonso Pacifer

Great comment! Thanks <3

PS: I'm learning English too! Is hard, but the power of communication is awesome!

Some comments may only be visible to logged-in visitors. Sign in to view all comments.