1) Write readmes in Markdown for each significant subfolder, as an intro that any git repo web browser now renders.
2) Pick an IDE, or second IDE, for code reading & navigation. eg @jetbrains suite using @appcode for Swift and C++
-
-
-
I see it differently. Because we do not talk about how we read code, we take reading for granted. Still, your system is not made of text. It is made of data, and data should be manipulated through tools like queries or visualizations.
- Još 10 drugih odgovora
Novi razgovor -
-
-
Before you can read code it has to be written. So is it really about optimizing the way you read code or the trade offs during writing code that make reading it hard? E.g. giving up on pressure from your manager to release without proper refactoring.
-
Optimizing the way you read, or better yet, the way you do not read, is a highly relevant problem with returns on investments in the short term.
- Još 3 druga odgovora
Novi razgovor -
-
-
Highly recommend all of
@CoolSWEng books on this, "Code Reading" and "Code Quality" particularly. -
Those are interesting. Still code is to be understood enough to figure out what to do next. Reading should be but one way to achieve that, to be used mostly when details matter.
- Još 5 drugih odgovora
Novi razgovor -
-
-
Truth, code is read infinitely more times than it’s written.
-
That’s why you should stop relying on reading as the primary way to extract the necessary information from it. Instead approach it as data.
- Još 12 drugih odgovora
Novi razgovor -
-
-
Amen to this statement!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
That's true
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Č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.