I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
Linting and static type checking definitely remove a chunk of these issues
I'm trying to remember for C#, there was a tool that would check for potential memory leaks that wasn't the memory profiler. The name is escaping me at the moment.
As well for C# async/await, setting ConfigureAwait(false). Where I used to work we create a rule using the Roslyn compiler to check for this.
Anyways, looking forward to your next post!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice post Jonathan!
Linting and static type checking definitely remove a chunk of these issues
I'm trying to remember for C#, there was a tool that would check for potential memory leaks that wasn't the memory profiler. The name is escaping me at the moment.
As well for C# async/await, setting
ConfigureAwait(false). Where I used to work we create a rule using the Roslyn compiler to check for this.Anyways, looking forward to your next post!