AI-enabled developer productivity, build systems, and engineering leadership
Posted on in Programming
AI is very good at making CI failures feel less lonely.
That is useful. A large CI log can be hostile terrain: thousands of lines of setup output, dependency chatter, repeated warnings, retry noise, test framework boilerplate, and one real clue hiding near the bottom. Asking an AI tool to …
Posted on in Programming
Build failures become expensive when they stop being reproducible.
The first failure is usually just a problem. The third person saying "it only happens in CI" is when the problem starts turning into folklore. Someone reruns the job. Someone else clears a cache. A third person changes an unrelated file …
Posted on in Programming
CI output is part of your developer experience.
That sounds obvious until you look at the average failed build. A pull request goes red, the developer opens the CI job, and the first thing they see is a scrollback landfill: dependency installation noise, folded shell wrappers, progress bars, warnings from …
Posted on in voice
Trying to debug an <acronym title="Asterisk Gateway Interface">AGI</acronym> in Asterisk can be a frustrating experience. The main problem is that STDERR only outputs to the terminal Asterisk was started from. In most cases, this means the terminal is the server console. If your Asterisk server is sitting …
Posted on in System Administration
If you're like me, it probably seems obvious that command logging is an important part of system administration. Any change I make, whether it's on a router or server, is logged somewhere. Although folks give plenty of reasons why they don't use tools like sudo for super-user functions (inconvenience and …
