Ben Hale talks about the new support for JMX access, debugging, and profiling.
Nathan Taylor provides an introduction to the dynamic analysis research space, suggesting integrating these techniques into various internal tools.
Nitsan Wakart discusses concrete cases in which profilers misguide, misrepresent and at times subvert the systems they aim to help us diagnose.
This talk covers the classic profiler features. What is a hotspot? What is the difference between sampling and instrumentation from the profiler perspective? What are the problems with those methods?
Jerry Yoakum discusses how code profiling tools and techniques can be used to evaluate code for constructions and errors that are likely to cause problems, highlight places in need of refactoring.
Peter Lawrey discusses data-driven reactive systems, profiling latency distribution in such an environment, finding rare bugs, implementing resilience and monitoring.
The authors introduce Alembic, a new static analysis tool that frees programmers from having to manually move computation to exploit locality in PGAS programs.
Adam Tornhill teaches how to predict bugs, detect architectural decay and find the code that is most expensive to maintain, how to evaluate knowledge drain in a codebase, and much more.
Bjorn Freeman-Benson suggests “listening” to the code, refactoring it based on various factors such as the defect rate or underperforming services, providing strategies and tools.
Patrick Smacchia shares code analysis-related practices - structuring code, measuring code quality, automated tests, code contracts, reporting progress, trending- based on his experience with NDepend.
Panos Astithas presents some of the debugging, profiling and tracing tools available to web developers today.
Daniel Spiewak and Aaron Bedra take a look at code verifying starting with Tony Hoare’s paper on testing(1969), type theory, and language-integrated proof systems.