Explore >> Select a destination
|
You are here 
|
seanmcp.com | ||
| | | | |
ezyang.github.io
|
|
| | | | | Preparatory Refactoring says that you should first refactor to make a change easy, and then make the change. The refactor change can be quite involved, but because it is semantics preserving, it is easier to evaluate than the change itself. Current LLMs, without a plan that says they should refactor first, don't decompose changes in this way. They will try to do everything at once. They also sometimes act a bit too much like that overenthusiastic junior engineer who has taken the Boy Scout principle too seriously and keeps cleaning up unrelated stuff while they're making a change. Reviewing LLM changes is important, and to make review easy, all of the refactors should happen ahead of time as their own proposed changes. | |
| | | | |
hamatti.org
|
|
| | | | | Debugging is a key skill for any developer. I wrote this guide for frontend developers to up their skills in finding out issues and fixing them in their codebase. | |
| | | | |
dorotac.eu
|
|
| | | | | ||
| | | | |
akashgoswami.dev
|
|
| | | A quick overview of what I plan on using this website for | ||
