As expected, the Monday post did not happen due to the server maintenance running a few hours long and clobbering the window for queuing the post. Unfortunately, the maintenance was for upgrading the Community Server version and that failed, so there's the possibility of more down time in the future. I'm failing back to my alternate, alternate plan, which is to just get the posts out one day at a time and not worry about it too much.

The reader survey is unofficially closed. I don't mind having suggestions continue to come in the future. I'm calling these survey outcomes rather than survey results because I didn't ask for any quantitative measurements. These are just ideas for how to make things better that I picked out of the responses. Almost everyone liked the current format so I'm not going to change anything about post frequency or size.

• More categories for tagging posts. I want to keep this at a reasonable number for manageability. I've currently got 17 categories, so I'll add categories that make sense but keep the total number under 25 for now.
• Build a table of contents. This was a really good suggestion because several other people complained that posts were hard to find. I'll tie this into the new categories that get created. I won't start doing this until after the server gets upgraded again to avoid broken links.
• Turning some of the multi-part series into long articles after they're done. I like to prioritize getting new content out but I realize that there are people that have not read all 180 posts and need help to catch up. This would eat the time slot for doing a normal post but I wouldn't do this more often than once every few weeks.
• More articles that tell you how to solve problems. I actually tried posting these kind of articles for a week and it ended up taking too much time because most problems are either way too short or way too long. It was a lot of research and editing. I can't do anything about the long problems, but I may post two articles at once if they're very short.

I can't make any promises about covering new topic areas. I like to write a lot of background before I go in-depth on a subject. I've already done 20 security posts, which is a solid month if they were all in a row. It's not practical to be doing that three of four times over at the same time. I started with channels and transports but since then I've added bindings, HTTP, message encoders, security, and TCP/IP. Every six to eight weeks I can probably take a week off from the normal schedule and do something totally new.