One side effect of LLM-everywhere dev I'm seeing is rejection of dependencies in favor of "bespoke everything." Today we...

One side effect of LLM-everywhere dev I'm seeing is rejection of dependencies in favor of "bespoke everything." Today we had some difficulty with a library not working quite right on target platform... co-worker pasted the LLM's "Most robust long-term fix" which was to reproduce / rewrite the troublesome function entirely within our code. (or, rather, the LLM would do it)I have been doing dev for a while and that does not seem a robust, long-term fix to me! It seems like a hack you'd do until either you figured the library issue out or support was added.But I also see in programming subreddits a common LLM tell, which is rewriting something (key-value store, console graphics gimmick, blockchain junk, etc) as "lightweight, no-dependencies." In C? They're doing HTTP from scratch with socket.h? I guess!In reality I suppose - many core algorithms are napkin-sized in pseudocode, so "easily" reproducible...#softwareengineering #softwaredevelopment #llm #ai