My familys recipe for monkey bread, which varies from the traditional by being a biscuit not a dessert.
This arose as a bit of a joke that bounced around among several friends and I. I thus present to you, IPv4, if it were Enterprise Ready.
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.
Many moons ago, I tried to use the GeoIP database, via MySQL – and discovered that MySQL was doing the wrong thing with the queries. Naturally, I found some tricks to make it faster.
Recently, I've been introduced to the AAIA's 'ACES' datasets. These datasets aim to describe the make, model, and configuration of pretty much every vehicle in recent history.
These datasets are a terrifying case study in how not to design datasets.
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.”
Maybe percentage-spent-on-overhead is the wrong metric to look at when it comes to charities…
“Cryptography is perilous because you get no feedback when you mess up.”
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.