7 ms·

That's an odd one to cherry pick. There's nothing performative about source control. It's one of the most important tools for actually shipping software.

woutr_be 4y ago
I was going to say; I would ask this, as a lead up to CI/CD, and how they feel about developers shipping features continuously, or if there’s any process to actually ship what I’ve build.
technion 4y ago
I can see the concern though. If you say something like "we invested in a large workflow involving Gitlab/Gerrit/anything else" and a potential applicant without any context expects you to go on the defense about why you aren't just using Github, I can see that person being hard to work with. I'm particularly noting the "and why" part here.
- ryanbrunner 4y ago
  The problem isn't the question there though, the problem is an invented scenario that happens due to the response. The followup to that response could easily also be "Oh cool, how does that workflow work? Why did you go in that direction? What do you want to improve about it?"
skrebbel 4y ago
The performative part is engaging in endless discussions and iterations about internal tooling
- chrisseaton 4y ago
  > endless discussions and iterations about internal tooling They just asked a simple question. It's a one-to-three-word answer. 'GitHub', 'Gitlab', 'BitBucket', 'Self-hosted CVS'. They wanted information, not to start a fight like you thought.
  - skrebbel 4y ago
    I said "a series of questions akin to", not "this single question". Please don't take my words out of context. My comment isn't about source control. It's about warning applicants not to over-obsess about technical details when other stuff influences job happiness much more than git vs mercurial.
  - Anon1096 4y ago
    I think "what source control tool do you use" is fine, it's the "and why" where I start to think that you're asking the question to be combatative. I agree if you're expecting a couple word answer like Github etc, then perfectly good question to ask.
    - ryathal 4y ago
      The why can be really important though. We do X because Google does it, or something like that is often a red flag because they have some insanely convoluted process that they don't need. knowing that things are selected that fit the size and scale of where a company is or will be soon is important.

woutr_be 4y ago

I was going to say; I would ask this, as a lead up to CI/CD, and how they feel about developers shipping features continuously, or if there’s any process to actually ship what I’ve build.

technion 4y ago

I can see the concern though. If you say something like "we invested in a large workflow involving Gitlab/Gerrit/anything else" and a potential applicant without any context expects you to go on the defense about why you aren't just using Github, I can see that person being hard to work with. I'm particularly noting the "and why" part here.

ryanbrunner 4y ago
The problem isn't the question there though, the problem is an invented scenario that happens due to the response. The followup to that response could easily also be "Oh cool, how does that workflow work? Why did you go in that direction? What do you want to improve about it?"

skrebbel 4y ago

The performative part is engaging in endless discussions and iterations about internal tooling

chrisseaton 4y ago
> endless discussions and iterations about internal tooling They just asked a simple question. It's a one-to-three-word answer. 'GitHub', 'Gitlab', 'BitBucket', 'Self-hosted CVS'. They wanted information, not to start a fight like you thought.
- skrebbel 4y ago
  I said "a series of questions akin to", not "this single question". Please don't take my words out of context. My comment isn't about source control. It's about warning applicants not to over-obsess about technical details when other stuff influences job happiness much more than git vs mercurial.
- Anon1096 4y ago
  I think "what source control tool do you use" is fine, it's the "and why" where I start to think that you're asking the question to be combatative. I agree if you're expecting a couple word answer like Github etc, then perfectly good question to ask.
  - ryathal 4y ago
    The why can be really important though. We do X because Google does it, or something like that is often a red flag because they have some insanely convoluted process that they don't need. knowing that things are selected that fit the size and scale of where a company is or will be soon is important.