News for hackers. Stuff that matters.
Re:We can all be AI engineers – and we can do it with open s... by abeppu on Thursday November 14, 2024 @01:13PM (#42139246)
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?

And frankly, when you hire a manager or executive, there's not generally a single artifact that you could use to examine their value-add. You can see perhaps the trajectory of a company or a division or the size of their team over time, but you can't see the pile of ongoing decisions and conversations that produce actual value.

I think the flip side regarding code is, the stuff I do for fun outside of my employer's IP is not at all representative of what I do at work, or how. I pick topics that interest me, work in languages that my company doesn't use, etc, and because my purpose is learning and exploration, often it doesn't end up as a finished, working, valuable piece of tech. I deliberately don't do anything too close to my actual work both b/c that just feels like working longer and because I'm concerned it would make ownership of the code a bit fuzzy, and perhaps it would be inappropriate to consider open sourcing. Because my side projects are eclectic and didactic, I rarely put it in a public repo -- but it has served its purpose of teaching me something. If I shared all of my code side projects, they would show an unfocused person dabbling in a range of areas and not shipping anything useful, because that's what's fun ... whereas at work, I am focused in a few quite narrow areas, and working on customer-facing features, because the point is to build what the company needs rather than what I enjoy building.

Re:We can all be AI engineers – and we can do it with open s... by cess11 on Thursday November 14, 2024 @02:27PM (#42140125)
If I'm shopping for an accountant I will present them with one or two cases and see how they would reason about them. It's not as easy to do with a physician.

The main difference between those professions and people who build software for a living is that they have organisations that predate modernity that keep tabs on their members and kick them out if they misbehave.

We should absolutely build such organisations, but there will be intense confrontations with industry and academia when we try, because capitalists hate when other people unionise and academics think they're the best at evaluating peers.

It's fine that your personal projects aren't polished products. They show your interests and some of how you adapt to and solve problems. It's something you've chosen to do because you wanted to, and not something you did because you were pressured by profit. The everyday grind at work wouldn't show what you'd do under more exceptional circumstances, which is where your personal character and abilities might actually matter, but what you do for fun or personal development likely does.

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.

Re:We can all be AI engineers – and we can do it with open s... by rqmedes on Thursday November 14, 2024 @06:50PM (#42142578)
What a fantastic reply