News for hackers. Stuff that matters.
Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @01:48PM (#42139678)
> If you hire an accountant, do you expect to see the books of their other clients? When you choose a doctor, do you expect to see the charts of their prior patients?

I'm genuinely sorry for you if you think a programmer is analogous to an accountant or doctor. Presumably you are one of those people who think that a Software Engineer is as much an engineer as a Civil Engineer?

Anyway, let me not speculate as to your state of mind. You wrote a lot of words. What exactly are you even trying to defend or attack or justify? Is the number of your words commensurate to the informational content of what you think you're explaining? Can you explain your point in 1 sentence? Or perhaps I should just ask an LLM to summarize it. smh.

Re:We can all be AI engineers – and we can do it with open s... by abeppu on Thursday November 14, 2024 @04:22PM (#42141367)
Even if an ML/AI/software engineer has a public GH with projects on it, there's no strong reason to expect it will be a useful signal about their expertise.
Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @05:15PM (#42141783)
> Even if an ML/AI/software engineer has a public GH with projects on it, there's no strong reason to expect it will be a useful signal about their expertise.

That's only true if you don't know how to read code. I simply read their code and based on my level of expertise, I can determine if someone is at least at my level or if they are incompetent.

Re:We can all be AI engineers – and we can do it with open s... by abeppu on Thursday November 14, 2024 @07:25PM (#42142777)
I can't tell if you're deliberately ignoring the point: people's public hobby projects may not be _about_ their area of expertise. They may be side projects specifically because they are outside of their main area. It isn't about ability to read code. It's about the difference between what you know well enough to build a career in (and produce non-public work) and what's interesting enough that you'll build it and give it away for fun. They may have very little to do with one another, even if both are expressed in code.
Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @08:18PM (#42143068)
> I can't tell if you're deliberately ignoring the point: people's public hobby projects may not be _about_ their area of expertise.

I suspect it's you who's ignoring the entire conversation.

I initially replied saying that I don't trust someone who says they are an AI engineer yet have no code to enthusiastically show publicly. I used "show your GitHub" as a euphemism for "show your work".

> It's about the difference between what you know well enough to build a career in (and produce non-public work) and what's interesting enough that you'll build it and give it away for fun. They may have very little to do with one another, even if both are expressed in code.

This statement just tells me you don't know how to read code or haven't read much code. Code is just an expression of how an individual solves technical problems using algorithms, which are just a sequence of steps the CPU runs. There's no magical specificity in a field that prevents programming from being a transferrable knowable skill for the reader or the writer.

Or perhaps you're just being hard-headed and choosing to miss my point because you really want to oppose something someone said. I don't know.