Twonks | Bluesky

Transcript

TW😶NKS

A comic in four panels:

Panel 1. White text on black

AI Design Logic

Panel 2. A guy sits in a restaurant at a table with a checkered table cloth. A waiter stands near, hands behind back waiting attentively.

Guy: Get me a cheese pizza

Panel 3. The waiter returns with a pizza in hand.

Panel 4. The guy gestures proudly at the pizza. The waiter looks less than amused.

Guy: Wow, look what I made!

  • lime!@feddit.nu
    45·
    10 hours ago

    you know, i’ve tried to defend some usage in the past, explaining my processes and the many steps of manual refinement, masking, and layerwork i put in to things, how i only run local models with open weights, how all my power comes from hydro etc etc

    but as the tools keep evolving i’ve realised nobody else seems to actually care about the process. the pro-people just want as much slop as possible. someone likened it to a slot machine, where you keep pulling just because. that’s where we are now.

    • Flames5123@sh.itjust.worksEnglish
      6·
      4 hours ago

      I fully get where you’re coming from. I fully believe that you can’t vibe code correctly unless you already know how to code correctly. I’m against the shifting paradigm of “who cares what the code looks like aa long as it works properly and the LLM can read it quickly” bullshit that’s coming out of it. I want to read the code and understand it too. I want it to be object oriented and not just dumb ad hoc methods everywhere that’s 1,000 lines when it could’ve been 100 lines.

      Now anecdotally, as someone who uses it for my main work and side project, I am still getting a lot of use out of it. I’m learning new things at a faster rate than I would have before. For my side project, I am trying to optimize gear sets for a game and there’s hundreds of millions of different configurations. The LLM I’m using knows about my code and the project and what I need and is able to suggest other algorithms, like I was able to learn about Dinkelbach’s algorithm. I have it write up design docs with formulas and pseudocode implementation and I review that and it takes my comments into account. I treat it like a junior developer and ask for questions to make sure I understand what it’s doing. I think a lot of people aren’t treating it like a junior developer or intern and that’s where problems come from.

      Now, I wouldn’t be using it if it wasn’t free with my company, as this is more of “learning/research” for my job.

      And for my job, we have semantic memory and a ton of MCP servers setup that guide it through the right code and can do internal documentation search so it’s way more powerful than just using base Claude Code or whatever. It has helped me stay more on track with my projects as an ADHD person (even though I’m medicated) by documenting what it does after it does it in a shared doc rather than me forgetting to do that because I run a command and log off for the day or something.

      I do hate the water usage and energy usage though…