People often say “every code becomes legacy code” but that’s not true. Only successful code becomes legacy code. Let that sink in.
-
-
But other than that, yes, that's right. And it connects to project management. A fundamental flaw when transferring traditional project management theory to software is: Traditional projects are successful when they end. Most SW projects are successful when they continue.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I like the definition "legacy code is code we are afraid to change". But more fluffy though

-
I like that, too. These two definitions have quite a lot in common. The reason for defining it as "code without tests" is the fear of change in the absence of tests.
- Još 2 druga odgovora
Novi razgovor -
-
-
I have seen code with tests you don’t want to touch and I have seen code without tests that can be modified (and when necessary tests can be written).
-
Same. I’ve also seen a tortoise eating a taco. The lettuce, mostly.
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.