If our notion of “what is supposed to happen” is getting weaker, then developer experience becomes about helping developers and IT teams understand what their software systems are doing in the first place. We can’t see what is supposed to happen, so we need to see what IS happening. This means we need to shift from a mindset and approach of monitoring to a mindset and approach of observing — which in turn suggests that the future of developer experience hinges on better experience of observability.
future.a16z.com | The Case for 'Developer Experience' - Future
Filed under:
Same Source
Related Notes
- Now the real advantage of tracing to me is it comes out of the box ...from Mathew Duggan
- My experience is companies do not anticipate that the cost of monit...from Mathew Duggan
- The **OODA loop** is the cycle *observe–orient–decide–act*, develop...from en.wikipedia.org
- Dealing with Error: • Put the knowledge required to operate the te...from Don Norman
- insights from the seven stages of action lead us to seven fundament...from Don Norman
- These are qualities of a good system that we should strive to fulfi...from Josh Beckman
- As far as I can tell, cognitive bandwidth and network bandwidth bot...from Ferd.ca
- these are the three main lists of golden signals today: From the Go...from www.infoq.com