It's really harder to read... But in my opinion the main problem with old codes is that after many iterations, the code and its structure becomes a kind of Frankenstein. Also there's the fact that we're always evolving, and knowledge in general was more restricted in the past.
-
-
-
I think this comment captured it well "Quite literally no one knows everything about any such system - you have to take a systems approach, design for modularity, document like a graphomaniac, and expect constant rework"
- Još 1 odgovor
Novi razgovor -
-
-
It's the lack of context. While you write it you understand the concept and know what you want out of it. With other peoples' code or your own old code you need to invest mental energy into understanding it first, and we're just lazy to do it.
-
Yep, this is big. That, and the fact that thinking ideas is much faster than reading ideas. Just like there’s orders of magnitude between RAM / file / network operation speeds, there’s orders of magnitude of speed between thinking / reading / hearing.
Kraj razgovora
Novi razgovor -
-
-
Like the Netscape rewrite debacle, this keeps repeating itself endlessly in the software industry, whose history is markedly underrated.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
There's nothing wrong with rewriting code even if just to undertsand it. It makes it easier, because then you are not just reading. This blog post by
@peterseibel was a bit of an epiphany for me: http://gigamonkeys.com/code-readingHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I'm surprised this article never once covers the benefits of good documentation. If you make it easier to read and understand, it's suddenly more likely others will be able to adapt, improve, refactor, or enhance instead of throwing it all away.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Having complex thoughts on your own: easy peasy. Following a complex thought process and contributing to it: grab a snickers, you'll need that energy.
- Još 3 druga odgovora
Novi razgovor -
-
-
One of the reasons why is that devs often get themselves worked into a frantic hyper-focused (coffee, energy drinks, adderall, etc.) state which leaves them prone to spinning cobwebs, and then try to read code in a “normal” state where “hyperfocused brain” is a human dependency.
-
It’s similar to the quote commonly attributed to Einstein: “We cannot solve our problems with the same thinking that created them.” In order to effectively read unfamiliar code, you need to be in a mental state beyond what was required to write it.
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.
• Lighthouse, PageSpeed Insights, DevTools • Founder TeeJungle