<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Process-Improvement on jdcsen</title><link>https://jdcsen.com/tags/process-improvement/</link><description>Recent content in Process-Improvement on jdcsen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 01 Jan 1970 00:33:44 +0000</lastBuildDate><atom:link href="https://jdcsen.com/tags/process-improvement/index.xml" rel="self" type="application/rss+xml"/><item><title>One-Command Nova Sonic Dev Environments</title><link>https://jdcsen.com/projects/nova-sonic-dev-provisioning/</link><pubDate>Thu, 01 Jan 1970 00:33:44 +0000</pubDate><guid>https://jdcsen.com/projects/nova-sonic-dev-provisioning/</guid><description>&lt;ul&gt;&#10;&lt;li&gt;Python provisioning system that stands up the complete Nova Sonic inference stack on one developer machine.&lt;/li&gt;&#10;&lt;li&gt;Deploys several Triton model containers plus the C++ node-graph orchestrator, wired together and ready to take speech-to-speech traffic.&lt;/li&gt;&#10;&lt;li&gt;Took a fifteen-person team from sharing a couple of hand-built demo environments to every engineer having their own.&lt;/li&gt;&#10;&lt;li&gt;Same pattern as &lt;a href="https://jdcsen.com/projects/l3dockerize/"&gt;L3Dockerize&lt;/a&gt;: make the right environment the cheap one.&lt;/li&gt;&#10;&lt;/ul&gt;</description></item><item><title>One Build for Cloud and Device: Consolidating a 500k-Line C++ Engine</title><link>https://jdcsen.com/projects/build-system-consolidation/</link><pubDate>Thu, 01 Jan 1970 00:33:42 +0000</pubDate><guid>https://jdcsen.com/projects/build-system-consolidation/</guid><description>&lt;ul&gt;&#10;&lt;li&gt;The legacy ASR engine, roughly 500k lines of C++, was built by its owners with GCC and plain CMake for the cloud. The on-device team consumed it as a library across about 7 ARM toolchains from the Android NDK plus 4 x86 gcc/clang variants, through a Conan-based build layer.&lt;/li&gt;&#10;&lt;li&gt;Before: on-device releases were hand-curated snapshots of the upstream engine, maintained in forks of every ASR package and re-merged periodically. Each release took days at minimum and often weeks, as toolchain-specific breakage surfaced and needed patches.&lt;/li&gt;&#10;&lt;li&gt;Fix: point all engine code at a single virtual build-system package. In the cloud dependency universe it resolves to bare CMake; in the device universe it resolves to the Conan layer, which drives the same CMake underneath. About 40 packages converted; one source tree builds for all 12 toolchains.&lt;/li&gt;&#10;&lt;li&gt;Kept it that way with a pre-merge analyzer that compiles every pull request against the device toolchains before it can land, so device compatibility is checked at merge time rather than discovered at release time.&lt;/li&gt;&#10;&lt;/ul&gt;</description></item><item><title>L3Dockerize: Python-based containerization tool</title><link>https://jdcsen.com/projects/l3dockerize/</link><pubDate>Thu, 01 Jan 1970 00:33:40 +0000</pubDate><guid>https://jdcsen.com/projects/l3dockerize/</guid><description>&lt;ul&gt;&#10;&lt;li&gt;Python-based Docker container builder.&lt;/li&gt;&#10;&lt;li&gt;Dynamically resolves and fetches software component dependencies to build Docker images.&lt;/li&gt;&#10;&lt;li&gt;Intended to serve as a low/zero cost tool for developers to convert existing software installs to more easily monitorable, scalable, and extensible docker-based installations.&lt;/li&gt;&#10;&lt;li&gt;Concept evaluated in a system-wide CIT test of an L3Harris hardware product.&lt;/li&gt;&#10;&lt;/ul&gt;</description></item><item><title>BUPDATE: Batch Updating tool</title><link>https://jdcsen.com/projects/bupdate/</link><pubDate>Thu, 01 Jan 1970 00:33:39 +0000</pubDate><guid>https://jdcsen.com/projects/bupdate/</guid><description>&lt;ul&gt;&#10;&lt;li&gt;Python/Bash Scripting Toolkit for cross-project refactoring.&lt;/li&gt;&#10;&lt;li&gt;Uninvasive, agile solution to deal with problem of poorly-isolated dependencies impacting many components.&lt;/li&gt;&#10;&lt;li&gt;Core application written in Python, per-project scripts writable in any language.&lt;/li&gt;&#10;&lt;li&gt;Designed according to Unix ”simple, clear, modular, extensible” philosophy to facilitate integration into existing toolchains and processes.&lt;/li&gt;&#10;&lt;li&gt;Successfully deployed to automatically upgrade the dependencies of approx. 60 components without user intervention.&lt;/li&gt;&#10;&lt;/ul&gt;</description></item></channel></rss>