Why Observability is Relevant to Developers
Summary
What do developers know about the code changes that were just introduced into the codebase? When will they start noticing if something goes wrong? Should they completely ignore observability sources and let DevOps&SREs worry about how their code runs in prod?
Continuous Feedback is a new dev practice that aims to make practical usage of code runtime data to shorten the feedback loop during development. In this round table discussion, we'll discuss ways in which developers using modern can get and apply early data about their code changes to detect issues and regressions as-they-code. We'll also discuss what type of new coding practices can support this to enable feedback to be an integral part of distributed and complex system development.
Host
Holistic developer and builder with a passion for development processes and practices. Afflicted by an acute Product Manager/Developer split personality disorder that was never treated. Currently, CTO and co-founder of Digma (digma.ai), an IDE plugin for code runtime AI analysis to help accelerate development in complex codebases. A big believer in evidence-based development, and a proponent of Continuous Feedback in all aspects of Software Engineering.
