Software testing has been an important, if not prevalent way of checking software correctness. In this article I will tell how have my doctoral dissertation on testing and verification of imperative software as well as my work experience after the studies led me to typed functional programming, which consequently gave me a different perspective on automatic software testing. Furthermore, I’ll explain why functional programming and static type systems are important for software correctness.
Philip Wadler makes a fun note about today’s programming languages: “Most of you use programming languages that are invented, and you can tell, can’t you?” I recommend watching his whole talk Propositions as Types!
In the meantime at the European Congress of Radiology 2018…
It was 2007 when David Parnas wrote this viewpoint, but almost 10 years later, things haven’t changed in (computer) science – Stop the Numbers Game.
This is what it looks like when your academic paper gets rejected for publication: PhD Comics.
After writing a library for Firehose data structures in KLEE last week, I thought I should write some unit tests before moving on to integrating the rest of the KLEE code base with the Firehose format. I faced some problems there and that’s when I switched to running KLEE on several hundreds of programs present in Debian GNU/Linux.
The PhD Comics has a nice chart helping you figure out if you should attend a conference.
A Comparative Analysis of Pandas vs. Academics by PhD Comics is hilarious!