It's out! As of today you can order the PRINT 2nd edition of Observability Engineering from any major bookseller; no more waiting for preorders. Co-written w/ @charity.wtf, @gmiranda23.bsky.social, @aparker.io & guest authors Buy: www.indiebound.org/book/9781098... or www.amazon.com/Observabilit...
I'm not into tokenmaxxing for the sake of tokenmaxxing, but damn that was a productive week.
hey btw if you don't know about the dutch reach, now you do. www.skoda-storyboard.com/en/lifestyle...
a set of slides from a deck I presented in 2022 at DDD Brisbane. and the problem is still getting WORSE. (the smoke pictures are satellite imagery from the 2019 bushfires)
yeah I don't think a ceasefire or deal are happening. x.com/Ebrahimazizi33
hey any Vancouver transit nerds know what these four lit buttons on a Compass reader are for? Spotted on a 99-B line bus. @translink.ca
Come find me at the Dev Community Zone! I am (assisted by @koogh.com) doing a set of demos around integrating AWS DevOps Agent and observability tooling to debug faster! #awssummitsydney
and also have a look at this graph showing % of codebase that we can prove was last modified or created with AI assistance: if you're curious how we managed to not ensloppify everything or collapse under our own weight of reviews and code maintenance, come to my talks!
oh ps have a fun graph: PRs landed on main per day, and time it took CI to validate them. Can you spot the point we switched to a system that only runs tests if the test dependencies changed? Also, notice the slope of the PRs/day curve changes *well* before that.
neither of these are reliable sources. just open the WSJ website directly yourself, and link directly to it. even if there's a paywall, you'll at least get the headline.
the ad is not listed under adstransparency.google.com/advertiser/A... or adstransparency.google.com/advertiser/A... so Google has taken action. The stripe api key still appears to be live, unfortunately :(
One of the most satisfying graphs I've seen in my career, thanks to continuous profiling, Claude, and my amazing teammates.
yup, it looks like any correspondence with customersupportcmmail@amtrak.com and the associated records would have been leaked.
would not have been able to land 4 intricate critical-path latency PRs in 24 hours, or 18 broader performance improvement PRs in a single week without the help of both really good telemetry, and solid AI code-reading / code-writing assistance, and solid AI code review to help the human reviewers.
well, I guess I have my answer as to how much Claude I've been using