Alexis Roberson (@codewithalexis) header
Alexis Roberson (@codewithalexis) profile picture

devrel 🥑 @launchdarkly, DevOps/Full Stack Dev | Building systems with built in control levers | 📚 🎤 | Singer | https://teapaw.org/t.co/FHSW19JkbY

Joined October 2015
What happens when your software factory's agents keep copying the same outdated code patterns? A temporary workaround in one feature can become the default approach across several others. Here are three ways to keep your software factory from multiplying technical debt as it generates more code. #SoftwareFactories #TechnicalDebt #AIAgents #LaunchDarkly #DevOps @LaunchDarkly
1
1
16
Release controls help limit the impact of risky changes, but preventing agents from repeatedly introducing outdated patterns starts earlier in the factory. I put together a tutorial showing how to build a small software factory with explicit context rules, policy checks, and review gates: launchdarkly.com/blog/build-… What architectural rules would you enforce before letting agents implement changes in your codebase?
6
A customer keeps experiencing API timeouts, and engineers need better tracing to find out why. The proposed fix adds detailed diagnostic traces, but leaving that level of tracing enabled for every request comes with added overhead and cost. You've got four release options. Which one would you choose? Episode 2 of You Make The Release Call. #YouMakeTheReleaseCall #Observability #FeatureFlags #DevOps #LaunchDarkly
1
9
One useful detail about this scenario: LaunchDarkly supports short-lived, customer-specific feature flag targeting for troubleshooting. That means engineers can enable diagnostic tracing for an affected account during an investigation without exposing every customer to the additional overhead. Here's how to choose the right targeting approach, including short-lived troubleshooting: launchdarkly.com/docs/guides… Would you put a time limit on tracing like this, or disable it manually once the investigation is complete?
9
X Today we’re introducing Release Autopilot. The goal behind it: release integrity, so what reaches your users matches what you intended. My latest post explores why that matters as AI accelerates code creation. Read the blog launchdarkly.com/blog/releas… @LaunchDarkly
18
Two releases. One latency regression. Which change caused it? When rollouts overlap, your overall metrics might show a problem without revealing which change contributed to it. Here's how to approach overlapping releases with independent controls, exposure tracking, and predefined guardrails. #DevOps #SoftwareEngineering #FeatureFlags @LaunchDarkly
1
38
LinkedIn Live tomorrow, Oct 29 @ 6pm CT/4pm PT! "Release Control: How a Feature Flag Became a Control Lever" Feature flags started as a way to hide unfinished code. Now they decide who sees a change, how many people see it, and how fast you can take it back. With software factories pushing more agent-written changes into every deploy, that control matters more than ever. Join here lnkd.in/p/gANYw262
14
An agent writes the code, writes the tests, and CI passes. Plot twist: it misunderstood the requirement, so the tests validate the wrong behavior. A green pipeline is valuable. Production verification is still necessary. #DevOps #CICD #LaunchDarkly
28
A successful deploy doesn't tell you whether the new code has handled a request. I wrote about how feature flag evaluations can help close that gap, especially as agents increase change volume. dev.to/alexiskroberson/deplo…
2
63
A PR that increases an AI enablement app's response limit could fix incomplete plans, but also increase latency and token costs. How would you release it? In Episode 1 of You Make the Release Call, you decide how a real PR should ship. #DevOps #LaunchDarkly
1
39
Two releases, two rollbacks, and very different outcomes. In a software factory that ships changes at agent speed, the number of rollbacks says less about release health than how many users were affected, how fast the team detected the issue and how quickly it recovered.
10
Safety at agent speed depends on where controls sit and what each one is for. dev.to/alexiskroberson/treat…
🤖 Made with AI
22
Hey builders! I had a blast at the Build After Hours in Plano this past Tuesday. The slides from the demo are here: docs.google.com/presentation… "The Guardrails of a Productive Software Factory" presentation + a glimpse at the software factory I'm building to handle incoming requests for my interior design app github.com/arober39/decor-ag… Got questions about anything we covered, or ideas for future content? Drop them in this thread.
45
More agents writing code doesn't mean we need more reviewers at every step. Code review catches implementation issues. Release controls help manage what happens when our assumptions don't hold. Safer releases require both. #DevOps #SoftwareFactory #ReleaseControl
9
I just completed a whole livestream with no sound! Love that for me. I'm going live again tomorrow (with sound) for a quick ask me anything session. Super casual. Feel free to bring a snack or your lunch and join. We can talk tech or I can share a little about my intended presentation. lnkd.in/p/gxNEssfq
1
1
18