News for hackers. Stuff that matters.
Re:We can all be AI engineers – and we can do it with open s... by kazinator on Thursday November 14, 2024 @11:18AM (#42137704)
> It's really not that difficult to show what you've accomplished if you claim to be in a field.

Actually it is incredibly difficult, because you no longer have access to your previous employers' code bases and even if you do, it is illegal for you to show it to anyone.

Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @11:33AM (#42137888)
> Actually it is incredibly difficult, because you no longer have access to your previous employers' code bases.

So the person never does anything outside of his employer's IP? That's unfortunate, but as a heuristic, I'd like to see stuff that the person has done if they claim to be in a field.

Perhaps other people don't care, and will be convinced by expertise without evidence, but I'm busy, and my life is hard enough already: show me your code or gtfo. :-)

Re:We can all be AI engineers – and we can do it with open s... by kazinator on Thursday November 14, 2024 @12:31PM (#42138680)
Newsflash: the majority of working, paid developers do not do any programming outside of their employer's IP.

Someone who worked on successful projects that shipped and are still out there, they can point you to that. You can buy the app, or device with their embedded code, or use the website or whatever. Not always an option for everyone, or not all the time.

That's one reason why there are skill tests in interviews. And why people ask for, and contact, references.

Public code can't be trusted. If you make that the yardstick for hiring people, then everyone and his dog will spin up some phony github repo with stuff that can't be confirmed to have been written by them. Goodhart's Law and all that.

You have no idea how much help someone had with the code in their github repo, or to what extent it is cribbed from somewhere else. Enter AI into the picture now, too.

Re:We can all be AI engineers – and we can do it with open s... by cess11 on Thursday November 14, 2024 @02:14PM (#42140009)
When assessing a candidate that didn't come with a reliable recommendation or similar short circuiting I spend a short time chatting to learn a little about their personality, then I ask for code, suggesting they show a public repo where they keep some of their personal stuff.

If they can't I give the option to write some code that they like and they think shows off what they can do, usually suggesting to spend half an hour or a couple of hours on it.

To me it's an obvious red flag if there is nothing. It's as if talking to a graphics designer or photographer and they're like "no, sorry, I can't show a portfolio, I've only done secretive proprietary work and have never done anything for fun or practice".

Those that show me something get to talk about it with me. A casual chat about style, function, possible improvements and so on. Usually when they have nothing to show they also don't put in that half an hour to make something up, or get back with excuses about lack of inspiration or whatever, and that's where I say "thanks, but no thanks, good luck".

If you can't easily initiate a git repo and whip something up and send it to me in half an hour you won't be a good fit. It means you aren't fluent and lack in experience. I might consider internship, or a similar position where you mainly do something else, perhaps you're good at managing Linux servers or something but want to learn how to design programs and develop software as well.

Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @01:39PM (#42139565)
> Newsflash

Thanks for the newsflash! It's always great to hear that snarky boomer anachronism. Do you remember how you'd be watching cartoons then suddenly a dramatic interruption, a banner flying across the screen, clarions sounding, and bam! Newsflash! Upon which your parents tell you to hush because "this is important!".

> the majority of working, paid developers do not do any programming outside of their employer's IP.

Dude. Explain that to your recruiter. I'm just a random and we're hanging out talking about transformers then a guy walks into the bar and proclaims, "I am an AI engineer!" Just show me some code already or what are we even talking about when you say you're an AI engineer?

This isn't a moral issue. I'm glad that you (and allegedly majority of developers) are employed and never do anything outside of work. But for the purposes of a conversation, what are you talking about in a field if you have nothing at all to show in public or to your peer group?

> Public code can't be trusted. […] You have no idea how much help someone had with the code in their github repo, or to what extent it is cribbed from somewhere else. Enter AI into the picture now, too.

Code either compiles and runs or it does. The author can either explain it or doesn't understand it.

That's why we would have a conversation: For instance, if I'm hiring (or if I'm being hired), or we're just having a semi-serious conversation about technical stuff, we typically walk each other through something difficult that we solved. We discuss the code we've written and show it. We talk about stuff and that's how we figure out how much we both know about the topic.

Why is this even remotely controversial? ;-) Do you guys never talk to anyone about what you do or what you know? Do you never help friends or colleagues or even acquaintances discuss technical problems at their companies or startups or with their freelance projects? Do you never just discuss technical stuff after having a meal with friends, when you open a laptop and read code? Do you even never write code with friends for fun or to figure out new stuff about novel problems?

> That's one reason why there are skill tests in interviews. And why people ask for, and contact, references.

Thanks for explaining to me how recruiting and employment works. Thankfully I'm an adult who has existed on the planet for some time. I imagine you assume I've never filed a reference letter? But I've also seen reference letters being gamed just like every other reputation system so ...

Anyway, out of curiosity, if you've literally never done anything other than what your employer gave you, how did you even become a programmer? You left college or high-school and walked straight into a job then learned to code there, or what?

Re:We can all be AI engineers – and we can do it with open s... by kazinator on Thursday November 14, 2024 @03:43PM (#42141005)
> The author can either explain it or doesn't understand it.

I've never been challenged to explain any of the code my CV points to. I could have made it all up. If they randomly asked about something I have not looked at in a long a while, it could actually look like I don't know it! There is so much of it that I would have to study the code as a full time activity to be able to fluently spout off about any random sample of it.

I think I'm going to rearrange my resume to move the free software stuff farther down and maybe shorten it. It could come across as a negative.

Some hiring people genuinely don't understand why someone would put in a 40 hour week and then do some more on evenings and weekends. Well, I don't know how many. In my career I heard something along those lines from around two. Not everyone will tell you.

> You left college or high-school and walked straight into a job then learned to code there, or what?

It doesn't describe me, but does almost everyone I've ever known in the field (other than distant strangers met through online free-software-related channels, who are an obviously biased sample).

Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @03:59PM (#42141143)
> If they randomly asked about something I have not looked at in a long a while, it could actually look like I don't know it!

Typically the interviewer asks: "Tell me about something you worked on in this list of stuff you provided."

An interview isn't designed to trick you into failing random questions. It's to find out what you care about. You choose what to talk about. :-)

At least, that's how I engage in conversations. I want you to decide what you want to talk about so that I can get to know you.

Re:We can all be AI engineers – and we can do it with open s... by spacemanspiff01 on Thursday November 14, 2024 @12:32PM (#42138687)
It takes a special someone to work 40-50 hrs per week, writing hard creative software, then go home and write hard creative software in a different domain, while also balancing family/life.

Also, unless you are in CA many companies have extensive IP assignment clauses, which makes moonlighting on other projects potentially questionable.(especially if they are assholes)

My previous job made it hard to even submit bugs/fixes to open source projects we used internally. Often we just forked b/c bureaucracy (there's a reason it was my previous job)

Not saying your wrong, seeing someone's code is nice. As long as you are aware that you are leaving alot on the table by excluding those that do not have a presence. (Particularly older with kids)

Re:We can all be AI engineers – and we can do it with open s... by rqmedes on Thursday November 14, 2024 @06:45PM (#42142537)
100%. Also The really difficult work is usually a lot more than 40-50 hours a week
Re:We can all be AI engineers – and we can do it with open s... by hardolaf on Thursday November 14, 2024 @08:53PM (#42143255)
> My previous job made it hard to even submit bugs/fixes to open source projects we used internally. Often we just forked b/c bureaucracy (there's a reason it was my previous job)

The process for me to submit a PR to an OSS project at my last firm took so long that by the time it got through legal review and I was authorized to see it through to the end, it had been 1.5 months and I went from having some free time to work on it at work to being swamped with work doing hardware bring-up and leading a massive redesign project.

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
Re:We can all be AI engineers – and we can do it with open s... by rqmedes on Thursday November 14, 2024 @06:41PM (#42142504)
This just tells me you have never worked on anything difficult or something you are passionate in your job
Re:We can all be AI engineers – and we can do it with open s... by kazinator on Thursday November 14, 2024 @09:50PM (#42143559)
Although I'm generally on your side in this debate, this remark is fallacious.

We simply cannot tell that.