It does sound like it would barely have broken even when considering the opportunity cost of the highly-compensated developers who had to write it, which they ignore in the article. It goes against the "rules of thumb" i learned at Google, which suggest that an engineer would break even if they saved [redacted but huge number] CPUs per year, and should only choose problems that promise to save 10x that or better.