|
Nick Seng wrote:
I used to work for a Software House, and the culture here was more or less "one employee does all". We did everything from getting requirements from clients, showing product presentations, Systems setup, the whole she -bang. And oh yeah, ocassionaly Code.
I've had to do much the same for most of my working life. It is valuable experience, knowing that you can turn your hand to anything when the situation requires. Although I'd like to forget my brief stint as a trainer. Several care homer owners in a room, with me giving lectures on how to do various tasks on the computer system. It makes me cringe to think about it. Strutting around like a geography teacher. Gagh. Still I was only 19 and didn't know much better. Still it taught me patience, which is a very valuable trait when dealing directly with clients.
Michael
CP Blog [^]
|
|
|
|
|
But hopefully closer to Never real soon now. 
--
Weiter, weiter, ins verderben.
Wir müssen leben bis wir sterben.
|
|
|
|
|
I really should not have gone over there, but the boss asked me to, "just in case", so I went.
I got to the office at 08:30 this morning, I have not started to code yet and its 15:00...
I prefer to deal with machines, compilers and that sort of thing.
I sometime get "quiet" periods, where I only go once every few months to clients, now I am in a "rush" period, going almost weekly.
|
|
|
|
|
This year i got good employee certficate form my office. I felt so very happy. And i thought, that is the real satisfaction that what i got.
But this is nothing if we get a excellent feedback from client's who uses our software.
I realise this ultimate plessure and happiness when my client comment "Good Work Sreejith".
Sreejith Nair
[ My Articles ]
|
|
|
|
|
similar to what Marc mentions below, I have "internal" clients and "external" clients. from a development perspective, the internal clients use in-house proprietary tools that i develop. it's like a company within a company really. Now rarely in my line of work would I meet the external customer. Our requirements are usually something along the lines of: "here, make this fly." Oh, and: "here, make sure that if this breaks, it can still fly."
~Nitron.
ññòòïðïðB A
start
|
|
|
|
|
Same here. Currently, I support a tool I wrote that is used internally in several company locations. Much more satisfying than several previous jobs I had, where as a non-developer I got to go to customer sites and be the liason between irate customers and the developers "back-home" who got them that way 
|
|
|
|
|
I have to. I work for myself
When I was just a grunt programmer. I hated having to deal with clients.
Now I love it. It is the second favourite part of my job. It helps a great deal to get a feel for business you are creating a solution for. Both the senior people and the ones who will actually work with my software.
It certainly builds up your communication skills and I've found it has helped me build better software.
Michael
CP Blog [^]
|
|
|
|
|
Yes all the time. Although I do not work for myself, I´m the only PC developer in the company(the others are all embedded), and I have to do all the coaching and training for our systems and the software.(being a native English speaker is is an advantage)I think it´s great, the best of both worlds, lots of traveling AND hacking/developing away. I can only agree that it builds up your communictaion skills, and you get a better "feeling" while developing the software for what the customer actually needs/wants.
bum... and I thought I´d got rid of all the bugs 
|
|
|
|
|
If you think about it, anyone who asks you for something, or to whom you've promised something to, is your client. Your coworker, your boss, etc. Clients aren't just the people at the end of the food chain (or the beginning, depending on your perspective).
This is something that TQM (Total Quality Management) teaches, and even though TQM has been slammed a lot, when I worked as an employee I found it really helpful to view the people that I work with as clients. And it's a two way street too--I am somebody else's client.
It helps you to communicate expectations and implementation plans, to document (horrors!) and more formalize communication, and in general to be more professional with regards to how you communicate with your coworkers.
Marc
MyXaml
Advanced Unit Testing
|
|
|
|
|
Agreed. I build a lot of internal stuff for our company. We are a service company (healthcare), but my function is for supporting the company, not necessarily the service part of it. Most of the time, I meet with those who deal with medical professionals outside of our company, and a few times a year, I meet with them as well. So in my view, not only are patients a client, but so is the staff at hospitals and clinics. One could argue about whether or not the people in the business office, marketing, accounting or chiefs in your company are your customers, but they are often your intended recipient of your work.
Visit http://www.outsourceapro.com and find out about becoming a developer in one of our development teams for some of our future consulting projects.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
