kernicPanel
Follow
22.2K views | +4 today
kernicPanel
JavaScript, Node Js, Git, Vim, and more…
Curated by Nicolas Clerc
Your new post is loading...
Your new post is loading...
Scooped by Nicolas Clerc
Scoop.it!

Running an Express server with Grunt and Yeoman: Part 3 | ar[V]elocity

Back in part 1 of this series I introduced a small number of tools that make a web engineer’s life easier: Grunt, Yeoman, Express, and Nodemon. In part 2 I provided a repository of filesand explained how to use them to have a running server that’s capable of automatic browser and app server reboots for rapid development.

 

Now, in part 3, I’ll explain how we can use this workflow to automatically run unit tests when development files or test files change, backend or frontend, and how to expose internal functions and properties in our Node or RequireJS modules to the testing environment so that we get less bugs. Onward!

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

Basics of the Unix Philosophy

The ‘Unix philosophy’ originated with Ken Thompson's early meditations on how to design a small but capable operating system with a clean service interface. It grew as the Unix culture learned things about how to get maximum leverage out of Thompson's design. It absorbed lessons from many sources along the way.

 

The Unix philosophy is not a formal design method. It wasn't handed down from the high fastnesses of theoretical computer science as a way to produce theoretically perfect software. Nor is it that perennial executive's mirage, some way to magically extract innovative but reliable software on too short a deadline from unmotivated, badly managed, and underpaid programmers.

 

The Unix philosophy (like successful folk traditions in other engineering disciplines) is bottom-up, not top-down. It is pragmatic and grounded in experience. It is not to be found in official methods and standards, but rather in the implicit half-reflexive knowledge, the expertise that the Unix culture transmits. It encourages a sense of proportion and skepticism — and shows both by having a sense of (often subversive) humor.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

Single page apps in depth (new free book)

This free book is the book I would have wanted when I started working with single page apps. It's not an API reference on a particular framework, rather, the focus is on discussing patterns, implementation choices and decent practices.

I'm taking a "code and concepts" approach to the topic - the best way to learn how to use something is to understand how it is implemented. My ambition here is to decompose the problem of writing a web app, take a fresh look at it and hopefully make better decisions the next time you make one.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

Tutorial: a full Backbone.Marionette application (part 1) | Bridging the geek-suit divide

In previous posts, I introduced you to Backbone.Marionette which provides many niceties to help you build complex Backbone.js apps. We’ll cover more advanced topics here, such as Backbone.History, modal windows, organizing code into sub applications, and more. The resulting app can bee seen live here. Let’s get started!
more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

Writing Testable JavaScript

Writing Testable JavaScript | kernicPanel | Scoop.it
As our JavaScript takes on more and more responsibilities, we need a reliable codebase—one that is thoroughly tested.
more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

stream-handbook

How to write node programs with streams

This document covers the basics of how to write node.js programs with streams.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

MVC is dead, it's time to MOVE on.

MVC is dead, it's time to MOVE on. | kernicPanel | Scoop.it

MVC is a phenomenal idea. You have models, which are nice self-contained bits of state, views which are nice self-contained bits of UI, and controllers which are nice self-contained bits of …

What?

I'm certainly not the first person to notice this, but the problem with MVC as given is that you end up stuffing too much code into your controllers, because you don't know where else to put it.

To fix this I've been using a new pattern: MOVE. Models, Operations, Views, and Events.

more...
No comment yet.
Scooped by Nicolas Clerc
Scoop.it!

chaplin

chaplin | kernicPanel | Scoop.it

chaplin - A Sample Application Architecture Using Backbone.js...

more...
No comment yet.