Are static analysis violations really fixed?
Static analysis tools are often used to find inconsistencies and possible bugs in code. But what happens next?
“Heap, Heap, Array!”
Allonsay’s language classification algorithm
How you can detect the language of texts, without using the “ML” word.
Finding the most common words in a set of texts for a word cloud
Alternatively: why word counting is nothing like bean counting.
(Not) looping over lists in PHP
This post discusses three common array functions: map, reduce, and filter.
Scalable transfer patterns
Path finding algorithms for public transport take a little bit more work to get right than those for private transport.
Understanding large-scale software – A hierarchical view
Program comprehension often focusses on the understanding of code, but in practice that often won’t be enough.
Practitioners’ views on good software testing practices
A look at some best practices for software testing.
Migrating to GraphQL: A practical assessment
Facebook’s GraphQL looks very promising, but is it ready for primetime?
Uncovering architectural design decisions
Poorly documented code can tell you what it does, but not what why. Issue trackers can help you rediscover that “why”.
Studying the impact of adopting continuous integration on the delivery time of pull requests
Continuous integration should make everything faster, but it can actually slow things down too.
How do design decisions affect the distribution of software metrics?
The authors of this week’s paper built a tool that can infer the design role of classes and let it analyse some Java projects.
Does it really matter to test-first or to test-last?
Debunking some myths about the effectiveness of test-driven development.
I’m leaving you, Travis: A continuous integration breakup story
What makes people abandon their continuous integration service?
The pricey bill of technical debt: When and by whom will it be paid?
Everyone keeps talking about how technical debt is bad, but how bad is it really?
On the usage of Pythonic idioms
Ways to ensure that all code is equal and no code is more equal than others.
Micro-clones in evolving software
Duplicate code. Duplicate code everywhere.
Are developers aware of the architectural impact of their changes?
I mean, surely this tiny addition is not going to have any noticeable effect on the system’s architecture?
Are code examples on an online Q&A forum reliable? A study of API misuse on Stack Overflow
I actually don’t know anyone who blindly copies stuff from Stack Overflow, but apparently it’s a thing.
Code smells for model-view-controller architectures
Here’s a list of six things you should not do in an MVC architecture.
Predicting estimated time of arrival for commercial flights
Achieving better ETA prediction using machine learning.
A large-scale empirical study on linguistic antipatterns affecting APIs
Does it matter if your method names contain tiny linguistic mistakes? Possibly.
Automatically assessing code understandability: How far are we?
Forget LOC and cyclomatic complexity; can we just calculate the understandability of code directly?
How not to structure your database-backed web applications
ORM frameworks make your life a lot easier, but can just as easily lead to performance problems.
Do you remember this source code?
I’ll tell you what, I don’t even remember writing this article.