I have noticed that most articles on how to author NuGet packages focus on the practical part; which commands to run and how to setup your own NuGet server. All these articles also fail to point out the most important information in the NuGet guidelines.
Read more here.
Reading this story about the worst daily scrum ever made me think about my own experience. An both actually reminds me of what happened in the linked story.
When you think about the reasons for reducing technical debt; what do your think about?
Just when I started working on my little toolbox I read this series on dependency injection for events which was great inspiration.
When I was working on the WithProgress extensions I learned something about Progress<T> that I didn't expect.
As you may know if you followed my blog before; I like to roll my own fake. For interfaces it is pretty straight forward with explicit implementation of the interface and properties with delegates for implementation.
If you liked my old series of articles covering TAP and especially the different extension methods I showed. Then you will be even happier now.
A couple of weeks ago I had just read Dan North's article about how he saw six things he thought he would never see because they were impossible. I had no idea I would myself see the seventh impossible thing just a few days later.
A few weeks ago the dynamic IP address restriction feature was announced for Azure Web services.
Several years ago I told a story about a project that proved that estimation was a waste of time once the work was split up in small enough chunks. Not necessarily equal size of chunks but manageable size chunks. But sometimes you need to do estimations because somebody wants to know the cost of some project or large feature.