Earlier quoted context omitted.
just last week AI led a developer on our team to brick our git history when he was attempting to fix a deploy. he's not a git expert but an llm should of not led him that far astray, no? i see on a weekly basis where if an llm was left to do what its initial direction was without human oversight it would have broken otherwise working programs
Your developer didn't have anyone reviewing the work he was checking in? Or he didn't have the common sense to ask anyone else on the team to verify?
Appearing productive in the workplace
681–686 of 686 posts
Re: Appearing productive in the workplace
#682Earlier quoted context omitted.
My colleague had a problem with commit messages, so now they're all written by AI. I don't know what depth of hell he managed to get the prompt from, but they're all now in the format "Updated /path/to/file: fixed issue in thingamabob", which means they're all at least 200 characters long and half of it is the file path, an absolutely pointless thing to put in a commit message. The best part is that whenever you look…
Out of curiosity, with it taking up that much of the message, is it the local file path on their computer?
Re: Appearing productive in the workplace
#683Earlier quoted context omitted.
I'm starting to see pushback for this. I know a Product Manager that was fired for padding his documentation with AI to the point there were mistakes and wasted work due to AI hallucinations.
we as a culture will gradually find a resting place here in regards to "proof of work" but it will be a painful decade in the meantime.
Nobody wants to consume slop.
Re: Appearing productive in the workplace
#684I spent most of yesterday, deleting and replacing a bunch of code that was generated by an LLM. For the most part, the LLM's assistance has been great. For the most part. In this case, it decided to give me a whole bunch of crazy threaded code, and, for the first time, in many years, my app started crashing. My apps don't crash. They may have lots of other problems, but crashing isn't one of them. I'm anal. Sue me. F…
Re: Appearing productive in the workplace
#685Earlier quoted context omitted.
I bought this book a year ago but have not read it. It's one of those books that requires effort from the reader, which these days seems in low supply for me. :) I'll have to give it another try. Recently I commented that: Artificial intelligence produces artificial results. I liked the double-artificial but I wasn't happy with the meaning. Perhaps Simulacra is more accurate? I will see :)
Results are results, though. By "artificial results" do you mean those that merely appear to be results, or do you mean results achieved via nonhuman means? If I write the exact same code as the AI, our results will be indistinguishable.
But I mean: they appear to be results. They look real, but are not. There are subtle errors hidden that the casual observer will not, or even cannot detect.
Obviously there are exceptions to this. Many exceptions. AI right now can probably write most if not all algorithms on par or better than I could. It can put together working prototypes for many ideas I've had and not had time to implement.
But the danger is in assuming that because it can do A, it can do B, because a human that does A can do B.
Re: Appearing productive in the workplace
#686Earlier quoted context omitted.
Reminded me of The Tao of Programming [1]. Fantastic little read that brightened my morning (during a boring meeting). [1]: https://www.mit.edu/~xela/tao.html
Love this! > The Master was explaining the nature of Tao to one of his novices. > > "The Tao is embodied in all software -- regardless of how insignificant," said the Master. > > "Is the Tao in a hand-held calculator?" asked the novice. > > "It is," came the reply. > > "Is the Tao in a video game?" asked the novice. > > "It is even in a video game," said the Master. > > "Is the Tao in the DOS for a personal computer?…