Redesigning DontCodeTired.Com (Part 1) - The Content Inventory

This is the first in a series of posts describing how I am redesigning the blog.

DontCodeTired is looking tired and boring, it also sucks when viewed on a mobile phone, hence I've decided to do a redesign. I am not a designer, if I was willing to pay for a designer (and I knew where to find one) I may have decided to use one. Certainly for a commercial project I would push heavily for a professional designer to be employed.

Building a content inventory

A content inventory is a way of examining and documenting the content that is currently on the site. This will not mean every individual post at this point, rather the key areas of content. The point of doing this is so at a later stage we can consciously decide what content is suitable for what devices, we may even throw away content completely.

At this point I don't want to pre-think about the actual new design - other than some what-extra-stuff-could-I-add.

Current DontCodeTired Content Inventory

Common to all pages
- Page header (title + sub title)
- Page footer ( be logo, dct link, terms of use link)
- Main nav menu
    - home
    - archive
    - contact
    - subscribe (rss)
    - log in
    - filter by APML

Common sidebars
- Silverlight apps links
- Tag cloud
- Recent posts
- Search box


- form

Log in page

Terms of use

Article (short view)
- Body Title
- by jason
- date time pub
- Body content
- rating
- tags
- sharing (email etc)
- permalink
- comment clink
- post RSS

Article (full view)
- prev next nav bar
- Body Title
- by jason
- date time pub
- Body content
- rating
- tags
- sharing (email etc)
- permalink
- comments link
- post RSS
- related posts
- comments

Possible New Content

- Advertisements: min one one each page, between posts, maybe side bar
- Logo
- Follow me on twitter button
- latest tweets/tweet? (only desktop & tablet??)
- Linked in profile link???
- My WP7 apps links
- My OS projects links
- Technical Debt Simulator
- share on g+
- share on fb
- share on twitter
- about me box (short aside) with link to longer about me page
- about me longer page

How it looks at this point


Redesigning DontCodeTired.Com (Part 2) - Designing with Personality


Brownfield Application Development (Part 2) - Lose Weight, Feel Great

If there was The Biggest Loser for software, legacy applications would be up there sweating on the treadmill and trying to resist the chocolate cake.

One of the characteristics of legacy code bases is bloat, fat, weight - basically stuff that we could do without.

This bloat slows us down: more scrolling, more stuff to distract us from the thing we're looking for, longer VCS operations, longer builds, more keystrokes etc.

15 Diet Tips for Overweight Apps

  1. Remove unused usings
  2. Removed DLL references that aren't needed (and delete the DLLs from source control)
  3. Delete commented out code (you are using a VCS right?)
  4. Delete pointless class or method XML comments (empty summary, params with no useful info, etc.)
  5. Delete unused class files
  6. Delete commented out tests
  7. Delete ignored tests (if you can't un-ignore them and get them working quickly)
  8. Delete bad tests (tests without asserts, etc.)
  9. Remove unused variables, methods, constants, etc.
  10. Remove unused JavaScript and CSS files
  11. Delete unused screens, pages, custom/user controls
  12. Removed unused CSS styles
  13. Remove pointless inline comments "// the line below declares a variable for loop counter"
  14. Remove multiple line spaces between members (unless you like them)
  15. Delete unused configuration settings


March Windows Phone 7 Roundup

Windows Phone SDK 7.1.1 Update Now Available

"it’s the final version of the CTP we released last month, and enables Windows Phone developers to do two things: Develop apps that work well on the new 256 MB devices; Use the WPSDK 7.1 to develop on machines running Window "

Find your local Windows Phone Champion

Reactive Extensions v2.0 Beta available now!

Windows Phone Data Binding Tutorial

Windows Phone Dev Podcast


FeatureToggle 1.1.0 Released

FeatureToggle 1.1.0 includes a new EnabledBetweenDatesFeatureToggle.
This toggle can enable a feature when the current date is between a start and end date.
Also in 1.1.0 all dates must be specified:  dd/MM/yyyy HH:mm:ss


Brownfield Application Development (Part 1) - Managing Motivation and Energy

[This is the first in a meandering and irregularly published series on brownfield / legacy application development.]

TL;DR: measure stuff that makes you happy when it gets better.

Working on a brownfield application can be frustrating, demotivating, difficult, energy-sapping and soul-crushing; or to put it in other words: "let's just re-write it".

Sometimes a re-write might be the best choice, and sometimes the people with the cash might let you do it - but more often than not we inherit an application and have no choice but to work on it.

Once you come to terms with the fact that you can't do a re-write you have to either start looking sources of happiness and motivation or give up and not care.

One way too look at a bad (tightly coupled, no tests, un-unit-testable etc.) brownfield application is that it offers a goldmine of potential for improvements.

One of the biggest motivators is a sense of progress. In brownfield development you need to find something to give you a sense of that progress. In Agile we see user stories moving across the wall and getting to the 'done' column, this is one sense of progress, but sometimes this may not be enough if you know that you're actually leaving the codebase in a worse state than when you found it.

For me, one great motivator is knowing that overall the codebase is getting better, it gives me a sense of personal achievement and I know that we are a small step closer to be able to respond more quickly to changing business requirements in the future.

We have tools to measure different aspects of code quality; the key thing is to find some metrics that make you happy when you see the lines going up on the graph. The 2 simplest ones to start using are number of tests and code coverage: while these only give a partial view of code quality when you see the figures getting better week-in, week out, it can start to engender a sense of pride in the code-base. This new-found sense of pride can lead to less of a tolerance for Broken Windows.

Once you start to feel this sense of pride and potential it can become a powerful motivational force: "how awesome will it be when we get 50% code coverage!", "wow I can't believe we had zero tests to start with now we have 500!", etc.

Once you get that initial 'buzz' going you can start to add a few more metrics such as lines of duplicated code, cyclomatic complexity, etc. I'm not sure if it is a good idea to throw all these things onto the graph at the start of the project as it may seem overwhelming: "what's the point, look how bad it is, we'll never be able to make it better".

One of the things to be careful of with this approach is that developers should not see the graph as the end goal, but rather a helpful friend that whispers in their ear "you doing a pretty good job dude, keep it up". It's also important not to concentrate too heavily on the actual numbers: "why has our coverage only gone up by 1% this week", the important thing is the line is going up - it's about the trend over time, not the individual measurements.

It's probably not a good idea to link KPI, bonus amounts, yearly reviews to these figures either - as pretty soon you'll end up with 110% code coverage ;)

One last point: brownfield development can be really hard, but it can also offer a great opportunity for growth and learning new techniques for dealing with the problems inherent in brownfield app development.


FeatureToggle Now On NuGet

FeatureToggle is now available via NuGet

Just search in NuGet Package Manager for FeatureToggle or in Package Manager Console:

PM> Install-Package FeatureToggle

PM> Install-Package FeatureToggle.WPFExtensions

The NuGet packages are the easiest way to get started, they will create an example feature toggle and app/web.config entries to help you get started.

Project home page:


Februaries Windows 7 Phone Roundup

"The Windows Phone SDK 7.1.1 Update – CTP provides a new 256 MB device emulator image and an updated 512 MB emulator, and it provides the ability to deploy, run, debug and profile your Windows Phone applications and games in the 512 MB emulator or the 256 MB emulator. "

“A Case Study for Building Advanced Windows Phone Applications: Connecting with Cloud Services"

"The Windows Phone DataContext feature allows you generate a DataContext for use in Windows Phone projects, based on an existing database, saving you a large coding effort."

"Microsoft is pleased to announce the beta release of the Amazon Web Services (AWS) SDK for Windows Phone. Built by Microsoft as an open source project, this SDK provides developers quickly connect and integrate Windows Phone applications with AWS (S3, SimpleDB, and SQS Cloud Services)"

"Choosing between Panoramas, Pivots and/or Pages"

Amazing list of a gazillion WP7 resources : "The Big Dummies Guide for Windows Phone Developer Resources"

Northern Lights WP7 Toolkit - collection of tools such as : "NagForReview will ask, after a fix set of days and/or application starts, the user to review your app", "The checking of the application version against a txt file on a remote server enables you to inform the user, on startup of the app, that a newer version of your application is available", "The LittleWatson class let's you catch unhandled exception and automatically report them back to you through a webservice or let the user e-mail to you the next time the user opens up the application"

"Winning on the Marketplace: The differentiation game"

"With App Connect, your application can be launched from the Pictures Hub, enabling a convenient launch experience for picture-related applications. This topic describes how to create an application that can be launched from the Pictures Hub."

"Get Your Windows Phone Applications in the Marketplace Faster"

"Performance Considerations in Applications for Windows Phone"

"Performance Techniques for Windows Phone"

Windows Phone Background Agents Pitfalls

"Analyzing and Improving Windows Phone Application Performance"

Task based asynchronous programming CTP

Detailed discussion on memory costs in WP7 "WP7: CLR Managed Object overhead"

"7 Deadly Sins for … Windows Phone Developer"

MetroGridHelper - "fix those margins, align, and try and make your apps as beautiful and inspiring as you can"

A version of MetroGridHelper that works at design time in Visual Studio/Blend

"Silverlight Validation WP7"

Really awesome, clear and concise guidelines for using Windows Phone 7 App Bar

Adding a Privacy Policy to your app

"Designing Windows Phone Icons"

Great tutorial on creating icons in Expression Design


Record and playback sound

Dragging UI items

"An overview of fast application switching and page state in Windows Phone"

Introducing MoqaLate, (probably) The World's Only Mocking Framework for Windows Phone 7 (WP7)

"This sample is the bare bones “how to use accelerometer”"

Great guide from Telerik on how to market your app, contains advice and some great links.


Introducing (probably) The World's Only Mocking Framework for Windows Phone 7 (WP7)

Introducing MoqaLate

Whilst I love developing apps for Windows Phone 7, the testing aspect is hard! I'm a TDD-er by default and it's such a pain to have to hand roll my own mock objects. 

So I created MoqaLate.

It's an alpha version but is usable now.

Not sure framework is the right term but it's something that generates mocks from your interfaces.

Add to existing project from NuGet:

PM> Install-Package MoqaLate

Read more about the project.

Download an example solution.

Read (currently very basic!) documentation.

View on

Awesome overview diagram :)