Stephen Russell wrote: > I have to chuckle here. You wrote code against a set of APIs. > There is a new version of them. > > You expect that there could / will be some change. > > What planet do live on to think that you are not going to get stung? > I don't care if it is a change in java from Sun / IBM or Office from > M$. Change is going to keep us in this cycle. > Maybe I'm spoiled, I'm used to xml, sql, html, etc not changing significantly. I don't object to "some" changes, but if you have to re-learn a tool every four years then it's not my glass of wine. Of course I live in the real world, and many a time I don't have a choice (that's why I complain every now and then). But whenever I have one, I vote with my feet.
> None the less the residents of Rome had to live after the flames were > extinguished. You mean after MShit has fallen? I'll live in Greece... sorry LinuxLand > So what are you going to do for your existing clients? > Tell them to piss off? I don't see how many people here are afraid to > communicate to clients in the past about changes. The point is that I want to decide when to communicate with my clients. I don't want MShit to manage my business. > In customer relations WE should contact the customer not them calling > in about your app no longer working.... only to find that they > upgraded to Office 2007 early this year. > > What M$ does for your business cycle is remind you that it is a cycle > and not a Gannt chart with starting and stopping points. > Shush! Come to think of it I should send them a thank you note. It's so nice of them to tell me how to run my business. > I am looking at getting back into code for one small group here in > town if they like me. I have to PM and design WS for portability of > the product to other new clients. Right now they are tightly bound to > their current client and tey are getting ready to expand to others. > It all deals with the DAL and how the data is pretty close to home > grown for many potential new clients. It deals with document > management and workflows. > ICBUATFA (I can't bloody understand all those fucking acronyms). DKWYTA (Don't know what you're talking about). _______________________________________________ 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.
