Dev Team Shipped Slower Parallel Feature After Benchmark Showed 16% Performance Loss

A developer building logq, a command-line log query tool for a zero-dependency hackathon, added an 8-goroutine parallelization flag despite benchmarks showing it ran 16% slower than a single worker on a 76.3MB test file. The team disclosed the performance gap immediately and shipped the feature regardless, citing its potential value at larger scales. A key design decision was a three-valued evaluator distinguishing between MISSING, null, and false states, preventing query crashes when log records have inconsistent shapes. The project also replaced the widely used third-party library tidwall/gjson with roughly 150 lines of custom code built on Go's standard library, avoiding known issues with float64 precision loss and unpredictable map iteration order. The team removed a CI pipeline two days before submission after it failed for reasons they could not fully diagnose, choosing transparency over leaving an unexplained failure badge.