Understanding how people are using your app is crucial to your mission as a developer. If you don’t know how your users are interacting with your code, how can you work out how to improve it? As the first instalment of my new blog series on behaviour data collection and analysis, this post covers some of the foundations. So, if you’re new to behaviour data and want to learn more, read on…Continue reading
Recently I’ve been on a quest to find more technical blogs written by women. In today’s post, I share 10 of my favourites, on topics ranging from Kubernetes to web accessibility. It’s a list personal to my tastes, but the aim is to ensure that we don’t lose sight of the fact that you don’t need to be a man to be at the top of your tech game.Continue reading
In my recent posts, I’ve been exploring how Roslyn-based code analysers can help to make your code cleaner and more robust. I’ve tried to keep it relatively IDE agnostic so far. In today’s post, I’d like to talk about some of the pain-points involved with using code analysers in VS Code, as well as some of the progress being made by the community.Continue reading
In my last post, I talked about why I love code analysers. Towards the end, I mentioned how easy it is to get started, but I glossed over the fact that flipping the switch on an existing application can be a pretty harrowing experience. In today’s post, I hope to make the jump a little easier by walking you through a 4 step strategy that I’ve found helpful on a couple of projects.
Static analysis can be a great way to ensure that your code is robust and clean. Unfortunately, many static analysis tools are prohibitively expensive and/or fiendishly complicated. In today’s post, I’d like to talk a little about Roslyn-based code analysers, which cost nothing and are easy to set up. In fact, keep reading for seven reasons that they’re ace.