Migrating to GraphQL: A practical assessment
Facebook’s GraphQL looks very promising, but is it ready for primetime?
Facebook’s GraphQL looks very promising, but is it ready for primetime?
Poorly documented code can tell you what it does, but not what why. Issue trackers can help you rediscover that “why”.
Continuous integration should make everything faster, but it can actually slow things down too.
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.
Debunking some myths about the effectiveness of test-driven development.
What makes people abandon their continuous integration service?
Everyone keeps talking about how technical debt is bad, but how bad is it really?
Ways to ensure that all code is equal and no code is more equal than others.
Duplicate code. Duplicate code everywhere.
I mean, surely this tiny addition is not going to have any noticeable effect on the system’s architecture?
I actually don’t know anyone who blindly copies stuff from Stack Overflow, but apparently it’s a thing.
Here’s a list of six things you should not do in an MVC architecture.
Achieving better ETA prediction using machine learning.
Does it matter if your method names contain tiny linguistic mistakes? Possibly.
Forget LOC and cyclomatic complexity; can we just calculate the understandability of code directly?
ORM frameworks make your life a lot easier, but can just as easily lead to performance problems.
I’ll tell you what, I don’t even remember writing this article.
You want comments in your code, but probably not too many.
Some tips that can help you streamline your code review pipeline.
You know about code coverage for tests, but code review coverage is just as important.
Go’s time
package takes a novel approach to defining datetime serialisation formats. Is it an improvement over existing alternatives?