Stephen Russell wrote: > On Wed, Jul 15, 2009 at 6:49 PM, Gene Wirchenko<[email protected]> wrote: > >> Did we say forever? It has not really been >> that long. I just recently was modifying some >> VFP procedures that I had not changed in just >> over ten years. Ten years really is not that long. >> > ------------ > > Ten years in tech time is a very very long time. Ten years in > geologic time is infinitesimally small. We are talking Tech here > right? > Wrong! We are talking people here. We are talking about amortizing your time/money/effort/strain in learning how some software works best for you or your customers. I don't give a rat's ass about tech time, I pay them to provide solutions not problems (just like my customers pay for my solutions and don't want to hear about my problems or my need to deliver something "new" to get some money out of their pockets).
> Who the F said I was embracing change? What I am writing about is the > fact that as professional programmers many here find it distasteful > when the #1 vendor introduces an upgrade to an existing product. > > If you were a professional you would determine if that might impact > your product(s). If it does you then decide if you are going to adapt > or not. > And once you decide it impacts in a bad way, and the "#1 vendor" does everything in his hand to not give you a choice, then you start looking for ways to dump "#1 vendor" and use better solutions. Sooner or later "#1 vendor" will go down. > To the contrary I find many on this list just piss and whine about the > changes. > > Why do you not see this as a perfect REASON to contact former clients > and tell them that everything is fine with the old SW you made for > them, and is there anything else I can do for you? Or you can bring > up the fact that the mail merge or the saving in a .dbf is no longer > supported in the new version. You customer have two options now. > Don't upgrade the Office version or let's talk about a change to your > software when you do in the future. > > M$ in this case is opening up door for communication for you. Why is > your first remark "Close that door! Were you raised in a barn?" > So now MShit runs my business and "helps" me contact my customers? How nice of them, I could never decide by myself when to do that. What about if I give them my bank's password and they start managing my money? That would be nice. >> Microsoft breaks our code, and you are OK with that? >> > ----------------------- > > I find it a PITA to test. I then realize that a customer from 2002 > may need something else but I have not called them, because they > should call me. > So your point is that we should stand MShit's practices just because you are a lousy businessman? >> As a professional, I feel an obligation to not drink the Kool-Aid. >> > ---------------------- > > hahahahaha I love the statements from the true consultant. I refuse > to identify anything outside of my direct needs. The rest is futile. > > Once again Stephen, we are in the business of providing business solutions. Maybe you'd be happier as a hair dresser or a fashion designer. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
