a similar ruling will also be a disaster for software as our tools of expression are very restricted. code is based on boolean algebra and predicate calculus, practice guides like design patterns and books teaching algorithms and data structures.

there are lots of ways to write bad code and only a few for good, correct code. Recognizing this led me to replicating known working code, code I had created, for multiple employers. so who's copyright did I intentionally violate?

I think we are attacking the wrong problem WRT ML and copyright. to me, ML shows the foundation on which copyright is built is a lie. we should use ML to break copyright for code.

For example, the "clean-room design" method of copying a work exists precisely to avoid potential copyright issues. One team reads the original work and writes a description in such a way that it cannot possibly be infringing, and a second team reads the description and creates the new work. This avoids any chance of someone reading the original work and incorporating potentially infringing aspects into the new work.