-
In this article authors document their experience of commercializing a static-analysis based bug finding tool. In particular, authors outline typical pitfalls that future tool-smiths will find useful to transition an awesome research prototype into a functional and viable commercial product.
-
Our work on inferring likely method mappings across APIs was accepted in SCAM 2015.
-
In this paper, authors provide an overview of the program analysis platform “Tricorder” that is being currently used in Google for program analysis. They also present a set of guiding principles that went into creating the platform.
-
This blog was put together using Jekyll and Github Pages. Listed next are the steps I followed:
subscribe via RSS
Posts
- Team Values
- J.A.R.V.I.S. for Developers
- Screens, Windows, Distractions, Focus, and Work
- 'Mini-Servers' for 'Micro-Services'
- A few Billion Lines of code Later: Using Static Analysis to Find Bugs in the Real World
- API Mapping using Text Mining
- Tricorder: Building a Program Analysis Ecosystem
- Creating this blog
- When, How, and Why Developers (Do Not) Test in Their IDEs
- Test Post!
- Hello World!