Oh shit, replied to you at exact time you replied to me here:<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10954970" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10954970</a><p>&quot;GRR isn&#x27;t hard just time consuming. Yes its not fully verified&quot;<p>I believe it now after pulling papers. I even know exactly how hard it is and what parts are decidable.<p>&quot; Working in aging tester frameworks pays a lot more then web development.&quot;<p>Makes sense. It&#x27;s why I advise against commodity jobs. The niche or unpopular stuff <i>usually</i> pays better. Not always, but usually.<p>&quot;The core purpose is exception logging. A lot of the exceptions will get mutated&#x2F;modified before being reported. &quot;Servo drive failed.&quot; is a lot less useful then &quot;Servo communication fault 0x274077343&quot; which I&#x27;ve memorized to tell me that a power surged knocked a comport off line.&quot;<p>Hmm. That&#x27;s more straight-forward than most async. Just detail-oriented work as you said. The taint idea of tracking exact sequence of mutations combined with design-by-contract tracks of function call contexts would certainly help that. How much I can&#x27;t say as your combination of tech obscures it. Don&#x27;t know enough Labview mainly. Microsoft has things like Spec# and verifiers for C# part with VB6 easy to ignore if you keep logic out of it.<p>So, you&#x27;re in better shape than many doing multi-language, legacy work. At least as far as verification concerns.