Static Code Analysis: SonarQube, Facebook’s Infer, and TypeScript

Posted Leave a commentPosted in quality assurance

Infer is a static code analysis tool promising finding many bugs that escape the attention of many other tools. My curiosity was piqued. The result was underwhelming: Infer found four possible NullPointerExceptions in the source code of BootsFaces. Later I ran SonarQube. It found many other potential NullPointerExceptions. Any in both cases, half of the […]

Getting Started With Continuous Delivery

Posted 2 CommentsPosted in Continuous Delivery, development processes, quality assurance

Basically, Continuous Delivery is simply a clever idea to make software development more simple, more reliable and more efficient. Sounds like simply tweaking the development process here and there, doesn’t it? But when you’re an experienced developer starting with Continuous Delivery, you’ll be surprised to meet a whole bunch of new tools you’ve never heard […]

Does Your Programming Language Influence Software Quality?

Posted Leave a commentPosted in Concepts of programming languages, quality assurance

This morning Heise published an article I found exciting at first glance. They claim Python has a superior software quality. At second sight thing look a little different. According to the comments, the article contains a number of mistakes. Maybe even worse, it’s utterly misleading. The study they cite says Python is high-quality software. They […]

Ceylon’s Approach To Eliminate NullPointerExceptions

Posted 2 CommentsPosted in Concepts of programming languages, quality assurance

Maybe you’ve already heard of Ceylon. Ceylon’s a language initiated by Gavin King, the creator of both Hibernate and Seam. Putting it in a nutshell, Ceylon is an attempt to create a better version of Java. The Ceylon developer team has released an early preview version (milestone 5). Andrew C. Oliver considered it to be […]

There is no accurate documentation of your code but your code itself

Posted Leave a commentPosted in quality assurance, refactoring

It’s a common misconception that every program needs documentation. Most people seem to be terribly scared by programs lacking documentation. Whenever I am asked where my documentation is, inevitably this question is followed by the next question: “What happens if you leave the company? Nobody┬┤ll be able to figure out your code!” That’s nonsense.