4 ms·

I feel bad for your team. Let people work how they want. I wouldn’t not hire someone on the basis of them not using a language server. The creator of the Odin

by dartos 2y ago

I feel bad for your team. Let people work how they want. I wouldn’t not hire someone on the basis of them not using a language server. The creator of the Odin language famously doesn’t use one. He’s says that he, specifically, is faster without one.

theptip 2y ago
No, it’s reasonable. If your team uses Git then it’s a valid question to establish if someone has only worked with Perforce. They didn’t say how heavily they weight the question. (All that said I expect that, soon, experience with the appropriate LLM tooling will be as important as having experience with the language your system is implemented in.)
- dartos 2y ago
  Right, but using git is a team wide thing. I can’t use perforce while my company is on git. But if I do or do not use an LLM to assist me while coding, my team is unaffected. If someone liked jetbrains, but your team used neovim, would you force them to use neovim?
  - Kwpolska 2y ago
    Editors may also be a team decision in some places. Some teams are using features unique to one IDE, for example.
    - chikere232 2y ago
      it can be a team decision, but it's a bad one
    - dartos 2y ago
      Then that tooling is required, like visual studio is a common one I know about in windows land. Though nobody should care if I edited my text files with neovim as long as I still used the same toolchain as everyone else.
- paxys 2y ago
  You hire people based on their fundamental knowledge and the ability to learn, not skills in arbitrary tools and frameworks which come and go every other day. If someone has used Perforce they will be able to get perfectly comfortable with Git by the end of their first week. So not knowing Git is an idiotic reason to reject a skilled developer. Same with programming languages, and just about every other aspect of software development.
  - swalsh 2y ago
    I don't really test any specific tools or frameworks, what i'm using has changed twice just in the last year. More so, I just want to hear that the candidate has some knowledge of what the current models can do well, what they can't do, and how they're integrating it. Whether you're copying pasting code or using something like cursor is not what i'm concerned about.
  - codr7 2y ago
    Yeah, but it's oh so easy to test for, and oh so nice to have plenty of boxes checked to cover your ass if the hire goes wrong.
swalsh 2y ago
My expectations around productivity are going to assume you're using AI. That means stuff that might have taken a few days, i'm going to expect in a few hours or less. It's not unreasonable, i've seen over and over agian that kind of speed up. I have a lot less approval to hire people than I used to... so it's really important to me that I can extract that level of productivity out of my team. If you're "working the way you want to" ie still handrolling all your code, you're going to find my expectations unrealistic, and that is certainly not fair to you.

by dartos 2y ago

theptip 2y ago

No, it’s reasonable. If your team uses Git then it’s a valid question to establish if someone has only worked with Perforce. They didn’t say how heavily they weight the question. (All that said I expect that, soon, experience with the appropriate LLM tooling will be as important as having experience with the language your system is implemented in.)

dartos 2y ago
Right, but using git is a team wide thing. I can’t use perforce while my company is on git. But if I do or do not use an LLM to assist me while coding, my team is unaffected. If someone liked jetbrains, but your team used neovim, would you force them to use neovim?
- Kwpolska 2y ago
  Editors may also be a team decision in some places. Some teams are using features unique to one IDE, for example.
  - chikere232 2y ago
    it can be a team decision, but it's a bad one
  - dartos 2y ago
    Then that tooling is required, like visual studio is a common one I know about in windows land. Though nobody should care if I edited my text files with neovim as long as I still used the same toolchain as everyone else.
paxys 2y ago
You hire people based on their fundamental knowledge and the ability to learn, not skills in arbitrary tools and frameworks which come and go every other day. If someone has used Perforce they will be able to get perfectly comfortable with Git by the end of their first week. So not knowing Git is an idiotic reason to reject a skilled developer. Same with programming languages, and just about every other aspect of software development.
- swalsh 2y ago
  I don't really test any specific tools or frameworks, what i'm using has changed twice just in the last year. More so, I just want to hear that the candidate has some knowledge of what the current models can do well, what they can't do, and how they're integrating it. Whether you're copying pasting code or using something like cursor is not what i'm concerned about.
- codr7 2y ago
  Yeah, but it's oh so easy to test for, and oh so nice to have plenty of boxes checked to cover your ass if the hire goes wrong.

swalsh 2y ago

My expectations around productivity are going to assume you're using AI. That means stuff that might have taken a few days, i'm going to expect in a few hours or less. It's not unreasonable, i've seen over and over agian that kind of speed up. I have a lot less approval to hire people than I used to... so it's really important to me that I can extract that level of productivity out of my team. If you're "working the way you want to" ie still handrolling all your code, you're going to find my expectations unrealistic, and that is certainly not fair to you.