摘要：本文僅用于學習和交流目的，不得用于商業目的。今年，我們依然會組織。隨著語言的發展，這種情況將不再適用。本系列主要討論如何獲得這些高度模塊化的應用程序。這一系列內的后續圖書會討論測試及部署等內容。更多精彩，加入圖靈訪談微信

本文僅用于學習和交流目的，不得用于商業目的。非商業轉載請注明作譯者、出處，并保留本文的原始鏈接：http://www.ituring.com.cn/art...

Nicolas Bevacqua，阿根廷人，是一位富有激情的JavaScript工程師，熱衷于打造健壯的構建流程和清晰的應用架構。喜歡談論關于JavaScript、性能、可維護代碼和開放互聯網的所有內容，曾多次在技術大會上發表web性能、ES6方面的知識分享。

2017年6月24日，Nicolas作為重量級嘉賓參加了“騰訊web前端大會”，分享《JavaScript的未來編寫方式》并參加圖書簽售活動。

大概10歲的時候，我上過一些學習Flash的課，也做些網站但純屬是為了樂趣。到了高中的時候，我開始做一些更有趣的項目，比如玩一款多人在線的角色扮演游戲——網絡創世紀。運行自己開發的服務器，實現游戲的特征。這段時間里，我學會了C#。大概做了兩年的時候，一個朋友告訴我“嘿，人們是愿意花錢讓你做這些事情的?！边@對于我來說太酷啦！是的，我想，這就是我如何開始編程的。

不，恰恰相反。我從來沒有覺得它是某種工作。我也不會因為把愛好變成了工作，就不再享受這份愛好。做自己喜歡的工作，這一點很重要。只有這樣，你工作的時候才不會感到痛苦。

五年前的技術社群要小得多。不過，現在我們有了Node.js大會、有了JS大會等，確實在慢慢變大。我所聯合創辦的Node.js大會是去年開始的。今年，我們依然會組織。我們希望把它變成一個定期舉辦的大會，人們才可以更多地參與到技術社區，而不僅僅是每年來那么一次，然后就完全忘了。

我們談話的這個時候，可能就有一個框架出現。重要的是，我們的主要任務不是跟隨那些耀眼的事物，而是更多地了解趨勢，什么是對我有用的、有幫助的。

如果兩年前開始的一個項目還在使用Angular，我就不需要認為Angular比React落后，Angular肯定會糟糕一些。是否使用某個框架取決于你的要求，總是去追求最新的技術是件很危險的事情。在一段時間內堅持使用同一種工具，講究工具的一致性是很有價值的。

此外，不被新技術落下也是很重要的。你可以，但是不建議你還在使用jQuery和HTML做網站。

關鍵是找到合適的平衡點。不斷豐富自己的知識，如果有時間就去嘗試一下。千萬不要因為是新技術就盲目嘗試。

首先，要弄清楚你適合哪種學習方式。有些人喜歡看知識截屏或者視頻演講。對于我來說，我在視覺學習方面的能力很差勁。我需要自己研讀。如果讓我看一段視頻，我會想要了解任何一種細節性的知識，反反復復看四遍。換做一本書或是一篇文章，我就可以很快掌握。我想說的是，你應該弄清楚自己是一個視覺型學習者，還是喜歡文本型內容的學習者。

然后，你就可以開始真正地學習JavaScript的基礎知識：句法、語法，等等。有了堅實的基礎，你就應該進入ES6的學習，掌握些特征。與此同時，你可能專注于某個單一的框架，Angular或者React或者其他任何一個框架，但一定要做到精通。你可以閱讀所有的文檔并瀏覽文件直到完全了解它的工作原理。

我用自己編寫的框架來學習事物是如何工作的。這是一個相當有效的方法，可以驗證些東西、編寫些技術工具。如果非要推薦一種學習資源，它應該是https://12factor.net。這是一個網站，它列出了從安全性、可擴展性等方面出發的12種不同的應用程序設計原則。我認為，人們應該了解它。

早期的時候，JavaScript基本上就是復制粘貼“如何做”。人們在網上找到一些代碼片段，復制粘貼到他們的網站，然后結束一天的工作。隨著語言的發展，這種情況將不再適用。

人們變得更加專業，開始開發一些JavaScript應用程序?，F在的JavaScript應用程序中有很多的模塊。起初，這些模塊都是相當大的?，F在，編寫小模塊變得簡單得多。

在我的系列叢書中，我試著教大家如何編寫出簡潔的、單目的模塊。原因是，人們希望編寫出專業的模塊，這樣就可以重復使用、測試，甚至在需要的時候給它提供官方文檔。最重要的是保證架構方面的可擴展性。當你有5個不同的模塊，每個模塊有5000行代碼的時候，事情會很難處理。如果你有5000個模塊，每一個都是100行的代碼長度，那么這就簡單多了。

本系列主要討論如何獲得這些高度模塊化的應用程序。這一系列內的后續圖書會討論測試及部署等內容。

How did you get started in programming?

When I was around 10, I had some classes using Flash. Also, I made websites for fun. In high school, I did a couple of more interesting projects, like playing the game called Ultima Online. I used to run my own server and implement features for the game. That"s how I learned C#.

After doing that for 2 years, a friend told me, “Hey, people actually pay you to do this.” It"s too cool to get paid. Yeah, that"s I guess how I begin.

Have you ever thought that turning love of role-playing games into a career will spoil your fun?

No, it"s the other way around. I never felt it like work to me. I would also never fall out of love with hobbies because I"m doing it for work. But it"s important to work on something you like. Then it won"t feel like torture when you’re doing it for days.

What does the tech community of your living place look like?

It"s much smaller 5 years ago. Nowadays, we have Node.js Conf, JS Conf and so on. It"s definitely growing. Node.js Conf started last year. This year, we will still run it. We plan to make it a regular thing so that people could engage more with the community, not just coming to this event once a year and then completely forget it.

There are lots of frameworks in JavaScript. How to keep up with the state?

There"s probably a framework coming out right now as we speak. The important thing is to know that the theme is not to follow those shiny stuffs. It’s more about figuring out the trends, what"s useful and helpful for me.

If I started one project 2 years ago, it"s still using Angular. I don’t really need to feel that Angular is a little bit lower than React and it must be worse. It depends always on your requirements. It"s very dangerous to go after the newest thing. The consistency of using the same tool for a while is valuable.

Also, it"s important to not be fallen behind. You can, but it’s not advisable to be still using jQuery or HTML for websites.

It"s about finding the right balance. Stay informed but try them if you have time. Be sure not to jump into everything just because it is.

Could you give us some learning steps of JavaScript in chronological order?

It"s really important to figure out how you learn things best. Some people love to read screen cuts or videos. I"m really bad at learning anything that I see. I need to read it. If I watched a video, I want to understand anything until I go over it like 4 times. When I read a book or article, I could get it. What I"m trying to say is that you should figure out whether you are a visual learner or if you prefer written contents.

Then you could start to really understand the basics of JavaScript: syntax, grammar, etc. Once you have a solid foundation, you should move into ES6 and learn features. At the same time, you might focus on a single framework, Angular or React, but be sure to be specialized on that. You could read all its documentations and browse files to figure out how it works.

I implemented my own frameworks to learn how things work. I think it"s an effective way to experiment and build things for yourself. If there were one source I would recommend, it should be https://12factor.net , which is a website that lays out 12 different principles for robust application design in terms of anything from security, scalability, etc. I think people should know it.

Currently, you are writing the Modular JavaScript book series. Why do you focus on modularity?

In the early days, JavaScript was basically on copy paste of "HOW". People find snippets of code on the internet that would give them comments for websites. They go to copy paste them into their site and call it a day. As the language developed, the case will not match any more.

People become to be more professional and started developing JavaScript applications. Now, JavaScript applications have lots of modules. At first, those were pretty big modules. It"s now much simpler to write small modules.

In my book series, I"m trying to teach people how to write concise and single-purpose modules. The reason is that people want modules to be specialized so that they can reuse them, test them, and even document them if needed. But the most important thing is scalability in terms of architecture. When you have 5 different modules, each one with 5,000 lines of code, it would be really hard to work with them. If you have 5,000 modules and each is 100 lines of code in length, it"s much easier.

The series basically discuss how to obtain these highly modular applications. Then the later books in the series will talk about Test and Deployment.