// TOPIC INDEX Category: #engineering

Engineering

5 Field Notes

Lessons from shipping software: DevOps, CI, launches, and the habits that separate working code from done code.

Subscribe Topic RSS
Tags:
Showing 5 of 5 posts in Engineering
02 // Engineering

Stop Pending Steps From Failing Your CI Build

Pending Cucumber steps are a handy to-do list in TDD, but by default they make Cucumber exit with code 1, so CircleCI marks the build as failed even when no tests fail. The --no-strict-pending flag keeps pending steps from failing the build while still catching undefined and flaky ones.

4 min read
03 // Engineering

Ansible, Github, and a Failed to validate the SSL certificate story

After GitHub dropped support for weak cryptography, ansible-galaxy suddenly failed with an SSL certificate error on macOS. The cause turned out to be Ansible running on the outdated system Python 2.7; reinstalling Ansible on Python 3 with pip fixed it.

5 min read
04 // Engineering

Attention to Detail

Across mentees with ten years of experience and those with less than one, the trait that best predicts a developer's progress isn't background or seniority but attention to detail. It shows up in whitespace and alignment first, and later in whether work is truly "done done" or only works on the happy path.

10 min read
05 // Engineering

The Lesson from Ignoring All Lessons

A weekend hackathon followed by an under-prepared product launch meant breaking every rule: an S3 migration script killed halfway by a Heroku timeout, a CI suite failing for no clear reason, and a launch three and a half hours late. Plans go awry; staying calm matters more than perfection.

8 min read
ESC

Type to search 38 posts