Explore >> Select a destination
|
You are here 
|
egghead.io | ||
| | | | |
ezyang.github.io
|
|
| | | | | The Rule of Three in software says that you should be willing to duplicate a piece of code once, but on the third copy you should refactor. This is a refinement on DRY (Don't Repeat Yourself) accounting for the fact that it might not necessarily be obvious how to eliminate a duplication, and waiting until the third occurrence might clarify. (See also The Wrong Abstraction.) LLMs love to duplicate code. Think about how, absent any other prompting, if you ask an LLM to modify a program, it will spit out a new copy of the program with the changes requested. For an LLM to decide to refactor code to remove duplication requires a moment where the LLM proactively decides to go out of their way to do some cleanup. (Actually, Sonnet 3.7 also has some of this inclinat... | |
| | | | |
blog.lmorchard.com
|
|
| | | | | [AI summary] The author developed a browser-based Breakout game using Phaser 3, documenting the AI-assisted coding workflow with Claude, and plans to expand it into a presentation. | |
| | | | |
jamubc.github.io
|
|
| | | | | Bridge Gemini models with Claude Desktop | |
| | | | |
www.uptycs.com
|
|
| | | Learn about the latest CUPS vulnerability in Linux systems, which poses a remote code execution risk. Discover mitigation strategies to secure your environment. | ||
