It's been a while since I've posed anything up here and it seems there's a new editor, so I thought I'd test some of it's features out!
Some web links: www.microsoft.com, www.maychild.co.uk, www.gmail.com
Some funcky fonts.
These editors are great for web use and really empower the user to create some great looking text. Within my current job, we use the Telerk editor with lots of success
I've returned after working on site for a few weeks, which I found to be a big learning experience. Working in an environment where you have no colleagues to bounce ideas off, limited Internet access and an unfamiliar PC really tests you. It is only when you are placed in this situation that you realize how much you depend on resources, and how helpful they can be, even simple things like having a cuppa with friends. You also begin to see how much customers rely on you. As I had no email, I had to catch up after hours, when other people had since left the office, and you find other work and support issues start to slip and tempers start to frey.
Thankfully, I finished, but their may be further installments.....
I've just knocked up an if statement that has about 6 expressions and it got me thinking about when to use a switch statement. I typically use switch statements for readability but there must be a specific scenario where using them will benefit over ifs. Someone at work mentioned that a switch is used to evaluate a variable and ifs to evaluate a condition. I also found this on the performance aspect.
What are other peoples opinions/ideas?
I started a project a number of weeks ago and as part of the project was responsible for the writing of the design spec (DS). In previous, non dot.net DS's, we have stipulated the methods, fields etc used in each page. This was more to allow for any other developer to pick up the project and understand what's happening than just for the sake of it. Obviously this meant that when/if the module changed, the DS had to be changed.
With dot.net this all changed. Now we don't include any of this information in the DS, we simply set XML Documentation file in the property pages of the project. This gives us warnings where we haven't commented a method etc and produces an XML file of our comments, we then use NDoc to convert it to a readable format. This ensures that the documentation matches to project 100%, as long as we remember to comment of course!
There's another article on MSDN.
More Posts