Andrew Pollack's Blog

Technology, Family, Entertainment, Politics, and Random Noise

How much investment do you make in your clients....when they'll never know?

By Andrew Pollack on 03/04/2005 at 10:09 PM EST

Its Friday night, and I'm waiting for Battlestar Galactica to start on SciFi (we already know I'm a geek) and trying to come up with something interesting that's not too contrived to put on this blog. After all, you people have been patiently reading through boring stories of my car burning and pictures of my kids -- and really, only my mother is interested in seeing those on the blogsite -- so I suppose I should throw something out here that has the markings of being business related.

I have a client (hard as that is to believe for some of you), and like many of my clients, they're a marketing oriented bunch. For obvious reasons I won't say who they are, but I will make clear they're a NEW client, not the one you all are already thinking of. Anyway, they had me build a "one-off" site to collect data from a targeted group of people. Now they want to use that data more fully and grow it into slightly more of a fixture in their plans. I'm in the same place I was around ten years ago with another system -- one that I'm still managing to this day. It is completely clear to me that unless we build something designed to handle a kind of data that so far doesn't exist -- then each and every thing I do for them is ultimately going to be tossed away for each next thing. Ultimately, all the power and utility of the platform I use that routinely allows me to underbid by as much as two decimal places will end up not saving anything.

Here's the dilemma -- I know that they're going to grow this into a cornerstone of what will become a fairly important "extranet". This basic "one-off" which was never meant to house any permanent data will frankly never be good in the role of keystone. At the same time, the client has an I.T. department who is working on a "Grand Project" to produce the kind of data management system needed for this kind of data and as long as that's ongoing, I'm never going to convince them that's its worth spending money on a concurrent effort even if its just designed to hold data that it will ultimately not own.

Even though they don't have a data structure designed yet for their big relational database, on the Domino side all I need to know are the kinds of "entity objects" I'm likely to be getting from them when they finally get it done. For this kind of site, that's easy. Its predictable at the macro level even if I have no idea what field names and values I'm ultimately going to be asked to bring over from the as yet unbuilt data store. BUT -- there's no way they'll pay me to build a repository they don't yet need.

If its you, do you spend about twice the effort you need to on these small efforts -- essentially doing work you're not getting paid for -- to build them with way more planning and organization than they would need if they were in fact never going to be more than short term tools? Do you build just what you need to for each task, but then never grow the system out to what it can be because ultimately there won't be any cost savings visible at the medium term?

I'm leaning toward taking the risk, spending the extra time, and over-building the initial pieces at a loss; with the goal of ending up with something compelling enough to be looking back on it 10 years from now and showing another junior admin how it all got started. Can you do that twice in a row, or am I better off just taking the quick hit little jobs and letting the rest of it die of its own foolishness?


There are  - loading -  comments....

My own thoughts on this are...By Ben Langhinrichs on 03/05/2005 at 07:25 AM EST
I think it is worth the risk. Part of the reason you are still at the other
client all these years later is you are not just a hired hand doing what you
are told. You have some vision, and can lead them forward. Not all clients
will take it well, even if you are looking out for them, but it is what sets
you apart and makes it less likely that the next "one-off" will be built in
Agreed,..By ajp on 03/05/2005 at 08:34 AM EST
...but by Murphys/Sods* law if take the risk the work will be wasted, if you
don't take the risk you'll regret it later.

* Murphys (US) = Sods (UK)
Domino is less susciptible to "second system syndrome"By Richard Schwartz on 03/07/2005 at 09:10 AM EST
Interesting business question here. My instinct is to say that on the first
few pieces of this, it would be a good idea to start building the framework
they're going to really need. An approach I might take -- and I know you're
very familiar with it -- is to build the storage in a quick-and-dirty fashion,
allowing you to get prototypes done for the customer quickly in the early
stages, but to also design and build an object structure that anticipates the
direction that you know things will have to go if the project progresses. You
only need to implement the parts of the object structure that you need now, but
you plan the interfaces for what you will need. That way you strictly contain
the need to re-work that lies ahead, but you don't do a lot of unpaid work and
you don't lose the ability to get things done very quickly in the early stages.

As for the title I put on this response, I'm referring to a tendency amongst
all of us in the software business to over-reach when building again something
that we've built before. Not sure who invented the term "second system
syndrome" (probably Fred Brooks if I had to guess), but it goes way, way back.
I remember hearing it when I was in college. Trying to apply _all_ the lessons
learned the first time can cause the second implementation to get totally
bogged down. I know this syndrome very well myself, having had to reassess and
drastically simplify several projects in the early years of my career as a
result of it. I can't say that this has never happened in more recent years,
but what I can say is that with Notes and Domino I've been much better at
anticipating the fact that it might happen and designing structures that make
it much easier to recognize when it is happening and to back down without
having to rewrite things from scratch. I think that designing objects from the
beginning, but doing RAD for each implementation (and re-implementation) is
exactly the right combination, and Domino is really good at encouraging exactly
that style of development.


Other Recent Stories...

  1. 01/28/2020Copyright Troll WarningThere's a copyright troll firm that has automated reverse-image searches and goes around looking for any posted images that they can make a quick copyright claim on. This is not quite a scam because it's technically legal, but it's run very much like a scam. This company works with a few "clients" that have vast repositories of copyrighted images. The trolls do a reverse web search on those images looking for hits. When they find one on a site that looks like someone they can scare, they work it like ...... 
  2. 03/26/2019Undestanding how OAUTH scopes will bring the concept of APPS to your Domino serverWhile a full description of OATH is way beyond what I can do in this quick blog entry, I wanted to talk a bit about how "SCOPES" interact with the already rich authorization model used by Domino. Thanks to the fantastic work by John Curtis and his team, the node.js integration with Domino is going to be getting a rich security model. What we know is that a user's authorizations will be respected through the node.js application to the Domino server -- including reader names, ACLs, Roles, and so on. The way ...... 
  3. 02/05/2019Toro Yard Equipment - Not really a premium brand as far as I am concernedDear Toro Customer Service, I arm writing about the following machine: Toro Power Max 1120 OXEModel:38654S/N:31000#### Specifically, bearing part #:63-3450 This is the part ($15 online / $25 at the local dealer) that caused me to raise my objections on-line. This piece of garbage is supposed to be a bearing. It carries the shaft which drives both stages of the auger. The shaft passes through the bearing (which is what bearings do) after the auger drive pulley as the shaft goes through the back (engine ...... 
  4. 10/08/2018Will you be at the NYC Launch Event for HCL Domino v10 -- Find me! 
  5. 09/04/2018With two big projects on hold, I suddenly find myself very available for new short and long term projects.  
  6. 07/13/2018Who is HCL and why is it a good thing that they are now the ones behind Notes and Domino? 
  7. 03/21/2018Domino Apps on IOS is a Game Changer. Quit holding back. 
  8. 02/15/2018Andrew’s Proposed Gun Laws 
  9. 05/05/2016Is the growing social-sourced economy the modern back door into socialism? 
  10. 04/20/2016Want to be whitelisted? Here are some sensible rules for web site advertising 
Click here for more articles.....

pen icon Comment Entry
Your Name
*Your Email
* Your email address is required, but not displayed.
Your thoughts....
Remember Me  

Please wait while your document is saved.