Hans-Christian Andersen
hans.andersen at phulse.com
Sat Jan 14 05:49:14 CST 2012
A similar problem is the issue of the "quick fix". For a given task or problem, if you present a number of options along with the pros and cons, the client will almost always pick the option that takes the least amount of time. Unfortunately, those almost invariably always are unstable or unmaintainable. So, the next time you come across some code or database that looks to be in very bad condition, consider that it might not necessarily be a reflection of their poor abilities, but that the project suffered from a constant pressure to produce a quick fix. - Hans On 14 Jan 2012, at 01:55, "Gustav Brock" <gustav at cactus.dk> wrote: > Hi all > > But you really have to ask yourself if the output will be worth 60 times the effort? > > If the client asks for "bells and whistles as to your finest abilities" it's fine, but what if he asked for a clean basic design or even didn't ask for anything other than an unspecified clock? What would you as project manager tell the new guy on the team that thought this was the time for a show off? > > /gustav > >>>> steve at datamanagementsolutions.biz 14-01-2012 04:25 >>> > Yeah, thanks a million, Rocky. That video is so cool. > > Regards > Steve > > -----Original Message----- > From: Rocky Smolin > Sent: Saturday, January 14, 2012 1:56 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Friday sort of OT > > Send him this: > > http://tumblr.thedailywh.at/post/12760859047/more-time-is-more-money-of-the-day-to-prove-to > > If that fails then the old chestnut: > > http://mikelynchcartoons.blogspot.com/2010/02/you-want-it-when-poster.html > > Rocky > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Steele > Sent: Friday, January 13, 2012 4:45 PM > To: Access Developers discussion and problem solving > Subject: [AccessD] Friday sort of OT > > I spent nearly two hours yesterday with a client discussing future changes > to his database. The discussion went well, and I've probably got 20-30 > hours of work set up for the next month or so. I asked him to prioritize > the tasks we discussed, as he knows I have work to do for other clients. > Here is an abbreviated version of the email he sent me, with numbered tasks > and priorities: > > Task 1 'soon as possible' > Task 2 'soon as possible' > Task 3 'soon as possible' > Task 4 'next Friday' > Task 5 'soon as possible' > Task 6 'next Tuesday' > > Aren't clients fun! > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com