100 reputation
2
bio website google.com
location Pennsylvania
age 38
visits member for 4 years
seen Jul 2 '13 at 18:50

Sep
29
comment When deciding on whether or not to work for a new company, what are your dealbreakers?
@Aaron - if you came on my team and decided to run your own source code control, you'd be gone pretty quickly. It's simply not possible to efficiently run a large project when everyone is using incompatible tools. Different, but compatible, tools is often fine ... but expecting a .NET development team invested in Visual Studio that you want to do all of your development on a Linux machine with Mono is a sure way to get canned.
Sep
28
awarded  Supporter
Sep
28
comment When deciding on whether or not to work for a new company, what are your dealbreakers?
@JuanZe - Development shops, maybe, but if you're going to be a developer at a corporation then I've only seen cubes.
Sep
28
comment When deciding on whether or not to work for a new company, what are your dealbreakers?
How many developer environments are NOT cubicles?
Sep
28
comment When deciding on whether or not to work for a new company, what are your dealbreakers?
For a large company, it's takes a lot of momentum to deviate from a certain path. Many large companies get products like VSS basically for free, so there's no reason for them not to use it.
Sep
28
comment When deciding on whether or not to work for a new company, what are your dealbreakers?
"I have to work with the provided tools" - some of that you cannot get away from. If a company is using Subversion for source code control, you have to use Subversion. If they want you to use Emacs instead of vi (or vice versa), then there's a problem.
Sep
28
awarded  Critic
Sep
28
comment When deciding on whether or not to work for a new company, what are your dealbreakers?
But at the same time, if someone is in the office for 8 hours and only working 3 of them, that person is under-productive.