Developer and refugee from Reddit

  • 1 Post
  • 33 Comments
Joined 3 years ago
cake
Cake day: July 2nd, 2023

help-circle






  • Fight.

    The only thing - the only thing - these fucking oligarchs care about is money. That’s it. Nothing else. Not even their own lives. Money is all. So deny it to them.

    Buy used computer equipment. Never new. Stop using Google. Stop using Amazon. Definitely 100% stop using ChatGPT, Claude, or any other LLM. If you feel you have to use an AI model for some reason, save up and invest in a machine capable of running small models locally.

    Make the AI companies bleed. And at the same time, reward other companies that do the right thing. That want to sell something other than dumb terminals with AI wired in.

    I mean, fuck, there are plenty of companies that hate this shit too, because it destroys their businesses. Not their business models, their actual fucking businesses. No game developer or PC manufacturer is any happier with these AI monsters eating all the RAM than we are. They know if it persists it’ll put them out of business. It’s not like Dell or HP wanted to just stop being able to sell hardware.






  • I feel like I’m being gaslit as I keep reading that there are developers that feel they successfully offloaded the task of coding.

    That’s because you are being gaslit.

    The people making those claims are either a) not developers in the first place, with no awareness of just how shit the “products” they’re pushing are, b) paid astroturfers trying to prop up AI, or c) former actual developers who’ve become addicted to the speed that’s possible with AI who are downplaying how crappy their own code quality has become because they have no familiarity with their codebase anymore and have forgotten how to do so much as a for loop.

    All these people claiming 10x or 100x gains, and everything they’re making is garbage no one should or would touch with a ten-foot pole.



  • No, I don’t mean writing all the boilerplate. It’s simpler than that.

    Just to take a random example, let’s say the throwaway project you decide to do is build a custom button component in Angular. The steps would be something like this:

    1. ng new buttons
    2. (Answer prompts)
    3. cd buttons
    4. ng serve
    5. (Create a custom button component in the new project)

    I chose Angular because these days the CLI for it does almost everything for you. It’s absurdly easy, and is the sort of thing it may actually be slower to ask an AI to do, because the AI will absolutely try to create a bunch of things in the project itself rather than through the CLI. And it will use Angular patterns from 2024 rather than anything current (such as Signals), because of its training data.

    Not only is doing something like this (in whatever language you prefer) good practice for keeping your practical skills, it’s a good reminder that AI is only one tool in the toolbox. If it becomes your only tool, well… The old saying about how if all you have is a hammer everything looks like a nail applies.


  • Leet code is good for making sure you still have a good grasp of programming conceptually, but I don’t think it’s good for testing your own practical skills.

    Seriously, just take an hour or two to scaffold out something new. Doesn’t have to be complicated, just something to confirm for yourself that you can still do it. The only rule is to do it without AI.

    When I did it myself, it was after months of my work requiring me to use AI, and there was a moment at the start where I was tempted to just fire up Copilot and tell it to do the work, which - of course - would have defeated the purpose. It was that moment where I realized I was addicted, and needed to go cold turkey.

    Now I do the bare minimum with AI I’m required to at work, and focus on crafting my code carefully, by hand as much as possible. And it shows. My code quality has improved.



  • It’s almost certainly also making your code worse.

    It’s not impossible to use AI effectively (although I would argue it’s impossible to use large “frontier” models ethically, as the companies making them are burning the planet down to power the process), but you have to be extremely vigilant and thoughtful about what you’re using it for, and you have to review every single line of code it produces, or you’re going to miss bugs and you’re going to lose skills.

    A good way to test yourself is to see if you can still scaffold out an application by hand. Doesn’t matter what… A to-do list, some buttons, whatever. Just test yourself to see if you can still do it.

    If you can’t, then you’ve lost the skills necessary to be certain that what you’re producing with AI is actually good.

    And if the idea of testing yourself like this makes you uncomfortable? Then AI isn’t a tool you use, it’s an addiction.