How To Deal With Untestable Requirements – Rewrite Them

Posted on:

The premise behind the rule that requirements must be testable is driven by the goal of avoiding ambiguous language in your requirements. Statements like “the application must have a clean user interface” or “search response times must be fast” are also untestable, but more because of language than anything else.

Collision Detection

Posted on:

I was doing a code-read for a team member earlier this year, and stumbled upon an elegant algorithm. This is super-simple, I realize, but I believe it’s a great example of avoiding complexity. Einstein said it best – “as simple as possible, but no simpler”. Problem : Given two solid […]

Welcome to Tyner Blain

Posted on:

Howdy! I’ve set up this blog to keep track about thoughts I have in the software development space. I’m Scott Sehlhorst, president of Tyner Blain LLC. I wear a bunch of hats, playing different roles throughout the software development process. Tyner Blain was founded with two goals – helping customers […]