-
Setting myself up to fail
Treating the timeline as the most important part of a project has burned me more than once — some thoughts on keeping quality under deadline pressure.
-
Thinking before programming
A link to Alistair Cockburn's piece on thinking through the algorithm before you start coding, rather than waiting for it to emerge.
-
It can be cold on the outside..
Two unrelated events made me realise I show my personal projects no real love — no design, no milestones, no plan — and how I intend to fix that.
-
You want how much
Contractor rates, the risk clients take on, and why staying contracting long-term means constantly investing in your own skills.
-
A test too far?
How I approached a 'simple' GitHub technical test as a senior developer — and the untested Sinatra page that came back to bite me.
-
Perception is everything
How I accidentally burned a recruiter by taking a job months after he'd first mentioned it — a story about perception and other people's point of view.
-
Clever.. Clever.. Clever..
Clever code is rarely better code — a JavaScript reduce trick compared with the boring loop that turned out simpler anyway.
-
Blast from the past
An unsent blog draft from 2011 about the struggles of pairing with juniors, and what I've learned about it in the years since.
-
These are not the solutions you are looking for..
Filtering, grouping and sorting in Angular, and how stepping back from a complicated array-diffing fix led to a much simpler answer.
-
You want to “what” now??
A friend wanted to hack the output of a gem I helped write; subclassing the JSON builder was far easier than fighting the library.