Today I came across a case against Cucumber,
and I have a couple bones to pick. More importantly, I want to elaborate a bit
on the author's comments about enjoying the Gherkin syntax, and expand on an
idea there.

I previously wrote about an idea I had
for managing technical debt in the face of continuous and inevitable business
pressures. I want to take a moment to follow up with some of the comments I've
received on the technique, how it evolved, and where it proved strong/weak.

“As Data Engineer, you’ll design and architect the pipeline for data ingested
from multiple sources. We are looking for creative, results-driven developer
who is excited about big, fast and flexible data.”

Getting At Awkward Code, For Great Testing

A couple days ago, I wound up helping out a colleague on a problem he was
having coming up with an appropriate test case for a piece of code in a Rails
app. It reminded me that I had wanted to talk about how structuring your code
affects what you are actually testing, and how that related to what you
want to test.