Personal Software Development Practices

  • Don’t fear the code. It’s just code.
  • Never write (or copy) a line of code that you don’t fully understand.
  • Figure out how things really work and why they work they way they do.
  • If you don’t understand something, go deeper. Read the source code for the library you’re using.
  • Use tools to figure out how things work–debugger, unit tests, sample programs.
  • Create a punchlist to guide your work–investigations, things to do, things to test
  • Test the hell out of your code. Be as thorough as possible
  • When you get stuck, go for a 5 minute walk.
  • When you get stuck, describe your stuckness out loud to somebody else.
  • Write down what you’ve learned. Create a FAQ document and answer all the questions.
  • Try to teach someone else what you’ve learned. Create a blog.
  • Leave breadcrumbs for yourself and others–personal notes or comments in the code.

A Recipe for Green-Field Software Development

[Re-post from Nov, 2008]

Developing Your Product and Your Customers in Parallel

I’ve been a member of a software development team since 1985.  That’s 23 years as a software developer.

Like many developers who have been around for a few years, some of my grey hair can be attributed to having worked on hellish projects, or on projects that failed outright.  Over the years, I’ve gradually added to my mental list of “worst practices”—things that tend to lead to project failure, or at least hide a failing project until it’s too late to turn it into a successful one.

It’s much easier to compile a list of worst practices than it is to pick some “perfect” development process.  But worst practices can lead to best practices simply by avoiding the bad practices.  At a minimum, we should at least avoid making the same mistakes over and over again.

If I had to pick a single worst practice (there are many), it would be this:

Not building the product that the customer really needed

This happens all of the time.  We (the developers) build a product that is bug-free, efficient, scalable, and does exactly what we intended it to do.  We even occasionally get the work done in something close to the amount of time that we said it would take.

But our well-built software still fails—for a variety of reasons.

  • It’s too hard to use
  • Users are unable to use it efficiently/effectively
  • It’s missing one or more critical features
  • Users don’t have a need for the software in the first place
  • It’s too expensive, given what it does

In order to be “successful”, software has to meet a critical need that the user has.  Good software solves a pressing problem.  Great software does so in a way that seems natural to the users.

So what do I mean by software “failure”?  Simply put, “failed” software is: software that doesn’t get used.

What are the consequences of failure?  For internal software projects, it means wasted time and energy that could have been spent on things that the organization does need.  For consulting houses, it means possibly not getting hired back by the client, or seeing your reputation diminished.  For ISVs developing software/services to sell, it means lost revenue or even bankruptcy.

For developers, failure means knowing that you’ve wasted your time, intellect and energy on something that no one is going to use.  That’s no fun.

Our goal then as developers is to build great software.  We want to see users working with our stuff, to see it making their lives better, and to see them excited about it.  That’s the true Holy Grail that many of us work towards.

The Remedy

So how do we develop great software?  We can’t all be Steve Jobs, or hire him into our organization.  So without brilliant insight, how do we figure out what the users truly need?

To understand what users need—truly, madly, deeply—we need to think beyond developing products and start thinking about developing an understanding of our users.

This focus on a Customer Development Process, rather than a Product Development Process, is the point of the book The Four Steps to the Epiphany, by Steven Gary Blank.

Blank’s main thesis is that we should work towards an understanding of our customers and their needs much earlier in the development lifecycle.  We need to fully understand what customers need and whether we can sell them our product before we go too far down the path of building that product.

Blank proposes a very detailed Customer Development Process and talks a little bit about when it should occur, relative to the typical phases of a Product Development Process.  This is a little tricky.  If we wait too long to learn about our customers, we risk building the wrong product.  But if we talk to them too early, before we’ve had time to think a little bit about our vision, we’re not really innovating, but just trying to build what they tell us to build.  That also can lead to failure.

The Product Development Process

Having worked as a software developer for so many years, I’ve seen lots of different software lifecycles.  In my first job, with Control Data Corp in Bloomington, MN, we were a Dept of Defense shop and rigidly followed DOD-STD-2167A—a very rigidly-defined classic waterfall process.  (Ask me about the 4-foot high Software Requirements Specification).

I’ve also done my share of agile development, working in groups that used various agile methods.

My main takeaway on software process is that it’s important to develop iteratively.  For me, that’s the most critically important piece of the agile movement.  Many of the other techniques, like pair programming and test driven development might be important, but don’t seem quite as critical as being able to build your product iteratively.  Short iterations allow agility.

For me, one book that really made a lot of sense in laying out a framework for an iterative lifecycle was The Rational Unified Process Made Easy, by Per Kroll.

For a lot of people, when they think about RUP (Rational Unified Process), they think: heavyweight and lots of modeling/diagramming.  But Kroll explains that RUP doesn’t necessarily mean heavy.  He refers to the number of artifacts that you’re required to produce as your level of ceremony.  And he describes RUP as:

An iterative approach with an adaptable level of ceremony

Again, iterative is the important part.  An iterative approach with very little ceremony would basically be an agile methodology.  But sometimes you work on projects that require a bit more ceremony—some project tracking, etc.  On these projects, you can still be iterative, but with more ceremony.  Here’s a picture:


RUP talks about general phases of the lifecycle being: Inception, Elaboration, Construction and Transition.  But Kroll is quick to point out that this does not just map to the classic waterfall model.  (Requirements, Analysis/Design, Implementation, Testing).  Rather, you’d typically perform some of each of the classic waterfall activities during each iteration of RUP.  You’d likely be doing a lot more requirements-gathering in your Inception phases, but you’d also be doing some implementation.  And you’d spend a lot of time writing code during Construction phases, but you might also still be tweaking some requirements.

Here’s a nice picture of how RUP typically plays out.  Again, note that the idea of iterations is important:


Personally, I like this view of the development lifecycle a lot.  This model is how I think about software development.  Work in an iterative fashion, but be aware of what main phase you’re in and adjust your activities accordingly.

Over the years, I’ve taken lots of notes to answer the question, “what activities should I be doing at each step”?  Kroll has a lot of good information in his book, but I’ve borrowed liberally from other sources.  What I ended up with was a fairly detailed “a la carte” list of activities that you might engage in across the lifecycle.

I say “a la carte” because every project will not engage in every step.  But I think it’s a nice master list to draw from.  And I think that I have the activities listed in a pretty reasonable order.

So here’s my list of high-level activities for the Product Development Lifecycle.  (See below for more detail for each activity):

  • Vision
  • Initial Requirements Gathering  (Inception)
  • GUI Conceptualizing
  • Identify Candidate Architecture
  • Define Non-Functional Tasks
  • Define Iterations  (Project Planning)
  • Write Development Plan
  • Execute Elaboration iterations
  • Write Business Plan
  • Write Test Plan
  • Write Deployment Plan
  • Execute Construction Iterations
  • Initiate Test Plan
  • Deploy Alpha Release
  • Write Customer Support Plan
  • Execute Deployment Iteration
  • Deploy Beta Release
  • Launch Product
  • Begin Planning Next Release

The Customer Development Process

I love the idea of the Customer Development Process, as Blank presents it in The Four Steps to the Epiphany.  He talks about discovering who your customers are, figuring out what they need, and then testing your hypotheses.  In other words—iterate not just on the product, but also on your model of who the customers are.  This includes not just an understanding of the customers and their needs, but also gets into the actual selling proposition and marketing of your product.

Here are the top-level activities in Blank’s customer development process:

  • Customer Discovery
  • Customer Validation
  • Customer Creation
  • Company Building

Lining Things Up

The trick is to figure out how the Product Development Process and the Customer Development Process relate to each other.  If you listed out the various phases of each process side by side, how would they line up?  At what point in your product development process should you start the customer development process?  Or should it be the other way around?

Here’s a first stab at lining the two processes up.  My goal was to come up with a high-level roadmap for doing new (green field) development, which would cover developing both the product and the customers.

Product Development Process
Customer Development Process
Initial Requirements Gathering
GUI Conceptualizing
Identify Candidate Architecture
Define Non-Functional Tasks
Define Iterations (Project Planning)
Write Development Plan
Execute Elaboration Iterations  >> Customer Discovery
Write Business Plan
Write Test Plan
Write Deployment Plan
Execute Construction Iterations  >> Customer Validation
Initiate Test Plan
Deploy Alpha Release  >> Customer Creation
Write Customer Support Plan
Execute Deployment Iteration
Deploy Beta Release
Launch Product
Begin Planning Next Release  >> Company Building

Should I Keep Reading?

The rest of this post expands on each of the activities in the table above, listing details of what happens during each phase.  This is the outline that I use when I’m trying to figure out “what to do next”.

Note again—this process is very much geared towards green-field development, and in a market where you are developing a product or service to sell to end-users.

Product Development Process—Details

Here’s the detailed breakdown of the steps involved in the Product Development Process.  Much of this content comes from the books I list at the end of the article, primarily The Rational Unified Process Made Easy and Head First Software Development.  But a lot of it is just my own concept of what you typically do during each phase.

Note that iterations occur in the Elaboration and Construction phases.


  • Do a short description of a handful of possible products
    • For each, describe:
      • Market or market segment  (which group of users, short description)
        • What is the problem that they experience
        • How painful to the users?  What workarounds are in place?
      • Short description of product that might help them solve this problem
      • Short feature list (<10 items, single sentence)
      • How does this product specifically solve the customer’s problem?
  • Expand on top one or two possible products.
    (For each, expand information to include):

    • Write up SIMs (Specific Internet Market Segment, Walshpg 158..)
      • Lots of details about the targeted user group
    • Other user information
      • How often do you expect each user group to user the product?
      • Why might they stop using the product?
      • Rough guess as to size of this market, e.g. # potential users?
    • Are there other non-primary users?
      (E.g. users who didn’t purchase, or just different group of users)

      • Also describe their “problem” and how product solves it
      • Are they also potential buyers, or just users?
      • What subset of the feature list might they use?
      • What else differentiates them from primary user group?
      • Also write up SIM for this user group
    • Bluesky one or more revenue models.  Answer for each:
      • What would this customer pay for this product?
        • Specify target price or range that might be tolerable
      • One-time purchase or ongoing subscription?  (or a combination)
      • Pricing tiers?  If so, describe
      • Trial period?  If so, describe
      • If >1 user group, repeat for other groups
      • What level of certainty do you have that they will purchase?
      • Why might they not purchase?  List reasons.
      • Possible ways to mitigate non-purchase reasons.
      • Does revenue model depend on continued use of the product?
      • How will you collect money?
      • What is your distribution channel?  (i.e. how do they receive product)
      • If ongoing subscription, describe what happens when they stop paying
        (E.g. limited access)?
    • Revenue model/estimates  (per yr)
      • Make rough estimate of ongoing costs, per user or account
      • List expected revenue per user, single or ongoing, per yr
      • Starting with desired annual revenue, describe # customers required to meet goal
    • Marketing / Sales vision
      • How might product be branded?
      • How is product positioned (e.g. tagline)
      • How might you reach desired users?  (make aware)
      • What is selling proposition (argument to buy)?
    • Competitive analysis
      • Assess and summarize competitive products that do similar/same thing as yours
      • What are their strengths/weaknesses?
      • Where can you improve on them?  To what degree?
      • What are you missing that competitors might have?

Initial Requirements Gathering
(Chap 2 of Head First Software Development)

  • Generate quick list of basic ideas, 1-3 sentences each, Title/Description
  • Ask user questions to flesh out the list
  • Bluesky to generate feature lists (Title/Description)
    • Use other people
    • Okay to spit out non-functional stuff, like specific GUI thoughts, or architecture
  • Build User Stories
    • Describe one thing
    • Language of the customer
    • Title/Description
    • 1-3 sentences
  • Pull out non-customer stories, save for later (design)
  • Refine initial set of user stories, w/customer feedback
  • Provide estimates for each user story
    • Include assumptions
  • Team estimation and revision
  • Clarify assumptions w/users, if necessary
  • Break apart users stories that are >15 days
  • Add up estimates to get estimate for total project

GUI Conceptualizing

  • Select key use cases that need GUI concept
  • User interaction goals
    • Outline some key goals of user interaction model
      (E.g. discoverability, efficiency, slick animation, etc)
    • Describe user action requirements verbally for specific use cases
  • Assess similar products’ GUIs for similar use cases
    • Pros/cons of each
  • For each use case selected
    • Paper prototype one or more possible GUIs
    • Storyboard any dynamic behavior
    • Brainstorm alternative approaches and paper prototype
  • Identify common sequences of use cases  (e.g. find/edit)
    • Storyboard use case sequences
    • Brainstorm ways to optimize the storyboard/sequence
  • Assess GUI model against several measures of good GUI design
  • Technical review of GUI feasibility
    • Build it, buy it, or freebie (part of tool or freeware)?
    • If build, rough guess as to effort
    • If buy, what is the cost?  One-time & ongoing.
  • Assess technical risk
    • Are there any aspects of GUI that need to be proven out?
  • Hammer looking for nails
    • Make short list of most compelling GUI models in new products
    • Is there anywhere in product that you might use these models?
  • Brainstorm user assistance model (help, wizards, demos, etc.–learning)
  • GUI models from competitors
    • If there are competitive products that compete in same space, summarize their main GUI elements.
    • Assess—is their GUI or user interaction model an asset or a liability?
  • Review
    • Early review internally (not w/customers)
    • Review static screen mockups (e.g. paper prototypes)
    • Look at discoverability–obvious what it’s used for?
    • Aesthetics

Identify Candidate Architecture

  • Identify one possible architecture that could support the product
  • Identify any areas of technical risk
  • Discuss pros/cons/risks
  • [For more details, see Kroll]

Define Non-Functional Tasks

  • Define additional tasks to be completed during inception that are NOT use cases
  • Possible examples include:
    • GUI proof-of-concept, for technical & usability
    • Building candidate architecture  (must do)
    • Technical proof-of-concept
    • Capacity testing for architecture (e.g. scalability)
  • Provide priorities and estimates for all tasks
    (will feed into iteration planning, along w/use cases)

Define Iterations
(Chap 3 of Head First Software Development)

  • Set target date for first (next) release
  • Work w/customer to prioritize user stories
  • Also feed non-functional tasks into process
  • Select subset of user stories to meet target date  (Milestone 1)
    • If the features don’t fit target date, re-prioritize
    • Focus on user stories that are absolutely critical
    • Baseline functionality–smallest set of features so that SW is at all useful to customers
  • Prioritize user stories in Milestone 1.0  (1-5, with 1 as highest priority)
  • Assign user stories to iterations, using 20-day iterations
    • Based on priority
    • Or user stories required to implement other user stories
    • Use velocity of 0.7  (0.7days effort for each real day)
      I.e. Each iteration should contain 14 person-days of estimated work
  • Reassess schedule and adjust schedule and/or content
    • Because of velocity, things likely can’t fit
    • Add iteration(s), change M1 date, or both
  • Get iterations & user stories into tracking spreadsheet
  • Construct burn-down graph for 1st iteration
    • X axis is calendar days
    • Y axis is person-days of work accomplished
    • Draw diagonal line as ideal burn-down rate

Write Development Plan

  • Describe everything that will happen from here on out
  • Include
    • Iterations and contained user stories & tasks
    • Milestones
    • Review points and staff
    • High-level test plan
    • alpha/beta/release plan
    • Staff
    • Schedule
    • Tools
    • Show steps in Product Development process
    • Show steps in Customer Development process
    • Show how the two processes line up
    • Include calendar alignment, if appropriate

Execute Elaboration Iterations
(Chap 4 of Head First Software Development – User stories & tasks)

  • Break down each user story into tasks
    • Title/Description/Estimate
    • Provide estimate for each task
    • E.g. Create class, create GUI prototype, create schema, create SQL scripts
    • Each task should be 0.5 – 5 days
  • Plot where you are on burn-down graph
    • Calendar day vs. new estimate of person-days of work left
  • Update spreadsheet w/tasks & their estimates
    • Task estimates replace user story estimates
    • Also track burn-down in spreadsheet
    • Put stickies on big board, tasks, In Progress/Complete, etc. (pg 116 of Pilone/Miles)
  • Start working on first tasks
    • Move stickies on board when they are In Progress
  • Daily stand-up meetings to track progress
    • First thing in the morning
    • Track progress–what has each person accomplished
    • Update burn-down rate
    • Update tasks
    • What happened yesterday, what is plan for today
    • Talk about any problems
    • 5-15 mins long
  • Add unplanned tasks to iteration, if necessary
    • Add user story, estimate, break into tasks, review w/customer, add to board
    • Use red stickies
    • Update burn-down, showing that you’re off
  • Next iteration
    (Chap 10 of Head First Software Development)

    • End of iteration review (pg 342-343 of Pilone/Miles)
    • Verify SW passes all tests
    • Demo/review w/customer
    • Plan next iteration
      • Add new user stories, if required
      • Update priority/estimates for everything
      • Adjust velocity
      • Feed in bug backlog as tasks
      • Priority tradeoffs include bug-fixes vs. new features
    • Follow steps from Pilone/Miles chap 4 (break down into tasks and estimate)

Write Business Plan

  • Goal isn’t to get funding, but to make a case for the product/business
    (at least on paper)
  • Include stuff like
    • Market description
    • Customer description
    • Description of competitors’ products/services
    • Product proposition
      • What is customers’ problem?
      • What is your vision for product/service
      • How does product/service solve their problem?
    • Outline of development plan
    • Outline of Product/Customer Development processes
    • Summarize revenue model
    • Summarize marketing/sales plan
    • Business structure: staffing, organization, etc.
  • Add other typical business plan elements

Write Test Plan

  • What to test, how to test, when to test
  • Plan for test-driven development, using appropriate TDD tools
  • Plan automated/nightly builds and automation of testing
  • See Pilone/Miles, chap 7, among others

Write Deployment Plan

  • How/when will software be deployed?
  • Map out alpha/beta/launch
  • Where does testing fit into the plan?
  • How will customers get the software?
  • How will they pay for it?
  • How do you track customers?

Execute Construction Iterations
(Chap 4 of Head First Software Development – User stories & tasks)

  • Break down each user story into tasks
    • Title/Description/Estimate
    • Provide estimate for each task
    • E.g. Create class, create GUI prototype, create schema, create SQL scripts
    • Each task should be 0.5 – 5 days
  • Plot where you are on burn-down graph
    • Calendar day vs. new estimate of person-days of work left
  • Update spreadsheet w/tasks & their estimates
    • Task estimates replace user story estimates
    • Also track burn-down in spreadsheet
    • Put stickies on big board, tasks, In Progress/Complete, etc. (pg 116 of Pilone/Miles)
  • Start working on first tasks
    • Move stickies on board when they are In Progress
  • Daily stand-up meetings to track progress
    • First thing in the morning
    • Track progress–what has each person accomplished
    • Update burn-down rate
    • Update tasks
    • What happened yesterday, what is plan for today
    • Talk about any problems
    • 5-15 mins long
  • Add unplanned tasks to iteration, if necessary
    • Add user story, estimate, break into tasks, review w/customer, add to board
    • Use red stickies
    • Update burn-down, showing that you’re off
  • Next iteration
    (Chap 10 of Head First Software Development)

    • End of iteration review (pg 342-343 of Pilone/Miles)
    • Verify SW passes all tests
    • Demo/review w/customer
    • Plan next iteration
      • Add new user stories, if required
      • Update priority/estimates for everything
      • Adjust velocity
      • Feed in bug backlog as tasks
      • Priority tradeoffs include bug-fixes vs. new features
    • Follow steps from Pilone/Miles, chap 4 (break down into tasks and estimate)

Initiate Test Plan

  • Begin regular testing
  • Functional, integration, system test (no customer testing yet)

Deploy Alpha Release

  • Outline goals for beta and exit criteria
  • Identify potential customers/users
  • Communicate w/users about goals & feedback mechanism
  • Feeds into appropriate spot in Customer Development process
    • Possibly at end of each construction iteration
  • Gather feedback and feed into development
    • E.g. Changes desired/required?

Write Customer Support Plan

  • How will customers be supported after software is deployed?
  • List main goal(s)
  • Decide on tools, e.g.
    • External issue tracking
    • FAQ sheets for tech support staff
  • Decide on process(es), e.g.
    • Communication w/customer
    • Looking for answer in FAQ
    • How to communicate answer, if known
    • Get closure
    • 2nd tier–investigate, look for workaround
    • Interaction between staff (e.g. support/development)
    • 3rd tier–reported bug, e.g. give bug # and have traceback mechanism
  • Escalation process

Execute Deployment Iteration

  • Working on deployment tasks, e.g.
    • Installs/uninstalls
    • Distribution/delivery
    • Payment
    • Customer tracking

Deploy Beta Release

  • Outline goals for beta and exit criteria
  • Identify potential customers/users
  • Communicate w/users about goals & feedback mechanism
  • Feeds into appropriate spot in Customer Development process
    • Likely after Deployment Iteration
  • Gather feedback and feed into development
    • E.g. Changes desired/required?
  • Beta should not last indefinitely

Launch Product

  • Announce product
  • Launch it
  • Throw a big party

Begin Planning Next Release

  • Post-mortem for Product/Customer Development processes
  • Lessons learned
  • Changes to process
  • Assess organize outstanding bugs
    • Prioritize, estimate
  • Organize list of possible future features
    • Plan mechanism for using existing customers to get feedback on priorities
    • Prioritize, estimate
  • Decide on schedule for next release
  • Map out iterations
    • Each iteration either bug-fixing or new development
    • Bug-fixing phase likely first
  • Goal: All bugs fixed prior to next release
  • Continued refinement of plan, based on ongoing customer feedback
  • Back to start of Product/Customer Development processes for next release
    (follow same processes, including updating relevant plans)

Customer Development Process—Details

Here’s the detailed breakdown of the steps involved in the Customer Development Process.  This comes directly from Four Steps to the Epiphany.

Customer Discovery

  • State hypotheses
    • Write briefs, state assumptions about product, customers, pricing, demand, competitors
  • Test problem hypotheses
    • Test in front of potential customers
  • Test product concept
    • Test product features in front of customers
    • Solves their problem?
    • Also test business model
      • Must-have?
      • Pricing
      • Distribution
  • Verify
    • You understand the customer’s problems
    • Your product solves these problems
    • Customers will pay for the product
    • You have in mind a profitable business model
  • Repeat if necessary

Customer Validation

  • Get Ready to Sell
    • Articulate value proposition
    • Prep sales materials & collateral plan
    • Develop distribution channel plan
    • Develop sales roadmap
    • Hire sales closer
    • Synch up Product/Customer Dev teams on features/dates
    • Formalize advisory board
  • Sell to Visionary Customers
    • Sell unfinished product
    • Answer all sales roadmap questions
  • Develop Positioning
    • Initial positioning
    • Articulate belief about product and its place in the market
  • Verify
    • Enough orders to prove we can sell?
    • Profitable sales model?
    • Profitable business model?
    • Can you scale the business?
  • Repeat, if necessary

Customer Creation

  • Get Ready to Launch
    • Market Type Questionnaire
    • Choose Market Type
    • Choose 1st Year Objectives
  • Position company & product
    • Select PR agency
    • Positioning audits
    • Positioning to market type
  • Launch company & product
    • Select launch type
    • Select customer audience
    • Select the messengers
    • Craft the messages
    • Message context
  • Create demand
    • Demand creation strategy
    • Demand creation measurements
    • Iterate or exit

Company Building

  • Reach mainstream customers
    • Change “earlyvangelists” into mainstream customers
    • Manage sales growth by market type
  • Review management / Create mission culture
    • Review management
    • Develop “mission-centric” culture
  • Transition to functional departments
    • Set department mission statement
    • Set department roles by market type
  • Build fast-response departments
    • Implement mission-centric management
    • Create an “information culture”
    • Build a “leadership culture”

Closing Thoughts

The key takeaway for me from Blank’s book was as follows:

It’s not enough to build a great product.  You must also build a product that the customers need and that they will buy.  It’s also critical to find a workable business model to sell to the right customers at the right price.

If you haven’t yet read Four Steps to the Epiphany, I’d really encourage you to go out and read it.  Then you can start thinking about how to develop your customers, as well as your product.


I’ve used the following sources, in varying degrees, for this post:

Why I Turned Off WordAds

Below is a letter that I recently sent to WordPress support, on the occasion of my turning off WordAds on two of my blogs.  The attachments that I mention, examples of ads on my blogs, appear after the content of the letter.


23 Jan 2013

I host two blogs on WordPress for which I signed up in the WordAds program.

I’m going to disable WordAds in both cases, based on the type and style of ads that are being shown.  But I thought it fair to share some thoughts with you, related to why I’m turning off WordAds.

The blogs are: and

Both of these blogs are quite small, in terms of traffic.  The first blog gets around 10,000 hits/mon, with just under 12,000 impressions in the most recent month.  The second blog is around 20,000 hits/mon, with just under 20,000 impressions in Nov, 2012.

Given how tiny these blogs are, in terms of traffic, I realize that WordPress won’t care all that much whether or not I host ads.  But I’d still like to share some quick thoughts on the ads being served, since this applies to any of your blogs serving WordAds.

My main complaints with the ads being served are:

  • They don’t look like ads  (e.g. ad consists solely of embedded YouTube video)
  • Ads are not separated from my blog content in any way, e.g. with a border
  • Ads aren’t relevant to my readers
  • Multiple ads leads to the web page being cluttered
  • The visual style of the ads cheapens my blog / brand

What I’d hope for with ads are ads that follow the more traditional design guidelines of print ads a little more closely.  I.e. They are clearly offset by a border and marked as an ad and they clearly contain a brand image for the item or service being advertised.  Ads that contain other content, like images from YouTube videos and giant Download buttons, overpower the content of my blog and also confuse the reader by appearing to be part of my content, rather than an ad.  (See attached images for examples, from my blog).

There are all sorts of ads served on the web.  Some are very tasteful and elegant, some less so.  I’m disappointed that the ads served up via WordAds are consistently in the latter category.  An ad should not actively try to pull the reader’s attention from the content and it should definitely not try to “trick” the reader into doing so (e.g. large download buttons).  Rather, professional ads should respect the reader by being clearly marked as an ad, displaying the relevant brand, and trusting that the reader will read the ad if they are interested in the product or service.

As a blog author, my main request in the area of ads is that they appear to be at least as professional and tasteful as my blog itself.  Since the ads served by WordAds are failing to live up to that expectation, I’m going to turn them off.  WordPress does host many blogs that I would consider to be well-designed and tasteful.  Your themes are also beautifully designed, with a very professional look.  But the ads that you’re currently serving don’t rise to that standard.  They cheapen not only the individual blogs that serve the ads, but the WordPress brand itself.

I realize that serving web-based ads is a tricky business to be in.  Wordpress needs to make money, as do the vendors serving the ads.  And given the state of web-based ads, it’s easy to serve up the same sort of ads that the other guys serve.  But given the strength and respectability of the WordPress brand, I would hope that you’d set the bar a little bit higher.  WordPress is already a leader when it comes to hosting blogs.  With some changes to the ads that you serve, you could also be a leader in the area of served ads, setting an example for other content producers on the web.

Thanks for taking the time to read this and to consider my thoughts.

Sean Sexton

130123 - Ad Complaint  130123-Ad2

The Latest on HP TouchPad Availability

I just received the following e-mail update on HP TouchPad availability.  I think I would have payed $99 for a TouchPad when it was first discounted, but after hearing so many stories of sluggishness and other problems, I’m unlikely to get one now–even at $99.

—E-Mail from HP—

Dear Customer,

Thank you for your interest in the HP TouchPad and webOS. The overwhelming demand for this product in recent days has made it difficult to fulfill your request at the present time, and we are working to make more available as soon as possible. While we do not yet have specific details, we know it will be at least a few weeks before we have a limited quantity available again. We will keep you informed as we have more specifics that we can communicate, and we encourage you to join the conversation here for the latest information.

In light of this and other recent HP news, we want you to know that we remain committed to you. We will continue to honor our warranties now and in the future. We will continue delivering products that make a difference in your life and we will continue to provide the best possible service to you every day.

We are grateful for your patience and loyalty and to show our gratitude, we are offering you an exclusive one-time opportunity to save an additional amount on all of our products, valid through the end of the day tomorrow, Wednesday, August 31, 2011. You’ll save 25% off all printers, ink, HP accessories, and PCs starting at or above $599. To take advantage of this offer, use your unique coupon code 4856696 at checkout, and for more information on the details of this offer, please look at the bottom of this email.


—E-Mail from HP—

MDC 2010 Takeaways

I attended the Minnesota Developers Conference (MDC 2010) yesterday in Bloomington, MN.  A nice dose of conference-motivation–some good speakers talking about great technologies.  In the FWIW category, here are my lists of takeaways for the talks that I attended.

1.       Keynote – Rocky Lhotka (Magenic)

General overview of development landscape today, especially focused on cloud computing and the use of Silverlight.  Takeaways:

  • We’re finally getting to a point where we can keep stuff in “the cloud”, access anywhere, from any device
  • Desire to access application data in the cloud, from any device, applies not just to consumer-focused stuff, but also to business applications
  • Smart client apps, as opposed to just web-based, are important/desired – intuitive GUI is how you differentiate your product and what users now expect
  • HTML5 is on the way, will enable smart client for web apps
  • Silverlight here today, enables smart clients on most devices (not iPhone/IOS)
  • Silverlight/WPF is ideal solution.  You write .NET code, reuse most GUI elements on both thick clients (WPF) running on Windows, and thin clients (Silverlight) running web-based or on mobile devices
  • I didn’t realize that I have in common with Rocky: working on teletypes, DEC VAX development, Amiga development. :O)
  • , @RockyLhotka (Twitter)

2.       WPF with MVVM From the Trenches – Brent Edwards (Magenic)

Practical tips for building WPF applications based on MVVM architecture.  What is the most important stuff to know?  Excellent talk.  Takeaways:

  • MVVM excellent pattern for separating UI from behavior.  Benefits: easier testing, clean architecture, reducing dependencies
  • MVVM is perfect fit for WPF apps, very often used for WPF/Silverlight
  • MVVM perfect fit for WPF/Silverlight, makes heavy use of data binding
  • Details of how to do data binding in MVVM, for both data and even for command launching
  • How to use: data binding, DataContext, Commanding, data templates, data triggers, value converters.  (Most often used aspects of WPF)
  • Showed use of message bus, centralized routing of messages in typical MVVM application.  Reduces coupling between modules.  (aka Event Aggregator).   Used Prism version.
  • Slide deck –
  •, @brentledwards (Twitter)

3.       Developer’s Guide to Expression Blend – Jon von Gillern (Nitriq)

Demoing use of Expression Blend for authoring UI of WPF/Silverlight apps.  Also demoed Nitriq/Atomiq tools.  Takeaways:

  • Blend not just for designers; developers should make it primary tool for editing GUI—more powerful than VStudio
  • Lots of tricks/tips/shortcuts – he handed out nice cheatsheet –
  • Very easy to add simple effects (e.g. UI animations) to app elements to improve look/feel, just drag/drop
  • Nitriq – tool for doing basic code metrics, summaries, visualize code, queries that look for style stuff.  (Free for single assembly, $40 for full )
  • Atomiq – find/eliminate duplicate code, $30
  •, @vongillern (Twitter)

4.       Introduction to iPhone Development – Damon Allison (Recursive Awesome)

Basic intro to creating iPhone app, showing the tools/language/etc.  From a .NET developer’s perspective.  Takeaways:

  • You have to do the dev work on a Mac—no tools for doing the work on Windows
  • The tools are archaic, hard to work with, much lower level than .NET.  (E.g. no memory management)
  • In many cases, consider creating web-baesd mobile app, rather than native iPhone.  But then you wrestle with CSS/browser issues
  • Worth considering creation of native iPhone app for the best user experience
  • Lots of crestfallen-looking .NET developers in the audience
  • , damonallison (Twitter)

5.       A Lap Around Prism 4.0 – Todd Van Nurden (Microsoft)

Showing Prism—a free architectural framework written by Microsoft, came out Patterns and Practices group.  Good for creating extensible apps, with plug-in model.  Takeaways:

  • Leverages MEF (Microsoft Extensibility Framework)
  • Good for apps where you have the idea of a lot of “tools” that plug into main application architecture.  Or for applications made up of various building blocks.
  • You write application modules that are decoupled from main app framework, loaded on demand.
  • Prism on Codeplex –

The Baby Has Two Eyeballs


Driving home the other night, I was teasing my 4-yr old daughter (as I often do).  We were talking about what sorts of games to play when we got home and I suggested that we could spend our time poking Lucy’s baby brother Daniel in the eye.  I also pointed out that we’d have to take turns and asked Lucy which of us should go first.

Lucy protested.  “Daddy”, she said excitedly, “we don’t have to take turns–Daniel has two eyeballs”!

After I stopped laughing at this, I realized that Lucy had seen something very important, which hadn’t even occurred to me:

Poking a baby in the eye is something that can be done in parallel!

Yes, yes, of course–you should never poke a baby in the eye.  And if you have a pre-schooler, you should never suggest eye-poking as a legitimate game to play, even jokingly.  Of course I did explain to Lucy that we really can’t poke Daniel in the eye(s).

But Lucy’s observation pointed out to me how limited I’d been in my thinking.  I’d just assumed that poking Daniel in the eye was something that we’d do serially.  First I would poke Dan in the eye.  And then, once finished, Lucy would step up and take her turn poking Dan in the eye.  Lucy hadn’t made this assumption.  She immediately realized that we could make use of both eyeballs at the same time.

There’s an obvious parallel here to how we think about writing software.  We’ve been programming on single-CPU systems for so long, that we automatically think of an algorithm as a series of steps to be performed one at a time.  We all remember the first programs that we wrote and how we learned about how computers work.  The computer takes our list of instructions and patiently executes one at a time, from top to bottom.

But, of course, we no longer program in a single-CPU environment.  Most of today’s desktop (and even laptop) machines come with dual-core CPUs.  We’re also seeing more and more quad-core machines appear on desktops, even in the office.  We’ll likely see an 8-core system from Intel in early 2010 and even 16-core machines before too long.

So what does this mean to the average software developer?

We need to stop thinking serially when writing new software.  It just doesn’t cut it anymore to write an application that does all of its work in a single thread, from start to finish.  Customers are going to be buying “faster” machines which are not technically faster, but have more processors.  And they’ll want to know why your software doesn’t run any faster.

As developers, we need to start thinking in parallel.  We have to learn how to decompose our algorithms into groups of related tasks, many of which can be done in parallel.

This is a paradigm shift in how we design software.  In the same way that we’ve been going through a multiprocessing hardware revolution, we need to embark on a similar revolution in the world of software design.

There are plenty of resources out there to help us dive into the world of parallel computing.  A quick search for books reveals:

Introduction to Parallel Computing – Grama, Karypis, Kumar & Gupta, 2003.

The Art of Multiprocessor Programming – Herlihy & Shavit, 2008.

Principles of Parallel Programming – Lin & Snyder, 2008.

Patterns for Parallel Programming – Mattson, Sanders & Massengill, 2004.

The following paper is also a good overview of hardware and software issues:

The Landscape of Parallel Computing Research: A View from Berkeley – Asanovic et al, 18 Dec 2006.

My point here is this:  As a software developer, it’s critical that you start thinking about parallel computing–not just as some specialized set of techniques that you might use someday, but as one of the primary tools in your toolbox.

After all, today’s two-eyed baby will be sporting 16 eyes before we know it.  Are you ready to do some serious eye-poking?