background preloader

El Libro para Principiantes en Node.js» Un tutorial completo de node.js

El Libro para Principiantes en Node.js» Un tutorial completo de node.js
Sobre el Tutorial El objetivo de este documento es ayudarte a empezar con el desarrollo de aplicaciones para Node.js, enseñándote todo lo que necesites saber acerca de JavaScript "avanzado" sobre la marcha. Este tutorial va mucho más allá del típico manual "Hola Mundo". Status Estás leyendo la versión final de este libro, es decir, las actualizaciones solo serán hechas para corregir errores o para reflejar cambiar en nuevas versiones de Node.js. Las muestras de código de este libro están probadas para funcionar con la versión 0.6.11 de Node.js. Audiencia Objetivo Este documento probablemente será mejor entendido por los lectores que tengan un trasfondo similar al mío: Programadores experimentados en al menos un lenguaje orientado al objeto, como Ruby, Python, PHP o Java; poca experiencia con JavaScript, y ninguna experiencia en Node.js. Estructura de este documento Empezaremos por mirar cómo el desarrollo en JavaScript en Node.js es diferente del desarrollo en JavaScript en un browser. Ok.

Developer Network Scaling Your JavaScript Applications (Videos) Summary Developers creating JavaScript applications these days usually use a combination of patterns like MVC/MV*, modules, widgets and plugins for their architecture.Whilst this works great for apps that are built at a smaller-scale, what happens when your project starts to grow? In this talk, I present an effective set of design patterns for small, medium and large-scale JavaScript applications. Slides The slides for this presentation can be found over on SpeakerDeck. Video 1/3: Architecture For Small-Medium Size Apps (23 mins) Video 2/3: Writing Modular Code (16 mins) Video 3/3: Patterns For Large-Scale Development (33 mins) It's important to stress that there are many ways of building large-scale applications.

Test-Driven JavaScript Development in Practice TDD is an iterative development process where each iteration starts by writing a test which forms a part of the specification we are implementing. The short iterations allow for more instant feedback on the code we are writing, and bad design decisions are easier to catch. By writing the tests prior to any production code, good unit test coverage comes with the territory, but that is merely a welcome side-effect. Republished Tutorial Every few weeks, we revisit some of our reader's favorite posts from throughout the history of the site. Turning Development Upside-Down In traditional programming, problems are solved by programming until a concept is fully represented in code. Test-driven development turns the development cycle upside-down. The Process The test-driven development process is an iterative process where each iteration consists of the following four steps: Write a test Run tests, watch the new test fail Make the test pass Refactor to remove duplication The Observable Library

Related: