Fully agree. Replace code gradually over time, testing each change against real-world data. Feels slower, but in reality you are just solving the difficult real problem instead of the easy imaginary one.https://twitter.com/bagder/status/1360133869433999362 …
-
Näytä tämä ketju
-
Note that this is different from "I just want to make this cleaner" refactoring, which has very little value IMO. Changes should all be moving toward a larger goal.
1 vastaus 0 uudelleentwiittausta 2 tykkäystäNäytä tämä ketju -
Vastauksena käyttäjälle @JJcoolkl
There is an adage that goes "write code that's easy to delete." and I think it's very useful here. I like to write with clear lines between "modules" of code, making replacing a part of it easy. A "complete rewrite" of a submodule is "incremental" on the whole.
1 vastaus 0 uudelleentwiittausta 2 tykkäystä -
Vastauksena käyttäjälle @tloch14
You are describing our entire engine! Of course, this gets tricky to do with things that get used in a lot of places, like a math library.
2 vastausta 0 uudelleentwiittausta 1 tykkäys
I was almost going to expand about how hard some things can be to replace, depending on the API necessitated by what it is (your right, math lib is a great example), so I'm glad you pointed it out. Do it when you can, be okay with it when you can't.
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.