Old questions

During the past couple years, questions have been queueing up on my comment inbox and not getting answered for different reasons. I believe the authors already found found the answers they were looking for or just don’t care about them anymore after a few months.

Having a lot of comments in my inbox is not really productive, so I’m archiving all questions older than 1 month. Later I plan to go through them again and use a few interesting questions as topics for new blog posts.

To avoid situations like that in the future, I’m establishing a new personal SLA. All questions and comments submitted to the blog should be answered within 3 days. So if you don’t hear back from me in 3 days, shout out!

If you submitted a question a while ago and did not get an answer, I apologize. If you’re still looking for some input, please submit it again. If you found your answer somewhere else and would like to share it, let me know. I’m always open to guest posts!

If broken it is, fix it you should

A while ago I was looking for an easy way to explain developers how to find and fix memory leaks. During my research I’ve found this really interesting blog by a Microsoft Engineer, Tess Ferrandez.

She is constantly posting new tips and guides on .NET development and troubleshooting. I really like the “.NET Debugging Labs”, step by step guides on how to fix common issues, such as Memory Leaks, CPU Hangs, Crashes and so on.

If broken it is, fix it you should: