SkillsCast
About the Speaker
A SkillsCast for this session is not available.
As programmers we all know about the importance of test suites but tend to leave creating a benchmark – either to measure against other software solutions, or to compare hardware choices – until the last minute. That can lead to a hardware choice made on too few criteria, having to react to a competing shiny solution on their ground, or simply continuing with your own ””new features”” when they should be taken behind the woodshed.
This can determine your work environment and team membership for years. I will discuss ways to avoid being caught out, and the importance of taking the time to prepare in advance.
YOU MAY ALSO LIKE:
Always Keep a Benchmark in your Back Pocket
Simon Garland
Chief StrategistKx’s