Sam BlackFeb 20
Flaki

"Learning to work effectively with AI is quickly becoming a core professional skill. Ignoring AI today would be like refusing to adopt source control twenty years ago."

Oh golly, I almost forgot SVN stole hundreds of thousands of peoples' (and particularly artists) livelihoods, set us back decades in climate change emissions reduction and increasingly hurling towards global catastrophe while _also_ upending global economy in hogging the combined human output of equipment production to manifest _even more_ data centers that will propel us even further towards a hypercapitalist dystopian hellscape. Good to be reminded.

Feb 20 at 6:55amWeb
Show threadAedan CullenFeb 20
@flaki I wonder if there will be an AI-versus-no-AI bifurcation in technology employers/employees. Will some companies be confident enough in themselves to say "your work here is expected to be human work; anything else is considered dishonest/against policy?" It seems to me that policy could be a filter for hiring really good people. You'd guarantee yourself a strong workforce into the future, by which time everyone else would've possibly run themselves into the ground by losing all their human ingenuity. You'd welcome all the young people who are genuinely motivated to learn rather than cheat, give them a place to build their human skills, and ultimately end up with way more high-power engineers than your competitors.
Show threadAzuaronFeb 20

@flaki Look, I hate AI more than just about anyone, but that quote is orthogonal to everything you're saying. Both things are true:

  • Learning to work effectively with AI is quickly becoming a core professional skill. Ignoring AI today would be like refusing to adopt source control twenty years ago.

  • AI is a massively destructive and unethical technology.

These statements are not contradictory.

My company is going to make me learn AI soon, and I really don't know what I'm going to do after that. It seems like all software engineering jobs are going full AI now. Stick it out and hate my life? Go full luddite and take down data centers? Die homeless? Retrain to a new industry?

Maybe I'll become a welder.

Show threadMatt PanaroFeb 20
@Azuaron @flaki
hah, I just saw a billboard for a welding school the other day, and seriously thought about it 😜
Show threadThe Orange ThemeFeb 20
@Azuaron @flaki AI is a core professional skill in 2026 like doing lines of coke was a core professional skill in 1985. That is to say, a lot of people might be doing it and pressuring you to join, but that doesn't make it good, and it doesn't mean you have to do it.
Show threadAzuaronFeb 20
@theorangetheme Buddy, fuck off. I'm literally going to get fired about this, so just fuck off.
Show threadThe Orange ThemeFeb 20
@Azuaron I'm sorry, but you don't need to talk to me that way. Enjoy your block.
Show threadAndrew DalkeFeb 20

@flaki If that argument is taken seriously, professionals can ignore AI for 10-25+ years.

20 years ago is 2006. SCCS started in late 1972. From "The Source Code Control System" (1975): "The Programmer's Workbench has proven to be very popular with both management and programmers, and is now used by almost all software projects at the author's installation." "The Evolution of a Source Code Control System" (1978) says there were 3 million LOC under SCCS.

Where I worked in 1993-1998, we used CVS.

Show threadJeff GriggFeb 20

@dalke @flaki

Yea; I learned RCS (Unix Revision Control System) in the 1970s.

And some people are going without source control even now.

But source control has obvious benefits, in terms of tracking changes, recovering old versions, collaboration between team members, auditing, etc.

…

The best measures of LLM usage show slightly negative value. And they'd have to multiply productivity by at least an order of magnitude to actually be worthwhile.

Show threadAndrew DalkeFeb 20

@JeffGrigg @flaki My comment was directed more to the presented thesis.

1) if it has meaning we can look at the history of source control to see the decades of development, cost/benefit studies, and diffusion, including grass-roots uptake, before it became an expected skill for professional developers ca. 20 years ago;

2) otherwise, it demonstrates that the person making the argument (and most of the audience, alas) is ignorant of the history.

The word "truthiness" is also ca. 20 years old.

Show threadJeff GriggFeb 20

@dalke @flaki

I think we are, mostly, vigorously agreeing with each other.

Yes, some employers "forced" source control onto coders who did not want it.

But it's a cheap technology with lots of obvious and easily measurable benefits for the users and many others.

LLMs are costly, even "after" externalizing many of their costs. And their measured benefits are somewhere between "meh" and "you're better off without it."

And we're facing massive forced adoption.

Those are big differences.

Show threadAndrew DalkeFeb 20

@JeffGrigg @flaki I think we are having adjacent conversations.

You are comparing the pros and cons of using that technology. I agree with your assessment.

But I am criticizing the logic of a specific argument which, in its attempt to draw a parallel between the use of version control and use of AI to advocate for wider AI use, actually ends up being an argument *against* wider AI use.

I further conjecture that argument is made not from knowledge of history, but from truthiness vibes.

Show threadMatt PanaroFeb 20
@flaki remember when every executive mandated source control, and made its adoption a quarterly performance objective? And the Super Bowl ads! So many, and so creative! 😝