• 0 Posts
  • 5 Comments
Joined 1 month ago
cake
Cake day: May 22nd, 2026

help-circle
  • timochka@lemmy.ziptoSelfhosted@lemmy.worldSelfhosted & AI - Part 2: The Results
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    edit-2
    1 day ago

    Honestly? Let the wave of neo-ludditism pass?

    Is it necessary to respond to every Internet fad? Ignore it and eventually it will go away. Pretending otherwise is like thinking King Cnut can hold back the tide.

    (Or, if that’s not good enough - just ban promotion entirely. I don’t give a rat’s arse if code was AI generated or artisanally hand-woven onto magnetic cores by Jeff Minter in a kaftan - the real problem is spam, so just stop all promotional posts and the problem goes away.)


  • Christ.

    When will the forward-planning sub-committee of the AI tagging steering group be meeting? I presume they’re going to need to submit a motion to the ways-and-means council sub-sub-committee first and then maybe we can expect a notice on the procedure to follow for interim planning permission to write a post? Will interim planning permission allow the post to be made (subject to the countersignature of the automated post approval bot) or should it be saved in Drafts and then a separate submission (noting the interim permission and any objections received in the consultation period) be made to the full plenary session of the zoning committee?

    Or do we just say “fuck this shit” and find another group?




  • He may be dead right, and unduly pessimistic at the same time.

    The industry massively overhired relatively unskilled people who believed the job was “writing code”, for a few decades; those people got by thanks to Stack Overflow and the fact that most of the code that needed writing really didn’t need much skill anyway. There’s very little innovation or engineering in most business platforms - a couple of decent architects and an army of code monkeys can deliver most of the software that’s needed. We also developed programming languages and frameworks that made it much easier for the unskilled developers to be productive.

    Sad to say, these are the people now loudly wailing about the iniquities of AI. If you thought churning out code was the profession - you absolutely should be very concerned that AI will replace you - it will. But if you realised that code was only ever a side effect of the job, which was applying computing to solve problems - you have little to worry about. AI is just a new tool to do it, and is no more a threat than optimising compilers, mamaged runtimes or IDEs were.

    When I started my career, I wrote assembly code by hand for platforms that barely even had an operating system. Then C. Then Java - and as far as I’m concerned, every programming language since then has pretty much had training wheels permanently attached… For the last few years, I’ve preferred Rust, although the job has been more about developing architectures for others to implement than coding myself. But my expectation is that I’ll end my career writing instructions for AIs to implement; and that’s absolutely fine. The job didn’t change, just some of the intermediate representations I had to write to do it. The profession will probably go back to look more like the one I entered - fewer people doing it, but with more formal education in computer science, and much less “coding”.

    Which is not to say I don’t think there’s anything to worry about for the profession, there absolutely is. How the hell we identify the future senior engineers with the actual skill and aptitude required, when there are no junior roles to provide the necessary apprenticeship - and when the education system is struggling to adapt to AI use in class - is a massive and fundamental problem. That’s what keeps me awake at night, not people who think writing CRUD APIs in C# is a divine gift.