[–] 7 points 9 months ago (2 children)

It’s not negative that nobody understands the spaghetti code, it’s advanced optimized code that mere mortals can’t comprehend, and marketing can sell that.

Don’t forget to bill by the hour to clients for bug fixes. 

  • source
  • parent
  • context
  • [–] 7 points 9 months ago (1 child)

    This. 

    They’re incredibly useful, but you have to treat their output as disposable and untrustworthy. They’re reinforcement trained to generate a solution, regardless of if it’s right, because it’s impossible to AI evaluate that these solutions are correct at scale.

    If you’re writing some core code: you can use an agent to review it, refactor parts, stump the original version, infill methods, and to run your test/benchmark scripts. 

    but you still have to manage it, edit it, make sure it’s not recreating the same code in 6 existing modules, generating faked tests, etc. 


    As an example this week on my side project I had Claude Opus write some benchmarks. Total throwaway code.

    It actually took my input files, generated a static binary payload from it using numpy, and loaded that into my app’s memory (on its own that’s really cool), then it ran my one function and declared the whole system 100x faster than comparable libraries that parse the original data. Not a fair test at all, nor was it a useful test.

    You cannot trust this software. 

    You’ll see these games metrics, gamed tests, duplicate parallel implementations, etc. 

  • source
  • parent
  • context
  • [–] 7 points 9 months ago (5 children)

    Nah, we need to optimize the spaghetti code with an n8n optimization pipeline for more spaghetti, lets make sure to build a new library for eache seperate function call. Once the function has run we'll tear down that library and build the next, if it errors out that's fine, we can just have the GPT hallucinate another library and call that into the function. It's fungible OOP all the way down. Infinite code is infinite tech debt, I call that job security.

  • source
  • parent
  • context
  • [–] 13 points 9 months ago (1 child)

    Prompt: "write a python script to create a thousand linkedin accounts with plausible sounding names, and then setup a cronjob to post every day a punchy linkedin just-so story explaining why everyone should be paying for my LLM and to keep paying for it when I jack up the price 100x to cover my expenses"

  • source
  • [–] 6 points 9 months ago (1 child)

    I think my management is decent about receiving feedback, but are also very into AI utilization right now. I’m not sure what level of feedback to give, because I do feel being too obstinate and negative would mark me, and with my adhd I often dont have a good read on where that line is. But I’d love to press them on where it will stop being worth it to keep pushing it? When the venture capital dries up? Climate/local data center regulations finally get implemented? Because those will all drive token cost up by a lot

  • source
  • [–] 17 points 9 months ago (6 children)

    The 1st major project in my first coding job made me understand technical debt even though I didn't know the name of it.
    I suppose there are some people that just see spaghetti code and their only thought is to add more spaghetti code. Thankfully I also understood spaghetti code with my project in uni.

  • source
  • parent
  • context
  • [–] 65 points 9 months ago (6 children)

    My sister-in-law is a software engineer and project manager. This isn't groundbreaking news or anything but she said that her engineers are using generative AI like this. The problem is that it created exceedingly inefficient and bloated code that barely works. En masse it will bog down systems due to the exponential inefficiencies.

    It's fine. Everything is fine.

  • source
  • view more: ‹ prev next ›