50% of C++ development seems to be worrying over the 95% of use-cases your tiny, isolated, never-to-be-reused piece of code will never see and adding complexity to handle it. Then trying to "abstract" those problems away with more layers of complexity.
-
-
“Optimize for refactoring” where can I read more about techniques for this?
-
I don't know anything specifically. But focus on: -Fewer levels of abstraction. Have all the information right there in one place. -Good naming, good comments. Comment on what you DIDN'T do and why. -Lots and lots of asserts. You WILL screw up. Let the machine help when you do.
- Još 1 odgovor
Novi razgovor -
-
-
83% of all statistics are made up on the spot.
-
It's true - though I did do a quick look at one codebase history and the number was certainly up there.
- Još 1 odgovor
Novi razgovor -
-
-
Always think of making you code usable before making it reusable.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Optimize for code boundaries !
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
and many times the only reason it gets rewritten is because someone else decided it was "ugly"
- Još 1 odgovor
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.