Coderific

rating for Softscape

1.0 Worst Place To Work posted on January 29, 2007

JWilliams may be one of the owners since the place he describes is not the place where I worked. Highest turnover of any company I've worked for.

See 17 more ratings for Softscape!

5 comments

Write a comment!
  • Re: Worst Place To Work posted on January 29, 2007 09:12 PM

    So you do not know if JWwilliams is one of the owners? Looks like Softscape is a very small company, so if you really worked there you would know.

    What about the other guy that liked working there? Completely different story to yours.

    I think an "owner" would be flamed pretty hard on this forum if he (and some other employee at the company) were making up their postings - others in their company would scream "murder". No?

    Your posting sounds suspicious.

    reply | quote

  • Re: Worst Place To Work posted on January 31, 2007 12:41 PM

    The owners have sued former employees. Your posting sounds like you are paid to promote them.

    reply | quote

  • Re: Worst Place To Work posted on February 01, 2007 07:07 PM

    You wrote: "The owners have sued former employees. Your posting sounds like you are paid to promote them."

    I have never heard of Softscape until you made your postings. I have never been in contact with anyone from that company (either current or past employees).

    Was it you that changed the company name of Softscape to Dorfmaster? Here is a forum post on this topic http://www.coderific.com/forums/posts/325?start=0. If it was you, this is a rather immature way to attack a company.

    As I said in my other posting on Softscape - if an employer posts 100% polarized views from your own, don't you think that other SoftScape employees will retaliate (especially the ones that you say are getting sued!!) if there is any truth to your allegations? Let's see if they do and you will be proven to have some grounds for your accusations.

    But, the other issues with your strong words in your postings (and possibly changing the company's name to Dorfmaster) are not the way to address your issues. You can have a better effect if your writing is calm and focused on facts and issues. It will help your fellow developers more, if you stay calm and write your issues accurately.

    Once again, ill behaved developers bring shame upon the entire industry. Please try to control yourself.

    reply | quote

  • Re: Worst Place To Work posted on February 02, 2007 11:27 AM

    If you search "Softscape +sued" on the Internet you will find that the earlier poster is not alone in his characterization.
    That said, I agree with you that his rebuttal was out of line.

    reply | quote

  • Re: Worst Place To Work posted by thehacker on February 05, 2007 06:36 PM

    JWilliams could be a pseudonym for one of the Watkins family members, or it could be the name of someone at Softscape who drank the kool-aid. There were a few of those (out of 100-150 people total) when I was there. The original poster's opinion matched my experience, so I'm inclined to believe his take on the company.

    There were people there who liked it. They were mostly kids right out of school and bad older programmers who didn't realize how dysfunctional and supoptimal Softscape's development practices were or didn't care, and yes-men who kissed ass and banged out crap. The intelligent, creative and talented engineers tended to leave as the job market improved. Demand for programmers was much worse in 2003 than it is today. This kept many people around during my time at Softscape.

    reply | quote

scores in this rating

development process

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

culture

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

compensation

salary unrated
health coverage unrated
paid time off unrated
snacks unrated
other perks unrated

organization

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

general

location unrated
nearby food unrated
business model unrated
cool technology unrated
vision and strategy unrated
warm fuzzy feeling unrated
overall 1.0

preferences

casual dress code unrated
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 unrated
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# unrated
use of Objective-C unrated
use of C unrated
use of C++ unrated
use of PHP unrated
use of ASP unrated
use of legacy languages unrated