56
Best way to sabotage AI at work?
(hexbear.net)
Ask Hexbear is the place to ask and answer ~~thought-provoking~~ questions.
Rules:
Posts must ask a question.
If the question asked is serious, answer seriously.
Questions where you want to learn more about socialism are allowed, but questions in bad faith are not.
Try !feedback@hexbear.net if you're having questions about regarding moderation, site policy, the site itself, development, volunteering or the mod team.
This is amazing because all of this is entirely useless at best and actively hostile at worst, but it's all exactly the kinda thing the morons pushing LLMs want. This is 100Xing tech debt generation, all features no maintenance.
I kinda hate my current job, but at least I'm the only dev and the entire codebase is my own handwritten slop. Refusing to use AI at any point has basically allowed me to minimize feature creep and force all our tooling to fit in a decently modular home baked framework that only takes up ~100MB for the whole history and around 60K lines of active code (split I over about 4 or 5 separate open source repos I'm maintaining).
Half of my commits now are deleting huge portions of the codebase since I've noticed they aren't used, or have been replaced over the years by better solutions. All of this runs the entire project management, design and QA suites for a 60 person fiber optic design firm.
I do have a habit of just deciding to delete modules and waiting for tickets to flow in then rewriting them on the fly, but there's no better way to find out if something is important than deleting it in prod and waiting for complaints lol