IMO the best way to use this crap in software development for projects that already exist is to have the fucking things write up or amend docs.
Developers mostly hate writing docs, and in corporate software I’ve found that the docs are usually added once and then never verified again.
Writing up profuse gibberish that contains some amount of useful information is what these bullshit machines were made to do. Have it write up some docs, read them and make sure they aren’t completely insane and get a pat on the back from your boss for working with “agentic AI”.
Good documentation makes me happy, bad documentation makes me run away. I suspect I’m not the only person who not only reads the fucking manual but thinks writing good technical documentation is an art of its own. Good luck with trying to replace proper documentation with profuse gibberish.
IMO the best way to use this crap in software development for projects that already exist is to have the fucking things write up or amend docs.
Developers mostly hate writing docs, and in corporate software I’ve found that the docs are usually added once and then never verified again.
Writing up profuse gibberish that contains some amount of useful information is what these bullshit machines were made to do. Have it write up some docs, read them and make sure they aren’t completely insane and get a pat on the back from your boss for working with “agentic AI”.
Good documentation makes me happy, bad documentation makes me run away. I suspect I’m not the only person who not only reads the fucking manual but thinks writing good technical documentation is an art of its own. Good luck with trying to replace proper documentation with profuse gibberish.
I mostly agree with this, but in corporate software the stuff mostly either doesn’t exist or is outdated to the point of basic inaccuracy.
I’m talking readmes that still have the template information in them or have stayed the same since the first commit.