Tim Oxley: The Structure of Node.JS Applications - JSConf.Asia 2015

Подписаться 277 тыс.

Просмотров 17 тыс.

50% 1

The Node.JS & npm ecosystem is oft praised for it's "culture of extreme modularity", which has led to the proliferation of hundreds of thousands packages on npm. How do modular patterns translate into the construction of evolving, real-world applications? It's Modular vs Monolith!
Tim Oxley is an an Australian JavaScript developer living in Singapore working with NodeSource. Tim is a co-host of the NodeUp podcast, author of NodeSchool's functional JavaScript workshop, founder of the CampJS conference, founder of the SingaporeJS meetup and an avid open-source contributor.
JSConf.Asia - Red Dot Design Museum, Singapore - 19 November 2015.
Source: 2015.jsconf.asia
Slides: www.slideshare.net/timoxley/mo...
License: For reuse of this video under a more permissive license please get in touch with us. The speakers retain the copyright for their performances.

Наука

Опубликовано:

4 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 8

@luminaia 8 лет назад

Super useful. cheers.

@maybepumpkins 6 лет назад

Principles to keep in mind: Don't write it if YAGNI: en.wikipedia.org/wiki/You_aren%27t_gonna_need_it Do the simplest thing that could possibly work: www.agilenutshell.com/simplest_thing Top-down programming (start by writing your main/entry function first): en.wikipedia.org/wiki/Top-down_and_bottom-up_design#Programming Wait until you use it three times before extracting it into a reusable function: en.wikipedia.org/wiki/Rule_of_three_(computer_programming) Give contributors commit access early: openopensource.org/ And more: github.com/timoxley/best-practices

@alexpotap3985 6 лет назад

He delivered his PAIN :)

@TumbleGamerTK 6 лет назад

saxophones are made of metal

@rickyj1 8 лет назад

Just noticed, a lot of the programmers have glasses.... crap

@christopherstamp9716 7 лет назад

Hmmm.... This doesn't work in all environments. Api is key when you want to change out libraries and such. I had an example at work. Elegance is key, but So I saves you from working 1000 hours refactoring thousands of lines of code that used to reference your know broken code. Abstraction exists for a reason.

@wunder5776 7 лет назад

I admit, I did not finish watching this video because I couldn't focus on the talk. However, I feel like the issues he was having with libraries are the result of a few things. 1. Over engineering the library by putting too much thought into reuse thus producing imperfect code. 2. Lack of understanding in functional programming. 3. Lack of understanding in data type. I know JavaScript isn't really an type based language, but it can be achieved with prototype and constructor. These are my views on half of the video.

@secoif 7 лет назад

heh, exactly one of the key points of the talk is to encourage people to not put too much thought into reuse. I mainly write functionally and it only helps to a point. Can create hard-to-unravel layers of over-engineered complexity no matter your programming orientation.