Short version

[ONE PARAGRAPH on the shape of the work: the systems Earl owns, the kind of problem he is called into, and what "end to end" means concretely.] D2 fixes the positioning — .NET and Azure depth, cross-platform breadth — but the paragraph is Earl's to write, and writing it from anything else would mean inventing a career. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Most recently the work has been AI-shaped. I build internal tooling and agents that other engineers run, and I have rebuilt my own delivery around AI-assisted development — [TASK] from [BEFORE] to [AFTER]. Those are two separate things and I keep them apart: one is an artifact other people use, the other is my own throughput. I have not rolled the practice out beyond myself, and nobody owns AI governance where I work. Both of those are gaps I can see rather than claims I can make.

[ONE PARAGRAPH on working with other engineers: architecture others adopt, review standards, and the documentation that makes new people productive.] The structured version is in the case studies. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat, duis aute irure dolor in reprehenderit.

I also design and print physical products, and write drivers when vendors won't. That work lives at the3dcoder.com — apps across three stores, 3D models and prints, open source, and the occasional thing that only exists because nobody else was going to build it.

It is on a separate site on purpose. It is evidence of range and of being willing to go and learn an unfamiliar layer of the stack, which is a different argument from the one the case studies make.