📎 Webclip
How I Became a Senior JavaScript Developer with Personal Projects
The author says the decision to build his own tools changed his career. He used personal projects to learn how technologies work, improve his skills, and move from limited JavaScript knowledge to broader front-end experience.
Reading notes#
- He began by working on open source every day for one year as part of the Write Code Every Day challenge.
- He created banana CSS to learn JavaScript and ended up learning Node.js, CLI creation, linting, unit tests, JSDocs, continuous integration, data structures, ASTs, and gulp plugins.
- He then made millenium.js to learn more JavaScript in the browser and study performance, front-end library practices, algorithms, JSX, and Redux.
- After watching Ready Player One, he decided to create a game-related tool instead of just a game.
- For burnout.js, he set rules such as not using Canvas or WebGL, rendering animations with CSS only, writing functional code, and maximizing isomorphic code.
- Through burnout.js, he learned more about functional programming, DOM performance, and collision algorithms.
- He also built N.O.M.s while working on burnout.js and used it to write all burnout.js unit tests.
- N.O.M.s was designed to work in the browser and Node.js, keep assertions in pure JavaScript, use emojis, and avoid a custom CLI for running tests.
- He says these personal projects later helped him work on complex corporate products and lead a full-stack team.
- He concludes that creating tools, not just using them, was one of the best decisions in his developer career.
