5 ms·

If a developer was asking questions this granular in an interview I'd be very concerned that they're really focused on the wrong things for growth as a person a

by weego 4y ago

If a developer was asking questions this granular in an interview I'd be very concerned that they're really focused on the wrong things for growth as a person and employee. 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.

ethbr0 4y ago
> If what source control or oss libs we use are a dealbreaker Have you ever worked at a TFS shop?
- MarcellusDrum 4y ago
  I currently do. It's not perfect, but honestly, I don't understand the hate.
  - glitchc 4y ago
    Wait till you have to deal with a merge conflict.
- bbarn 4y ago
  Ah, VSS and SVN's bastard love child. Don't miss that.
- peteri 4y ago
  Depends on the version to be honest. 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.
bartvk 4y ago
> If what source control or oss libs we use are a dealbreaker then you're a problem waiting to happen. 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.
gjulianm 4y ago
This is a fairly limited point of view. For starters, you need to realize that the candidate is probably interviewing for more companies and having more offers. If the offers are similar enough, I might end up making a decision based on which source control you use or on whether you use libraries I don't like or not. 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.

by weego 4y ago

ethbr0 4y ago

> If what source control or oss libs we use are a dealbreaker Have you ever worked at a TFS shop?

MarcellusDrum 4y ago
I currently do. It's not perfect, but honestly, I don't understand the hate.
- glitchc 4y ago
  Wait till you have to deal with a merge conflict.
bbarn 4y ago
Ah, VSS and SVN's bastard love child. Don't miss that.
peteri 4y ago
Depends on the version to be honest. 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.

bartvk 4y ago

> If what source control or oss libs we use are a dealbreaker then you're a problem waiting to happen. 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.

gjulianm 4y ago

This is a fairly limited point of view. For starters, you need to realize that the candidate is probably interviewing for more companies and having more offers. If the offers are similar enough, I might end up making a decision based on which source control you use or on whether you use libraries I don't like or not. 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.