Главная
Study mode:
on
1
TIM OXLEY MODULAR VS MONOLITH
2
GOOD MORNING!
3
WHO AM I?
4
NODE.JS: CULTURE OF EXTREME MODULARITY
5
ME IN 2012
6
RABBIT HOLES EVERYWHERE
7
NOTHING FOR FREE
8
MOST OF THE TIME
9
WHAT PROBLEM AM I TRYING TO SOLVE? 'IS THIS THE SIMPLEST THING THAT WILL WORK?
10
AVOID PREMATURE MODULARISATION
11
ASSUME YOUR FIRST ATTEMPT WILL BE BAD 60
12
CODE RETREAT
13
DON'T GET PRECIOUS ABOUT YOUR CODE
14
OVER-ENGINEERING: THE ADDING OF UNNECESSARY COMPLEXITY
15
COMPLEXITY KILLS PROJECTS
16
DEFER DECISIONS
17
DRAW IN PENCIL BEFORE YOU DRAW IN INK
18
ABSTRACTIONS DECREASE LOCAL COMPLEXITY WHILE INCREASING GLOBAL COMPLEXITY
19
BUILDING THE WRONG THING FOR THE RIGHT REASONS
20
BUILD THE SIMPLEST THING THAT WORKS?
21
FLAT IS BETTER THAN NESTED Z
22
At the statement level: avoid nested if/else. At the function level: avoid nested callbacks (i.e. Pyramid of doom) At the class level: avoid nested inheritance hierarchies. At the file level: avoid n…
23
BUILD THE SIMPLEST THING THAT WORKS u
24
AVOID UNNECESSARY COMPLEXITY
25
THANK YOU!
Description:
Explore a conference talk from JSConf.Asia 2015 that delves into the structure of Node.js applications, comparing modular and monolithic approaches. Discover how the Node.js and npm ecosystem's culture of extreme modularity translates into real-world application construction. Learn from Tim Oxley, an Australian JavaScript developer and NodeSource employee, as he shares insights on avoiding premature modularization, deferring decisions, and building the simplest solutions that work. Gain valuable perspectives on managing complexity, avoiding over-engineering, and maintaining a balance between modular and monolithic structures in Node.js development.

The Structure of Node.JS Applications

JSConf
Add to list
#Conference Talks #JSConf #Programming #Programming Languages #Javascript #Node.Js #Software Development #Application Development #Modular Programming
1 of 25

TIM OXLEY MODULAR VS MONOLITH