I suspect this is meant as "interesting to others". I find my job interesting in software development. Many others doing the same job may not. Somehow I have al

I suspect this is meant as "interesting to others". I find my job interesting in software development. Many others doing the same job may not. Somehow I have always found interest in it: from self-learning on 8-bit home computers, and co-op internships, all the way for decades in my career. Currently, I'm 'de-obfuscating' a codebase that was unintentionally obfuscated by having a list of 'steps' that are composed into 'pipelines' and share a communication datastructure. People in general are really bad at making DSLs (see Greenspun's tenth rule[0]). If you've ever used a framework that encodes coarse instructions in JSON, you get the gist of where this was headed. The direct way would be to have humans write out the equivallent in plain statically-typed code without shared mutable state. Using an LLM may be of help but still needs human checking. So I instead made a code generator that uses the DSL structures at runtime and self-inspection to write the equivalent plain code. It's not perfect, so always generates from the DSL structures and compares that to the hand-made implementation by showing a diff of the overridden sections. This way it stay's in sync until we flip the switch to use the new code. TL;DR - There are no small parts, only small actors. [0] https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule