News for hackers. Stuff that matters.
Re:We can all be AI engineers – and we can do it with open s... by JSDevOps on Thursday November 14, 2024 @10:05AM (#42136819)
Is anyone instantly suspicious when they introduce themselves these days an "AI Developer"
Re:We can all be AI engineers – and we can do it with open s... by pjmlp on Thursday November 14, 2024 @10:32AM (#42137171)
Yes, just like "Data Engineer" for knowing how to use Tableau or doing OLAP queries.
Re:We can all be AI engineers – and we can do it with open s... by WorldWideWebb on Thursday November 14, 2024 @11:41AM (#42137975)
I feel the same way about “UX Designer/Engineer”. Seems to mean someone who can put a wireframe together but has no design chops. Any good designer that has experience crafting user interfaces should be skilled at thinking through in-depth about what the user is doing when using the product and how to successfully guide them through that process.
Re:We can all be AI engineers – and we can do it with open s... by Ldragon27 on Thursday November 14, 2024 @11:35AM (#42137904)
Are you saying that true Data Engineers typically do more than just use Tableau or run OLAP queries, or do you see the title 'Data Engineer' itself as a bit of a red flag these days? I’m pretty early in my career and was leaning toward Data Engineering, but hearing stuff like this makes me wonder if going for SWE might be smarter.
Re:We can all be AI engineers – and we can do it with open s... by hobs on Thursday November 14, 2024 @11:40AM (#42137954)
The better paying role is a Backend SWE (usually). A really a good data engineer is just a Backend SWE who has specific experience.

A bad one is a SQL analyst whose been promoted too much.

Re:We can all be AI engineers – and we can do it with open s... by bubbleRefuge on Thursday November 14, 2024 @01:03PM (#42139112)
as as data engieer/data architect , agreed. there are allot of 'tools' experts who are data engineers but can't code a lick.
Re:We can all be AI engineers – and we can do it with open s... by hobs on Thursday November 14, 2024 @02:01PM (#42139859)
Yep, that's where I am at - the amount of times people have talked to me about the most recent podcast where they've heard how a new tool will solve all their problems and really its some samey mix of CDC and bad python+sql is... a lot.

I think there's not a ton of political palatability for realizing most of their projects are like one API and a sane use of some SQL away.

Re:We can all be AI engineers – and we can do it with open s... by pjmlp on Thursday November 14, 2024 @12:07PM (#42138306)
For starters, Engineer only makes sense if the person actually holds an engineering degree, taken at an institution validated by the Engineering Order.
Re:We can all be AI engineers – and we can do it with open s... by JohnFen on Thursday November 14, 2024 @12:15PM (#42138435)
That's a legalism that isn't universal. Personally, I think that anyone who engages in engineering is logically an engineer. Maybe not a certified engineer, but an engineer nonetheless.
Re:We can all be AI engineers – and we can do it with open s... by pjmlp on Thursday November 14, 2024 @12:29PM (#42138648)
So is anyone that cooks a Chef.
Re:We can all be AI engineers – and we can do it with open s... by JohnFen on Thursday November 14, 2024 @12:38PM (#42138761)
"Chef" is a specific job title. Anyone who has that job, regardless of qualifications, is a "chef", yes.
Re:We can all be AI engineers – and we can do it with open s... by pjmlp on Thursday November 14, 2024 @04:09PM (#42141254)
Yeah but can they deliver, and handle a kitchen, like one that actually has a diploma in Culinary arts?
Re:We can all be AI engineers – and we can do it with open s... by portaouflop on Thursday November 14, 2024 @07:43PM (#42142908)
Sometimes they can, sometimes not. What is your point here?
Re:We can all be AI engineers – and we can do it with open s... by JohnFen on Friday November 15, 2024 @10:02AM (#42147516)
Some can, some can't. A degree is no guarantee that the person is able to perform at a high level, and the lack of a degree is no guarantee that they can't.

But none of that is relevant to my point, which is largely linguistic. If a person is doing a thing, then they are "a person who is doing the thing."

If a person is engineering, then they're an engineer by definition. That's not saying they're a good or bad engineer, just that's what they're doing.

There is a role for certifications, of course! But those certifications are intended to mark a lower boundary of ability, nothing more. Rather than overloading "engineer" to indicate that a person has a certification, I'd advocate calling them something like a "certified engineer". That would be correct and accurate, and wouldn't exclude a whole lot of great defacto engineers.

Re:We can all be AI engineers – and we can do it with open s... by hobs on Thursday November 14, 2024 @12:35PM (#42138726)
My Kiss The Chef apron says yes.
Re:We can all be AI engineers – and we can do it with open s... by taway1874 on Thursday November 14, 2024 @12:49PM (#42138910)
LOL! A butcher cuts meat and so does a surgeon. Who would you prefer to operate on you?
Re:We can all be AI engineers – and we can do it with open s... by Eisenstein on Thursday November 14, 2024 @03:45PM (#42141029)
"The creative application of scientific principles to design or develop structures, machines, apparatus, or manufacturing processes, or works utilizing them singly or in combination; or to construct or operate the same with full cognizance of their design; or to forecast their behavior under specific operating conditions; all as respects an intended function, economics of operation and safety to life and property"[1]

[1] https://en.wikipedia.org/wiki/Engineering

Re:We can all be AI engineers – and we can do it with open s... by valval on Thursday November 14, 2024 @11:28AM (#42137828)
To be fair, the market dictates the job titles.
Re:We can all be AI engineers – and we can do it with open s... by Taylor_OD on Thursday November 14, 2024 @01:02PM (#42139088)
Eh. Titles dont really mean anything. Do we want to start the age old software engineer vs software developer title debate again?

Let someone call themselves whatever they want. If they can do the job they were hired for then... who cares?

Re:We can all be AI engineers – and we can do it with open s... by pjmlp on Thursday November 14, 2024 @04:11PM (#42141273)
Yes, we want, a bootcamp isn't a three to five years degree with a possible exam.
Re:We can all be AI engineers – and we can do it with open s... by bubbleRefuge on Thursday November 14, 2024 @01:02PM (#42139089)
having data engineer in my title has led to recruiters calling about DBA type roles. ugh.
Re:We can all be AI engineers – and we can do it with open s... by wrs on Thursday November 14, 2024 @11:39AM (#42137950)
I’m instantly suspicious when anyone uses the term “AI”.
Re:We can all be AI engineers – and we can do it with open s... by bdangubic on Thursday November 14, 2024 @12:19PM (#42138503)
in 2024 thats as crazy as being suspicious of anyone that uses the term “internet”
Re:We can all be AI engineers – and we can do it with open s... by wrs on Thursday November 14, 2024 @03:31PM (#42140861)
I guess your perception depends on how many tech hype cycles you’ve lived through. I’ve lived through three for “AI” alone.
Re:We can all be AI engineers – and we can do it with open s... by 8338550bff96 on Thursday November 14, 2024 @04:12PM (#42141278)
Who cares what it is called? I care about the capabilities.

In my experience when people say things like this what they're just projecting insecurity

Re:We can all be AI engineers – and we can do it with open s... by taway1874 on Thursday November 14, 2024 @12:51PM (#42138934)
No, it's not crazy at all. Back in the early noughts everyone was associating themselves with Internet and WorldWideWeb (yes, they used to spell that out). Same thing happening today with AI. It is irritating ...
Re:We can all be AI engineers – and we can do it with open s... by ocular-rockular on Thursday November 14, 2024 @02:30PM (#42140165)
You would be surprised how many people have no idea what "machine learning" means (not even technical definition but just as in the field). I'm working on a PhD in an adjacent field and basically have to tell people I work in AI for them to have any semblance of what I do.
Re:We can all be AI engineers – and we can do it with open s... by namaria on Thursday November 14, 2024 @05:50PM (#42142060)
I don't think telling people that have no idea what machine learning is that you work with 'AI' is giving them any semblance of understanding what you do.
Re:We can all be AI engineers – and we can do it with open s... by ocular-rockular on Friday November 15, 2024 @11:56AM (#42148632)
No, it's not. But at least they have some relative, albeit flawed, context. It's the difference of having heard of something vs not.
Re:We can all be AI engineers – and we can do it with open s... by kmmlng on Friday November 15, 2024 @07:18AM (#42146224)
I used to be in the same camp, but have since abandoned this position. The world has changed. Very serious people use the term "AI" nowadays. I don't find that it's a high-precision signal for identifying charlatans anymore (though it is high-recall).
Re:We can all be AI engineers – and we can do it with open s... by master-lincoln on Thursday November 14, 2024 @11:38AM (#42137938)
I would interpret that as somebody working on ML algorithms and architectures, not somebody developing a product that uses some form of AI at runtime...
Re:We can all be AI engineers – and we can do it with open s... by JohnFen on Thursday November 14, 2024 @12:13PM (#42138404)
I work on such a team, and we don't refer to ourselves as "AI engineers". We're devs working on developing deep learning systems (but not genAI).
Re:We can all be AI engineers – and we can do it with open s... by swyx on Thursday November 14, 2024 @01:54PM (#42139765)
correct - but "developing a product that uses some form of AI at runtime" is a job that people do and the community has consolidated around "AI engineer" as shorthand https://www.latent.space/p/ai-engineer

i argue that its useful to have these shorthands to quickly understand what people do. its not so nice to just be default suspicious at a perhaps lower-technical-difficulty job that nevertheless a lot of comapnies want and a lot of people do

Re:We can all be AI engineers – and we can do it with open s... by dr_dshiv on Thursday November 14, 2024 @02:42PM (#42140311)
Difficulty ≠ Value

But we think it is, due to our learned industrious—which is the opposite of learned helplessness. We associate difficulty with reward. And we feel discomfort when really valuable things become very easy. Strange times.

Re:We can all be AI engineers – and we can do it with open s... by throwaway290 on Thursday November 14, 2024 @11:06PM (#42143882)
Why is it lower difficulty? If didn't get that impression from the article
Re:We can all be AI engineers – and we can do it with open s... by throwaway314155 on Thursday November 14, 2024 @03:11PM (#42140655)
> devs working on developing deep learning systems (but not genAI)

Catchy job title.

Re:We can all be AI engineers – and we can do it with open s... by 8338550bff96 on Thursday November 14, 2024 @04:05PM (#42141212)
I work on such a team too. I don't care what you call me - pay me
Re:We can all be AI engineers – and we can do it with open s... by JohnFen on Friday November 15, 2024 @10:04AM (#42147543)
My job title is "software engineer".
Re:We can all be AI engineers – and we can do it with open s... by spmurrayzzz on Thursday November 14, 2024 @11:54AM (#42138131)
I haven't seen this sort of work called AI Developer yet, but I may have missed the trend shift. Isn't the convention for this still to use the title of Machine Learning Engineer (MLE)?
Re:We can all be AI engineers – and we can do it with open s... by master-lincoln on Thursday November 14, 2024 @12:04PM (#42138269)
There is another thread here that seems to confirm it's me who has missed a trend shift. I didn't know this term had a special meaning. I just followed the thought that an x-developer is somebody developing x.
Re:We can all be AI engineers – and we can do it with open s... by throwaway290 on Thursday November 14, 2024 @11:03PM (#42143862)
They use "AI" like they use "Python" in "Python developer" or "Web" in "Web developer".
Re:We can all be AI engineers – and we can do it with open s... by 0points on Thursday November 14, 2024 @10:47AM (#42137380)
Instant red flag. Like "Scrum master" used to be back in the day.
Re:We can all be AI engineers – and we can do it with open s... by marcosdumay on Thursday November 14, 2024 @11:28AM (#42137815)
> back in the day

Well, most are called "project manager" now. But it would still be a giant red flag, just like the project manager job title or even worse, using PM so you don't know exactly what it means.

Re:We can all be AI engineers – and we can do it with open s... by amelius on Thursday November 14, 2024 @11:13AM (#42137641)
"AI engineer" is the new "Web developer".
Re:We can all be AI engineers – and we can do it with open s... by moffkalast on Thursday November 14, 2024 @11:20AM (#42137730)
I prefer the term "Scrumlord" /s
Re:We can all be AI engineers – and we can do it with open s... by 1123581321 on Thursday November 14, 2024 @04:01PM (#42141164)
There are some funny comments that use that term. This one’s my favorite. https://news.ycombinator.com/item?id=25721837
Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @10:11AM (#42136909)
> Is anyone instantly suspicious when they introduce themselves these days an "AI Developer"

I'm only suspicious if they don't simultaneously and eagerly show me their Github so that I can see what they've accomplished.

Re:We can all be AI engineers – and we can do it with open s... by llm_nerd on Thursday November 14, 2024 @10:20AM (#42137018)
Of the great developers I have worked with in real life, across a large number of projects and workplaces, very few have any Github presence. Most don't even have LinkedIn. They usually don't have any online presence at all: No blog with regular updates. No Twitter presence full of hot takes.

Sometimes this industry is a lot like the "finance" industry: People struggling for credibility talk about it constantly, everywhere. They flex and bloviate and look for surrogates for accomplishments wherever they can be found. Peacocking on github, writing yet another tutorial on what tokens are and how embeddings work, etc.

That obviously doesn't mean in all cases, and there are loads of stellar talents that have a strong online presence. But by itself it is close to meaningless, and my experience is that it is usually a negative indicator.

Re:We can all be AI engineers – and we can do it with open s... by jchw on Thursday November 14, 2024 @11:08AM (#42137592)
I think the actual truth is somewhere halfway. Hard to not have any GitHub presence if you use enough open source projects, since you can't even report bugs to many of them without an account.

But if you mostly mean in the sense that they don't have a fancy GitHub profile with a ton of followers... I agree, that does seem to be the case.

LinkedIn on the other hand... I sincerely can't imagine networking on LinkedIn being a fraction as useful as networking... Well, at work. For anyone that has a decent enough resume LinkedIn is basically only useful if you want a gutter trash news feed and to be spammed by dubious job offers 24/7. Could be wrong, but I'm starting to think you should really only stoop to LinkedIn in moments of desperation...

Re:We can all be AI engineers – and we can do it with open s... by mitchitized on Thursday November 14, 2024 @11:42AM (#42137991)
As a hiring manager LinkedIn profiles are a huge window into someone's professional side, just like github may be a huge window into their technical side.

As a candidate I think LinkedIn is absolute trash - and toxic with all the ghost jobs and dark patterns. Feels like everyone else has the same opinion, or at the very least it is a common one. But when I have 50 candidates to review for 5 open positions, LinkedIn is going to give me great insight that I cannot really get anywhere else. I keep my profile current in the hopes that I'm not doing it for LinkedIn, but for the person researching me to see if I am a valid candidate for their role.

Re:We can all be AI engineers – and we can do it with open s... by namaria on Thursday November 14, 2024 @05:57PM (#42142134)
"Linkedin is trash but I use it as a signal source" is kinda telling on yourself there bud.
Re:We can all be AI engineers – and we can do it with open s... by bdangubic on Thursday November 14, 2024 @12:25PM (#42138595)
coding since the ‘90’s - do not have a github account at all that I ever used for anything. of the top say 10 people I have ever worked with not a single one has a github account.

there is an entire industry of devs who work on meaningful projects, independently or for an employer who solve amazing problems and do amazing sh*t none of which is public or will ever be public.

I have signed more NDAs in my career than I have commits in public repos :)

Re:We can all be AI engineers – and we can do it with open s... by jddj on Thursday November 14, 2024 @02:35PM (#42140219)
Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @04:16PM (#42141315)
> I have signed more NDAs in my career than I have commits in public repos :)

Someone like you is extremely experienced and skilled, and has a reputation in your industry. You started working before it was normal and trivial to build stuff in public. Such activities were even frowned upon if I recall correctly (a friend got fired merely for emailing a dll to a friend to debug a crash; another was reprimanded for working on his own projects after hours at the office, even though he never intended to ever sell them).

That you have a reputation means posting work publicly would be of little to no value to your reputation. All the people who need to know you already do or know someone reputable who does.

Re:We can all be AI engineers – and we can do it with open s... by rqmedes on Thursday November 14, 2024 @06:33PM (#42142449)
In the same boat, the problem is you get stuck in a few companies due to the small circles of people who know what you can really do. It really limits your career options. Doesn’t matter if you regularly do in a week what a few hundred engineers cannot do in a year if no one knows it. Your get stuck in a big corp as they will pay you just enough to keep, nothing close to your worth as with no brand your not going to find better anywhere else
Re:We can all be AI engineers – and we can do it with open s... by bdangubic on Thursday November 14, 2024 @07:51PM (#42142951)
I wrote a relatable to your comment comment on this post: https://news.ycombinator.com/item?id=42141453
Re:We can all be AI engineers – and we can do it with open s... by jchw on Thursday November 14, 2024 @07:29PM (#42142800)
I suspect we're very different.

I'm younger, but not new to programming (started in the early 2000s.) Mentality-wise, I like working on software because I like solving problems, but I only really do a day job to make a living, not to scratch an itch, so I continue to work on software outside of work hours. I basically don't care what happens once my software reaches the Internet. I publish some open source software, but not as a portfolio; just for the sake of anyone who might find it useful. I don't really advertise my projects, certainly don't go out of my way to do so.

I basically have GitHub for roughly two reasons:

- I use a wide variety of open source software. I like to fix my own problems and report issues. Some projects require GitHub for this.

- May as well take advantage of the free storage and compute, since everyone else is.

Honestly, my GitHub is probably a pretty bad portfolio. It is not a curation of my best works, and I disabled as much of the "social" features as possible. It's just code that I write, which people may take or leave.

Earlier in my career maybe I cared more, but I honestly think it's because I thought you were supposed to care.

I have worked with some stellar programmers from many different places, probably more than I really deserved to. I don't know for sure if any of them didn't have GitHub accounts, but some of them definitely did have GitHub accounts, barren as they may have been.

Re:We can all be AI engineers – and we can do it with open s... by jacobr1 on Thursday November 14, 2024 @12:35PM (#42138719)
LinkedIn remains a reasonable substitute for emailing around PDFs of resumes/CVs.

Any usage beyond that, for "networking" or "social sharing" is terrible.

Re:We can all be AI engineers – and we can do it with open s... by A4ET8a8uTh0 on Thursday November 14, 2024 @02:14PM (#42139997)
<< I sincerely can't imagine networking on LinkedIn being a fraction as useful as networking.

I have removed my profile some time ago. While I agree with you in general, I have to say that initially LinkedIn was actually not bad and I did get some value out of it. It is a little harder now to not have it, because initial interviews scoff at its absence ( it apparently sends a negative signal to HR people ), but an established network of colleagues can overcome that.

I guess it is a little easier for people already established in their career. I still am kinda debating some sort of replacement for it, but I am honestly starting to wonder if github is just enough to stop HR from complaining.

Re:We can all be AI engineers – and we can do it with open s... by CM30 on Thursday November 14, 2024 @02:45PM (#42140342)
Eh, I've found LinkedIn moderately useful as a way to apply for jobs and share my CV. A few application forms have a field for it too.

Still have no idea how anyone can even hope to use the news feed there though. It's just a seemingly random torrent of garbage 24/7, with the odds of you getting any traction being virtually non existent.

Re:We can all be AI engineers – and we can do it with open s... by hardolaf on Thursday November 14, 2024 @08:49PM (#42143233)
> since you can't even report bugs to many of them without an account.

I joined my current employer a bit over a month ago at this point and legal still hasn't authorized me to open a GitHub account or authorized me to use my personal account to report issues.

Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @10:18PM (#42143683)
> legal still hasn't authorized me to open a GitHub account

Damn. You signed a contract that prevents you from ever publishing your own code? I guess everyone in the comments who are against have something to show in public all have security clearance or something. : ^ )

Re:We can all be AI engineers – and we can do it with open s... by hardolaf on Tuesday November 19, 2024 @08:19AM (#42183097)
I signed a contract prohibiting doing anything that I'm compensated to do for work outside of work or using information gleaned from my job without permission of the firm. This is a standard contract clause.
Re:We can all be AI engineers – and we can do it with open s... by red-iron-pine on Friday November 15, 2024 @01:03PM (#42149314)
in my experience linkedin is basically useless, outside of allowing HR to validate you exist and have enough connections at companies you used to work at to prove you were there. but even those can be gamed.
Re:We can all be AI engineers – and we can do it with open s... by JSDevOps on Thursday November 14, 2024 @10:30AM (#42137152)
If someone has to tell you either themselves of by proxy they are influential in the industry ... they are not.
Re:We can all be AI engineers – and we can do it with open s... by bilbo0s on Thursday November 14, 2024 @10:49AM (#42137399)
I’ve found this to be especially true of the great business minded devs that I’ve come across. They’re not giving you crap for free. Pardon my French.
Re:We can all be AI engineers – and we can do it with open s... by 0points on Thursday November 14, 2024 @10:51AM (#42137418)
It's spelled crêpe
Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @10:48AM (#42137381)
> Of the great developers I have worked with in real life, across a large number of projects and workplaces

Dear God, let's not pretend to be obtuse or facile. Saying "GitHub" is just a way of saying: "Show me what you've accomplished."

If someone has no accomplishments anywhere to show then someone else might find them credible but I don't, as a heuristic.

It's really not that difficult to show what you've accomplished if you claim to be in a field.

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.

Re:We can all be AI engineers – and we can do it with open s... by llm_nerd on Thursday November 14, 2024 @11:16AM (#42137673)
>Saying "GitHub" is just a way of saying: "Show me what you've accomplished."

Do you actually think all development happens in public GitHub repos? Do you even think a majority does? Even a strong minority?

Across a number of enormous, well-known projects I've worked on, covering many thousands of contributors, including several very well known names, 0% of it exists in public Github repos. The overwhelming bulk of development is happening in the shadows.

If your "field" is "open source software", then sure. But if you're confused into thinking Github -- at least the tiny fraction that you can see -- is "the field" of software development or even just generally providing solutions, I can understand your weird belief about this.

Re:We can all be AI engineers – and we can do it with open s... by noch on Thursday November 14, 2024 @11:31AM (#42137858)
> Do you actually think all development happens in public GitHub repos? Do you even think a majority does? Even a strong minority?

Are you actually able to read what I wrote? I said "GitHub" is a euphemism. I'm happy to read your papers on arxiv or elsewhere, for instance.

Try not to be too horny to reply in opposition and instead just read what another human is saying first. Otherwise your replies in high dudgeon are a waste of my time and don't teach me anything new.

Re:We can all be AI engineers – and we can do it with open s... by noch on Friday November 15, 2024 @07:40AM (#42146361)
> Do you actually think all development happens in public GitHub repos? Do you even think a majority does? Even a strong minority?

Do you think everyone you encounter is an idiot who just learned about the Internet yesterday? I started programming long before Github or Sourceforge even existed so given that all your assumptions about who you're talking to are so full of bad faith, I can only assume you have a chip on your shoulder and you don't know how to read what I wrote previously.

Re:We can all be AI engineers – and we can do it with open s... by taway1874 on Thursday November 14, 2024 @12:56PM (#42139012)
This is exactly what we're talking about here and you are proving our point.
Re:We can all be AI engineers – and we can do it with open s... by taway1874 on Thursday November 14, 2024 @12:53PM (#42138964)
Well said! Have you seen the titles and summary of those LinkedIn profiles? Not an ounce of humility. I'm afraid it's only going to get worse with "AI".
Re:We can all be AI engineers – and we can do it with open s... by woodson on Thursday November 14, 2024 @02:40PM (#42140294)
I say “I work in machine learning, what kids these days call AI” ;).