Coderific

rating for Global Care Solutions

4.0 Freedom to influence product posted on December 19, 2006

Not sure what these other postings are all about, but as far as I am concerned it is a great place to work if you love 100% Microsoft technology. If you do not love Microsoft, or you have a secret desire for open source, this is not the place to be.

I get to write software and have direct input to product features. I find this the best part of the job. Usually, in most companies, the developer does not get to influence product. At GCS we are encouraged to add our ideas. In fact, the bosses are always saying that we need to do our own research on the business side of the applications so we can influence the product more. Often told "buy books on your subject - we will pay, no problem" adn other messages like thihs.

We just moved to Visual Studio 2005 and .Net 2.0. So we moved a little late (about 1 year late), but with this big of a system (and it is really huge), it takes a lot of planning and tools to make it easy to move. VS 2005 has really improved productivity. GCS has built a lot of it's own internal tools as well, so we have a lot of automation in the development process. I have never seen a company invest so much in tools and process.

I saw a comment on high turnover. Not sure what company they work in, as I have only seen 1 junior programmer leave in 2 years here.

If I had my wishes to change the company?
- Better specifications. Sometimes we do not have the spec nailed down, so we have to change code along the way.
- More developers! There is a lot of great ideas in the company, and not enough developers to code them.

Everyone has an opinion.

See 11 more ratings for Global Care Solutions!

1 comment

Write a comment!
scores in this rating

development process

clear requirements 2.0
design and planning 3.0
quality assurance 2.0
automated testing 1.0
peer review 2.0
development environment 4.0
development hardware 4.0
physical workspace 4.0
infrastructure and support 4.0
issue tracking 4.0
source control 4.0
product quality 3.0

culture

cultivation of creativity 4.0
mitigation of risk 3.0
reasonable workload 3.0
prevention of crunch time 3.0
hitting deadlines 1.0
taking responsibility 3.0
development autonomy 3.0
keeping ego in check 2.0

compensation

salary 4.0
health coverage 4.0
paid time off 3.0
snacks 2.0
other perks 3.0

organization

advancement opportunities 4.0
employee retention 4.0
hiring process 1.0
quality of development management 2.0
quality of upper management 4.0
quality of developers 4.0
team-to-team communication 2.0
internal team communication 2.0
management-developer communication 2.0

general

location 4.0
nearby food 4.0
business model 3.0
cool technology 4.0
vision and strategy 3.0
warm fuzzy feeling 3.0
overall 4.0

preferences

casual dress code 4.0
use of Free Software unrated
development of Free Software unrated
use of GNU/Linux unrated
use of Mac OS unrated
use of Solaris unrated
use of Windows 4.0
use of BSD unrated
use of Python unrated
use of Perl unrated
use of Ruby unrated
use of Lisp unrated
use of Java unrated
use of C# 4.0
use of Objective-C unrated
use of C unrated
use of C++ 4.0
use of PHP unrated
use of ASP unrated
use of legacy languages unrated