Category: Programming

Don’t Fear Metrics When Measuring Developer Quality

I want to laugh when people say common metrics shouldn’t be used for establishing developer productivity. It seems like a prototypical pseudo-intellectual move to point out that such metrics can be misleading when used improperly, but the speaker of such

Tagged with: , ,

Base Component Naming

Say I have a project called React Report Maker and it has a report component. Components should be super generic right? So I should probably just call the containing file report.js right? Wrong. Generic components are great but if they

Tagged with: , , ,

Code Freeze Patterns

In development you can institute a couple different kinds of code freeze. This article describes them and gives pros and cons. Hard Freeze A hard freeze is handled at the source control management or deployment level. Turning off deployments is

Tagged with: , , , , ,

Process Artifacts Coming Soon

I was quipping this morning and I might have uncovered something useful. Culture consultant Jamie Notter put out this article and I mentioned to a coworker: This article is decidedly better than his last, but again, his solution is ‘pay my consultancy’ instead

Tagged with: ,

Project Oxygen and Cost Mitigation Value

In this article I argue that corporate management chiefly achieves value through cost mitigation, not genuine productivity enhancement. I do this in part by drawing on Google’s Project Oxygen, as well as my own experience. I previously discussed Google’s Project

Tagged with: , ,

Business-Efficient Programming

Efficient programming without qualification generally refers to programming which is technically efficient. Technically efficient code optimizes performance while minimizing resource usage. That’s not what this article is about. Efficient programming has a number of secondary meanings, and I’m talking about

Agile Estimation: To Repoint or Not to Repoint?

There is a minority practice in Agile Scrum sometimes called Repointing. This article describes the practice, compares it to the usual practice, and concludes by recommending that teams do not engage in Repointing. The usual Agile estimation procedure for an

Tagged with: , , , ,


DRY is a good first-pass rule of thumb, but RYE is optimal. “Repeat yourself efficiently” Examples: Add a data-attr to an HTML element so that some data can be read from it using $ rather than a longer jQuery selector

Tagged with:

Brackets > Atom

As a developer, working mainly in JS, unwilling to fork out cash, my preferred IDE is Brackets. Most people would say Atom is better. I object for the following reasons: Can’t exclude node_modules in many use cases. I shouldn’t have

Tagged with: , , , ,