![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Paul Bruneau <paul (AT) ethicalpaul (DOT) com> wrote: We'd really like to copy and paste script steps too! I mean it. We REALLY want this. No, *YOU* really want this. You don't want to be able to copy and paste script steps, Lynn??? Sure, that would be great, but I don't want it near as much as I want other features. It's way down the list for me. Everyone's priority list is different. Everyone's productivity-killers are different. I think was my point. |
(
#12
| |||
| |||
|
|
In article <1gyx1gr.1vpyn9q1kj5400N%lynn (AT) NOT-semiotics (DOT) com>, lynn (AT) NOT-semiotics (DOT) com (Lynn allen) wrote: Paul Bruneau <paul (AT) ethicalpaul (DOT) com> wrote: We'd really like to copy and paste script steps too! I mean it. We REALLY want this. No, *YOU* really want this. You don't want to be able to copy and paste script steps, Lynn??? Sure, that would be great, but I don't want it near as much as I want other features. It's way down the list for me. Everyone's priority list is different. Everyone's productivity-killers are different. I think was my point. My only "productivity killer" is when the fool the database is being created for keeps changing their mind what they actually want. ( |
(and
#13
| |||
| |||
|
|
My only "productivity killer" is when the fool the database is being created for keeps changing their mind what they actually want. ( |

#14
| |||
| |||
|
|
In article <300620050848275994%helpful_harry (AT) nom (DOT) de.plume.com>, helpful_harry (AT) nom (DOT) de.plume.com says... In article <1gyx1gr.1vpyn9q1kj5400N%lynn (AT) NOT-semiotics (DOT) com>, lynn (AT) NOT-semiotics (DOT) com (Lynn allen) wrote: Paul Bruneau <paul (AT) ethicalpaul (DOT) com> wrote: We'd really like to copy and paste script steps too! I mean it. We REALLY want this. No, *YOU* really want this. You don't want to be able to copy and paste script steps, Lynn??? Sure, that would be great, but I don't want it near as much as I want other features. It's way down the list for me. Everyone's priority list is different. Everyone's productivity-killers are different. I think was my point. My only "productivity killer" is when the fool the database is being created for keeps changing their mind what they actually want. (Ah... so the feature you most want in FM8 is new customers (andbetter ones too) |
)
#15
| |||
| |||
|
|
In article <1gyx1gr.1vpyn9q1kj5400N%lynn (AT) NOT-semiotics (DOT) com>, lynn (AT) NOT-semiotics (DOT) com (Lynn allen) wrote: Paul Bruneau <paul (AT) ethicalpaul (DOT) com> wrote: We'd really like to copy and paste script steps too! I mean it. We REALLY want this. No, *YOU* really want this. You don't want to be able to copy and paste script steps, Lynn??? Sure, that would be great, but I don't want it near as much as I want other features. It's way down the list for me. Everyone's priority list is different. Everyone's productivity-killers are different. I think was my point. My only "productivity killer" is when the fool the database is being created for keeps changing their mind what they actually want. (Helpful Harry Hopefully helping harassed humans happily handle handiwork hardships ;o) Isn't this about the fact that you didn't listen adequately in the first |
#16
| |||
| |||
|
|
Helpful Harry wrote: In article <1gyx1gr.1vpyn9q1kj5400N%lynn (AT) NOT-semiotics (DOT) com>, lynn (AT) NOT-semiotics (DOT) com (Lynn allen) wrote: Paul Bruneau <paul (AT) ethicalpaul (DOT) com> wrote: We'd really like to copy and paste script steps too! I mean it. We REALLY want this. No, *YOU* really want this. You don't want to be able to copy and paste script steps, Lynn??? Sure, that would be great, but I don't want it near as much as I want other features. It's way down the list for me. Everyone's priority list is different. Everyone's productivity-killers are different. I think was my point. My only "productivity killer" is when the fool the database is being created for keeps changing their mind what they actually want. (Isn't this about the fact that you didn't listen adequately in the first place? |
\
#17
| |||
| |||
|
|
My only "productivity killer" is when the fool the database is being created for keeps changing their mind what they actually want. (Isn't this about the fact that you didn't listen adequately in the first place? |
|
Nope. It's that they don't know what they want, they just want a database to do it because it looks good on the business plan ... or they want a database to do this and then realise that it would be better to do that instead or as well ... or they INSIST on the database working "this" slow and awkward way when I know it would suit them better to do it another way ... or ... But it's up to them. They're paying for it (sort of) and I just havce to waste the hours making it only to have to remove it later. |

#18
| |||
| |||
|
|
Nope. It's that they don't know what they want, they just want a database to do it because it looks good on the business plan ... or they want a database to do this and then realise that it would be better to do that instead or as well ... or they INSIST on the database working "this" slow and awkward way when I know it would suit them better to do it another way ... or ... But it's up to them. They're paying for it (sort of) and I just havce to waste the hours making it only to have to remove it later. Management - who needs 'em? \Helpful Harry Hopefully helping harassed humans happily handle handiwork hardships ;o) |
#19
| |||
| |||
|
|
Helpful Harry <helpful_harry (AT) nom (DOT) de.plume.com> wrote: My only "productivity killer" is when the fool the database is being created for keeps changing their mind what they actually want. (Isn't this about the fact that you didn't listen adequately in the first place? In Harry's defense, plenty of clients behave the way he describes. They literally do NOT know what they want when they start out. It can be because they don't have a good grasp of their own business processes, so they can't adequately describe the business rules that need to be embodied in the software. Or they don't have the right people involved in the project. The managers who are providing the specs are out of touch with the little people who do the work ("oh, we haven't done it that way in years, it didn't work. Now we do it *this* way") Or maybe the client thinks they only need a small part of their business managed by the software, only to find out that in order to DO that one part, several other areas are affected and must also be accommodated in order to make it work. I've encounted all of these and more. The most frequent symptom of this is that during design review, the client says.."that's not what I meant (or wanted). I want *THIS*." Nope. It's that they don't know what they want, they just want a database to do it because it looks good on the business plan ... or they want a database to do this and then realise that it would be better to do that instead or as well ... or they INSIST on the database working "this" slow and awkward way when I know it would suit them better to do it another way ... or ... But it's up to them. They're paying for it (sort of) and I just havce to waste the hours making it only to have to remove it later. Harry, as you get more experienced (not that you aren't already) and have a more reliable income stream, it gets a bit easier not to allow clients to wander where they ought not. I've told clients that I *won't* do certain things they thought they wanted, either because doing them would unfavorably impact performance, data integrity, or user experience, or because it would be a waste of their money. Of course, if I wanted to keep said clients, I've done it in a very tactful way, and backed everything up with reasoned arguments. I find the bottom line to be the reason that carries the most weight. ![]() I've also fired clients, for various reasons, including but not limited to slow pay, refusal to invest (the "let's just spend pennies on patching ill-designed and unstable files instead of rebuilding as would be proper" approach), and being difficult to work with or impossible to please. Inviting a client out the door can be a liberating experience, and at least in my market, there's no shortage of work. Last week alone I got three new business calls I had to refer out. Don't blame Harry for the shortcomings of clients. We've all had 'em. If ANYONE has a client who can describe perfectly, the first time, exactly what they want and then recognize that *that's* what they got when you it's delivered, I challenge you to produce them! Lynn Allen -- Allen & Allen Semiotics www.semiotics.com FSA Associate Filemaker Design & Consulting Hi Lynn, |
#20
| |||
| |||
|
|
Hi Lynn, Sorry to sound like I was having a go at Harry. I could sense the frustration he fells and it was that that I was trying to suggest and alternative. Who needs angst in their life when with the right tool and a bit of time it can be avoided? |
)![]() |
| Thread Tools | |
| Display Modes | |
| |