But, like... wouldn't you want them to at least know the steps of `git add` -> `git commit` -> `git push` and then click the button on Github? And Gitlab has basically the same web UI.

I have no problem with letting an IDE or LLM handle those details in practice... but I don't think I'd want to work with someone who doesn't understand the very basics of what's going on under the hood.

▲ pdonis 8 hours ago | parent | next [-]

> wouldn't you want them to at least know the steps of `git add` -> `git commit` -> `git push`

The GP said "open a PR", not "make a commit and push it to a remote".

▲ labcomputer 2 hours ago | parent [-]

Well, I can't read the GP's mind, but I'm fairly certain they didn't literally mean "candidate knows how to click one button in the web UI for a specific proprietary developer platform and type some stuff into a text box".

When I tell my LLM to "open a PR for those changes" (which is how I do it nowadays), my LLM understands that what I mean is "make a commit, push it to a remote and raise a PR".

Does it mean we've reached AGI when machines understand what we mean better than some humans?

▲ pdonis 2 hours ago | parent [-]

> When I tell my LLM to "open a PR for those changes" (which is how I do it nowadays), my LLM understands that what I mean is "make a commit, push it to a remote and raise a PR".

This makes it seem like all of those things are part of a single operation to you. That doesn't make sense to me.

On the occasions where I've submitted a PR to a project (anywhere, not just on Github), making the commit was not part of the same operation. I'd already made the commit and satisfied myself that it captured everything I wanted, before making the PR. I don't see those things as part of a single operation. I don't think the poster you were responding to does either.

▲ labcomputer an hour ago | parent [-]

  > That doesn't make sense to me.

So you think the OP is asking candidates a question, where the solution is:

1. Navigate your browser to GitHub.mycompany.example.com

2. Click the repo name

3. Click pull requests

4. Click the source branch[1] and destination branch

5. Click "create pull request"

???

I started out by assuming this was some kind of good-faith disagreement, but I guess you're just trying to be funny.

[1] Presumably already extant, because they never mentioned anything about committing code, nor pushing it to github (and that's not the same operation!).

	▲	pdonis 34 minutes ago \| parent [-]
		> So you think The OP said: "we also ask the candidate to open a PR" So I think the OP meant to have the candidate, um, open a PR. Which is not the same thing as making a commit and pushing it to a remote. Maybe you always conflate those operations, but that doesn't make them the same operation. If the OP actually meant that they ask the candidate to make a commit, push it to the remote, and then open a PR, I would have expected the OP to say, um, all of those things, instead of just the last one. I couldn't say how the OP expected the candidate to open a PR, since I don't know what their standard workflow is. There are ways of doing it from the CLI, as well as through the web interface, as well as through various IDEs. > I started out by assuming this was some kind of good-faith disagreement, but I guess you're just trying to be funny. Please save your patronizing for another time. And stop trying to put words in my mouth.

▲ medler 8 hours ago | parent | prev | next [-]

Years ago I was the “git expert” on my team, the person you went to when you got into trouble. But I have long since moved to jj, and I basically don’t remember git commands anymore. I also don’t use GitHub much, so when I need to open a PR I prompt an LLM to do it for me.

▲ calculatte 6 hours ago | parent | prev [-]

Why should anyone care? This is something that can be taught and learned in 2 minutes.