Service or Product?
-
Which industry would you like to work in and why?
-
Which industry would you like to work in and why?
obviously product based Vishal Swarnkar
-
obviously product based Vishal Swarnkar
Obviously? Why? regards, Paul Watson Ireland Feed Henry!
eh, stop bugging me about it, give it a couple of days, see what happens.
-
Which industry would you like to work in and why?
I have never worked for a service based company so I don't have any idea about it. I have worked form my current company for 7 years and have worked with 4 versions of the software and now I am working on a major version. The problem is that now I don't have exposure to other areas(software is for cost accounting). For that reason I will like to work for a consulting company.
-
Which industry would you like to work in and why?
I've worked in both service and product-based companies and found that each has their own merits. Working on a product can give you a real sense of pride for what you have created, especially when it is advertised in magazines, etc. Having a product that you work on for the long haul allows you to become a real expert in how it works, which is also great. The downside is that you end up doing a lot of maintenance work, instead of writing completely new code. Working in a service-based company does not usually provide that same sense of "ownership" over the code bases with which you work. It does, however, give you the opportunity to work in many environments, on many types of new applications, with different people, and in different problem domains. That can be very exciting and keeps you on your toes. I don't think that one is inherently better than the other. What really matters to me is that I work with quality developers who I can learn from, in my preferred language. Josh
-
obviously product based Vishal Swarnkar
In you view what is the difference between Service and Product? ... give us some examples if you can.
-
I've worked in both service and product-based companies and found that each has their own merits. Working on a product can give you a real sense of pride for what you have created, especially when it is advertised in magazines, etc. Having a product that you work on for the long haul allows you to become a real expert in how it works, which is also great. The downside is that you end up doing a lot of maintenance work, instead of writing completely new code. Working in a service-based company does not usually provide that same sense of "ownership" over the code bases with which you work. It does, however, give you the opportunity to work in many environments, on many types of new applications, with different people, and in different problem domains. That can be very exciting and keeps you on your toes. I don't think that one is inherently better than the other. What really matters to me is that I work with quality developers who I can learn from, in my preferred language. Josh
hmm...so if I develop a full blown enterprise level website does that mean I developed a product?
-
hmm...so if I develop a full blown enterprise level website does that mean I developed a product?
It depends on how the company makes money from it. If they sell access rights to the site, then yes. If it is used for attracting potential customers and providing services to existing customers, but access to the site is free, then no. That raises an interesting point. I guess there is a gray area - the IT worker. The IT worker might be a full-time employee who works on internal systems (which are not products) but also sticks around to maintain it. Josh
-
Obviously? Why? regards, Paul Watson Ireland Feed Henry!
eh, stop bugging me about it, give it a couple of days, see what happens.
Paul Watson wrote:
Obviously? Why?
Obviously, I would say it was his obvious use of the word obvious. Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash 24/04/2004
-
Paul Watson wrote:
Obviously? Why?
Obviously, I would say it was his obvious use of the word obvious. Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash 24/04/2004
:lmao: :rolleyes: I did ask for that one didn't I? regards, Paul Watson Ireland Feed Henry!
eh, stop bugging me about it, give it a couple of days, see what happens.
-
Which industry would you like to work in and why?
Product. I worked at a food manufacturing facility for almost 13 years, then for a consulting company at a paper manufucturing facility for the last 7 years (switched from contract to permanent March 1). In both instances, it was the feeling of being able to actually hold something in my hand and say, "I helped make this happen..."
-
Which industry would you like to work in and why?
Neither, I would like to invent some "new great thing" and sell it off and live off the royalties (and require the buyer to assume all responsibilty). If you work in products, you can have your product sued out from under you by someone claiming their patient of all knowledge applies to your product and you must license it from them. If it is services, there is always someone willing to work for less unless it is not enough to survive. In either camp, you will always find someone who will provide the product or service cheaper or better and will always live in a battle. This is why, you must work at something you are passionate about and does not matter if someone else takes if from you, the satification is enough for you. You may become wealthy and live a good long life enjoying it, but regardless of what happens, you will still be happy. Rocky <>< Latest Post: SQL2005 Server Managemnet Studio timeouts! Blog: www.RockyMoore.com/TheCoder/[^]