Everybody loves "green field" projects. Not only are they the chances to try some new shiny framework, but they are also the opportunity to not stumble upon on of those "legacy" projects, with code base crippled with bugs and huge technical debts.
But what if we could keep those "brown field" projects clean? and do we prevent our new projects to fall into the same traps as before? Well, one of the way to achieve this is via static code analysis tools, such as SonarQube!
Interested? Join us and learn more about how those tools work.
As always, don't hesitate to spread the words amongst your colleagues by hanging our poster (https://app.box.com/s/7p0h495zx1uz5s5ad403yea891xxdlhe) somewhere in your office.
Find bugs in your java code without executing it ? we can do it. Come discover how static analysis is a way to do this by discovering the internals of the Java Analyzer of SonarQube. What are the difficulties to understand the Java Language ? What is syntaxic analysis, semantic analysis and symbolic execution ? And how, just relying on source code it is possible to find issues in your code without executing it ? Answering all this questions will allow you to be able to write your own static analysis rules
About the Speakers
Java Developer, dad and cyclist when I get the time, I have been developing with java for more than 10 years. After working in a few services company and in a private bank, I am now working at SonarSource for 4 years in the language team on the java plugin for SonarQube.
https://github.com/m-g-sonar/ | https://github.com/Wohops
Java Developer in the Language Team @ SonarSouce. Graduate from the university of geneva (MSc. in Computer Sciences), joined SonarSource after a bit more that 3 years as consultant in a Geneva-based IT Service company. Loves mountains, running (a lot), hiking and telemark skiing