Skip to content

Instantly share code, notes, and snippets.

View moschel's full-sized avatar

Brian Moschel moschel

38 followers · 0 following
View GitHub Profile
@moschel
moschel / Weekly Widget 7 - Computes and Sliders.md
Last active December 16, 2015 21:38 — forked from justinbmeyer/Weekly Widget 7 - Computes and Sliders.md
Error in user YAML: (<unknown>): could not find expected ':' while scanning a simple key at line 5 column 1
--- 
title: Weekly Widget 7 - Computes and Sliders
tags: open-source canjs
author: justinbmeyer
lead: Learn why can.compute is the last API you will ever need as we explore using it
in a slider.
layout: post
---

Computes are amazing, especially when

@moschel
moschel / Data Driven Controls.md
Last active December 31, 2015 12:08
Data Driven Controls

Live bound templates in CanJS completely change how we build UI controls. When used correctly, live binding gives you far greater separation of concerns and code that is easier to understand and refactor.

In this article, we'll illustrate the clear advantages to using data driven, live bound UI controls, and show how to implement this in your own apps.

Advantages

Live bound templates provide a greater ability to keep UI Control code as semantic as possible, removing most or all of the manual DOM manipulation code that was necessary without live binding.

With live binding, the UI Control strictly maintains the “state” of the control, leaving the visual representation of that state to the View.

@moschel
moschel / 2.0.markdown
Last active January 1, 2016 17:49 — forked from justinbmeyer/2.0.markdown
title tags author lead layout
CanJS 2.0 Release Notes
open-source canjs
justinbmeyer
Today we're happy to announce the latest major release of CanJS.
post

CanJS 2.0 is out! It packs new features that advance CanJS' mission to make JavaScript application development even easier. This article will introduce the changes. It brings:

@moschel
moschel / seniordev.md
Created August 28, 2015 07:20
20% Senior Dev at Bitovi

What the Senior Dev does

  1. Architecture decisions - They will be another set of eyes to help make decisions about setting up the appropriate architecture.
  2. Oversight - They see the project from the eyes of an outsider, making easier to spot holes. They look for problems and make sure best practices are being followed.
  3. Adds value with quick projects - Things like setting up CI, setting up deployment scripts. Quick win projects that improve project efficiency that are hard for other developers to make time for.

Benefits for the project

  1. Quality - Having a developer who can oversee the project, even at 20% time, means the quality of the code goes up dramatically.
  2. Backup plan - If the main developer gets sick, goes on PTO, or leaves the company, we have someone else who can get up to speed quickly in an emergency, or at least help smooth the transition.
  3. Developer longevity - We’ve found that developers on projects without this in place have a high chance of quitting the project and Bitovi. Ad