Bio James has worked in many technology industries over the past 12 years, including: Backend engineering, Kiosks, video games, enterprise systems development, desktop applications and mobile apps. In the last few years, he has focused on mobile. He also hates writing and updating bios... Achievements Expanded a consulting company and brought profitability to projects through agile and lean methodologies. Links that make me look famous: StartUp Ready: Lean Startup Apps,

Keybase.io Signing Files

The 10%

I used to think, "Give it 110%", was logically impossible. That was, until I realized I was applying the statement individually instead of as a whole. The whole is greater than the sum of its parts. Aristotle Unlike this comic by SMBC, that extra 10% does not come from some external sources. That +10% comes from a team of people cooperating towards the same goal. Next time someone tells you to give it 110%, put your team first.

Write in CoffeeScript and package in Javascript

--- layout: post title: Write in CoffeeScript and package in Javascript tags: coffeescript, javascript, npm --- Like using CoffeeScript and want to publish your NPM modules but write them in CoffeeScript? It is actually really easy to do. { . . . "main": "build/index.js" "scripts": { "prepublish": "coffee --bare --compile --output build lib" }, . . . } `prepublish` is run before a `npm package` command. The one above compiles the contents of `./lib` and puts it in `./build`.

The importance of tests first in TDD

I see a common mistake with lots of people new to TDD and unit testing in general: Tests that appear to pass, but really do not. I have seen a few different ways this can happen: Flat out testing the wrong conditions for passing. Not understanding how the test framework is asserting. Trying to test for too many things in one test, missing the important state for passing. Lazy test, that is written to always pass to get green bar.