I levelled up my Claude Code workflow by giving it the ability to see its own front-end output — automatic screenshots captured during system/e2e tests, wired into a custom Code command that visually inspects every captured frame.
Two files, a few lines of config, and a meaningfully better feedback loop.
I can't download it, as it appears to be US only. Based on the screenshots, without 'feels like' support throughout the forecast (not just for current conditions) it wouldn't be useful where I live.
This is not exclusive to the East, but any culture with a high cost of expression. Recent interview with a Russian CEO, talking about how they have "growth across the board, only in the negative direction"
Nothing wrong with the attributes the author groups under 'transparent leadership', but the article shows a certain misunderstanding of servant leadership.
At the core of servant leadership is the idea that leaders shouldn't hoard power, but instead share it and empower their reports. That they are accountable to their reports, rather than the other way.
Nothing to do with acting like a parents and becoming a single point of failure.
So... clickbait title for an article that could have been called "Delete flakey tests"...but then and most of us would have just gone "yep" and not clicked.
Hyrum's Law especially applies when you have consumers of your APIs that violate Postel's Law. To minimise those in the past, we've introduced intentional jitter in our API responses that while didn't violate the schema prevented unintentional reliance on behaviour that wasn't intentional[1].