I haven't sent a newsletter for quite some time now. I didn't know what I wanted to share and ended up not drafting anything for a long time. Today I am sending the first refreshed version. There is no defined cadence in sending this newsletter. Instead, I will e-mail something when I have some thoughts I want to share - I hope you like it.
Let's talk about code analysis.
"Is code analysis really needed?". This question is something I have heard a lot over the years. From customers when I was a consultant, from managers in projects, from developers across teams, and so on.
As software evolves, so does the need for automation. We continuously see an increase in code changes across projects. There is no way to keep up with them all - unless we spend a moment to fine-tune our processes.
With the right set of tools at hand for both the developers and operations team, we can ensure to follow corporate policies and code guidelines. Meanwhile, we also can sleep better, knowing we have run the code through a few security checks automatically.
Recently, I published a popular post "Code analysis tools for Azure developers coding in .NET Core," further detailing my thoughts and some tips for recommended tools.
What about you?
I would love to keep this dialog open. Feel free to reply to this e-mail to help me gain insights from other parts of the field.
- Do you have code analysis tools enabled for your development teams?
- Do you have a list of preferred tools to enable better code?
- How does your current process work?
- What is your role in your the organization?
- If you do not implement any processes around code quality, what are the reasons?
I'd love to hear more, to broaden my views. You can hit 'reply' on this e-mail to get in touch.
Also, I would love to get some feedback on the format of this newsletter!