Two professional case studies about the work between an idea and a reliable product: choosing the boundaries, coordinating long-running compute, and designing for the next change rather than only the current implementation.
How stable contracts, durable parent/child jobs, provider adapters, and explicit failure policy keep a growing solver portfolio coherent. Includes a clean-room executable companion repository.
Read the architecture case studyHow I identified a research opportunity and independently built the SDK, service, asynchronous multi-job workflow, solver integration, reconstruction stage, and benchmarks needed to turn the method into a product.
Read the product case study