The Modular JavaScript book series glowing over the desktop of an eager learner.

📚 I’m writing a book series called Modular JavaScript! Help me crowdfund the effort 👋 and crowdshare the word 🌩. Follow @mjavascript on Twitter 🐦.

Nicolás Bevacqua

JavaScript and Web Performance Consultant
Disclaimer: it might be possible that I don’t look this good anymore.

I am Nicolás Bevacqua and I ❤ the web. I founded Pony Foo as a blog in late 2012. Early in 2016 I launched Pony Foo Weekly – a newsletter about the open web, highlighting the most important news every thursday. Now the platform is open to guest posts from contributing writers.

You can join us if you’d like!

I am a consultant, a conference speaker, the author of JavaScript Application Design, an opinionated blogger, and an open-source evangelist. I participate actively in the online JavaScript community as @nzgb on Twitter – as well as offline, in beautiful Buenos Aires.

I like writing about the current state of the web, new features coming our way in ES6, leveraging web performance optimization to make our sites much faster, the importance of progressive enhancement, sane build processes, and improving quality in your applications with modular design. I used to spend a lot of my time answering questions on Stack Overflow, but now I spend most of that time doing open-source work instead.

I really enjoy developing small open-source modules that I publish to npm and GitHub. Some of these are small utilities that work well in both Node.js and the browser, and some others are front-end components that make it easier to use certain parts of the web. My favorite approach to open-source is developing small modules, because that way you can compose your code in interesting ways while also fostering reusability. Learning how to write modular code is one of the most valuable things you can do to improve your skills as a JavaScript developer.

I have used a variety of tools when it comes to development. Trying out many different tools, creating some of your own, and experimenting are the best ways to really understand how they work and the tradeoffs between all the different tools and frameworks out there. I favor simple solutions. That’s why I prefer to use npm run and Bash in my builds. I also like React and Taunus when it comes to view rendering, because they’re simple and well-performing solutions. I use AWS for deployments because I like having fine-grained control, but I’ve also experimented with other providers like Heroku and Digital Ocean.

Re-inventing the wheel is a necessary evil if we want to learn from mistakes made in the past (regardless of who made them).