memory-leaks

Still reachable: lots of words in many pages.
git clone https://git.kevinlegouguec.net/memory-leaks
Log | Files | Refs | README | LICENSE

commit a3bd3c43fa8faa9c0fe6aaa6dfa02e3d3d8bdbb9
parent c3e13f4ede83d4ea4047f100a26a7f1a08720879
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Sat,  4 May 2019 22:37:55 +0200

Fix typo

Diffstat:
Mtechnical/reviews/talks.md | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/technical/reviews/talks.md b/technical/reviews/talks.md @@ -38,8 +38,8 @@ programmer starting to apply these rules: the programmer wonders when they will be able to understand the new application "the same way" they understood the old one. I.e. will they ever reach a point where they have a complete mental map of every interaction between every -object, the same way the used to have a complete mental map of the old -monolithic, sequential application? +object, the same way they used to have a complete mental map of the +old monolithic, sequential application? Metz's response is that nope, this will never happen; they will "cease to care" instead. In exchange, they will be able to make localized