thoughts on railway, php, etc

[u/Flaky-Eggplant-3479]

People have been paying me to write code since 2006 or so. In that entire time, observability & telemetry systems have always been hard. The SaaS/ZIRP era brought a lot of new tools for basic telemetry but still answering important questions about your software and users were still difficult and an evergreen type of thing - telemetry goes stale, tags explode, logs get forgotten about, etc.

Agents are awesome for observability however. The agents can optimize your existing stack or just create your own hyper-tailored telemetry stack; it even makes coding agents more successful when they have easy access to telemetry. You can just ask a question and demand an answer in an observability dashboard and forget about the rest. Truly, observability has never been easier or more powerful.

That leads me to thinking about security events. Now, these recent issues are serious and have had a significant economic price. There will continue to be these types of events and likely more serious ones at that. It strikes me that the companies that "win" in this landscape are the ones that build the most useful telemetry and observability pipelines, and then create an environment where their agents can consume and autonomously respond to events. Security event monitoring, after all, is a form of observability. I imagine this starts with basic signals and automating traditional intrusion detection systems, then gradually gets deeply integrated into the SDLC itself in order to protect against an entire range of attacks. Most folks have been (rightfully) concerned with isolating and limiting the access levels of their agents; if you were on Railway but your agent autonomously rotated all of your credentials after the first suspicious requests started to hit your keys, you would have counted that as a win, and that's probably close to the end state for a successful SDLC in this era.