Ask dealbreaker questions in interviews. If what source control or oss libs we use are a dealbreaker then you're a problem waiting to happen.
Ask dealbreaker questions in interviews. If what source control or oss libs we use are a dealbreaker then you're a problem waiting to happen.
But also, those questions are very useful to know what working for the company might be like. For example, my perception of the company depending on some answers:
- You don't use source control: the company doesn't really care about the development process. Very likely to be missing other development tools, and my job is going to be harder than it needs to be.
- You use Subversion: A signal that the company might be stagnated on legacy practices, systems and tools.
- You don't use OSS libs: the company tends to reinvent the wheel. Unless there's a good reason, looks like I am going to fight internal teams for getting standard features to the shared libraries, and my job is going to be harder because it looks like the process to get already-written code onto the company codebase is hard or even impossible.
Those signals are going to go into my decision process. Maybe not a dealbreaker, but might make a difference when comparing to other offers.
And yes, when people have asked me those things, I've been happy to respond. In fact, it shows me that they know what they want and probably have experience in those tools and the advantages/drawbacks of each approach.
Please reconsider this point of view, and here's why. I've actually asked this question :)
The reason is, that the company was huge but not in IT. I wanted to know if they actually used source control. Turns out, another team used TFS, but this one didn't. That was useful information.
Have you ever worked at a TFS shop?
The newer ADO with git as the source control is fine with me but I suspect if the company started with some of the early scrum templates and rolled forward it could be a complete horror show.
I wouldn't use it for Linux kernel development, but for a general .net shop it's what I would expect to see. I don't really interact enough with Jira to have a solid opinion.
I think the 2005 version source control was awful though, it got better and these days I'd hope everyone was using git.