The danger of doing too much

Freshness Warning
This blog post is over 15 years old. It's possible that the information you read below isn't current and the links no longer work.

Deane asked his readers how to provide clients with an easy way to update a small portion of a static site. His particular example is a company who keeps adding and removing locations from their "Where to Buy" list. Apparently he’s got a lot of sites that need some sort of simple updates but don’t warrant a lot of custom programming because he’s toying with the idea of building a application framework that would let him handle these mini apps easily and asks his readers for ideas.

One person suggests using Wordpress or another lightweight CMS to manage these pages. Deane responds

This is great for things that fit that data model, but what about things that don’t? What if they want to maintain a list of Supreme Court cases, complete with about 10 extra fields of data.

I suggest Deane would probably want to start looking at a custom web app at that point. The stated goal of the framework is to allow a simple customer-editable section without requiring lots of custom programming. The list of Supreme Court cases sounds more complex than that.

Developers run the risk of doing too much when they spec an application. They start looking at all the possible edge cases for their app and trying to incorporate them. This leads to a sort of analysis paralysis where the design becomes so complicated that nothing gets built.

Start simple. Look at the problem you have and solve it. Don’t start thinking about how this isn’t going to solve X or Y. Solve one problem and iterate. Another case comes up that doesn’t fit in? Iterate. Design your framework to be flexible enough to handle iterations, but don’t over-design. You’ll never get anything done that way.

Be simple.

And for Deane’s original problem of letting a customer update a list of locations without requireing lots of validation routines and such, I’d suggest something simple. Give them a text field that overwrites a file. The web page reads that file and displays it. Perhaps add Markdown or Textile processing to the file if they want fancy formatting options. Five minutes of programming work and the customer’s happy.

December 15, 2005 11:12 AM

Providing the Supreme Court example was a huge generalization. As the rules I stated in the post indicate, I'm talking about a single table of data -- one table, a set number of columns, a bunch of rows -- with CRUD functionality. Could you do a simple table like this to list Supreme Court rulings on a particular topic? Absolutely -- a potential client actually asked me for this once, and I mapped it out on a napkin. But you pick your data. Let's go back to the "locations" example -- I'm very partial to a generalized app with SQLite as a backend, so it's all self-contained. (And, dude, when you put two n's in my name, I become a woman. "Dee-anne.")

Timothy Appnel
December 15, 2005 2:12 PM

Agreed. Throw Xinha[1] in with that text field that overwrites a file and your set. [1]

This discussion has been closed.

Recently Written

The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2021 Adam Kalsey.