The cycle I find with code generation is that I move quickly - past comfort at or beyond the rim of my comprehension. That reaches a breaking point. Then comes reflection, I slow up, dive into the implementation, wrest control of it. Then I speed up again. Sustainable not steady.

I love this idea. As with any resource intensive operation, part of sustainability is finding a way to consume resources off peak so that the provider doesn’t have to resort to the least efficient sources is supply. Given cloud services are often locally optimized, processing off business hours may make a difference.

One challenge I struggle with is how to build cloud based solutions without generating unnecessary computes in the process. The work requires significant development by configuration. The API’s are abstract. The newer services like the AI suites are sparsely documented and the concrete examples obsolete quickly. So, working with them entails executing against the real resources at almost every step. We build with smaller models (if available), smaller sample sets, etc. but we’re still building without the ability to unit test.