From 4ddf573d3fd8320e8f8c894d05ed3905968d9de5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bar=C4=B1=C5=9F=20=C5=9Eenyerli?= Date: Sat, 11 Mar 2023 11:58:06 +0300 Subject: [PATCH 1/2] fix: typo --- cleancodeqa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cleancodeqa.md b/cleancodeqa.md index ab16dd0..cc77b94 100644 --- a/cleancodeqa.md +++ b/cleancodeqa.md @@ -16,7 +16,7 @@ It is economically better for most organizations to conserve programmer cycles t **BOB**: No, it seems to me that an IDE is a very specialized software system. There are only a few in existence, and only a very few that have become popular. -IDE's are interesting systems in that they span a huge domain of contexts. There are portions in which nanoseconds are extremely important, and other parts where they matter very little. A modern IDE has to be able to parse large extents of code on a keystroke by kestroke basis. Making sure that the parsing code preserves nanoseconds can have a big effect. On the other hand, the code that sets up a configuration dialog does not need even a tiny fractioin of that kind of efficiecy. +IDE's are interesting systems in that they span a huge domain of contexts. There are portions in which nanoseconds are extremely important, and other parts where they matter very little. A modern IDE has to be able to parse large extents of code on a keystroke by kestroke basis. Making sure that the parsing code preserves nanoseconds can have a big effect. On the other hand, the code that sets up a configuration dialog does not need even a tiny fractioin of that kind of efficiency. And, as an aside, the kind of efficiency the compile engine of an IDE needs is more algorithmic than cycle-lean. Cycle-lean code can increase efficiency by an order of magnitude; but the right choice of algorithm can increase efficiency by many orders of magnitude. From 6c26ad1ae26da7d78db711e8ce74249c828922e2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bar=C4=B1=C5=9F=20=C5=9Eenyerli?= Date: Sat, 11 Mar 2023 12:04:49 +0300 Subject: [PATCH 2/2] fix: typo --- cleancodeqa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cleancodeqa.md b/cleancodeqa.md index cc77b94..a96ec8c 100644 --- a/cleancodeqa.md +++ b/cleancodeqa.md @@ -16,7 +16,7 @@ It is economically better for most organizations to conserve programmer cycles t **BOB**: No, it seems to me that an IDE is a very specialized software system. There are only a few in existence, and only a very few that have become popular. -IDE's are interesting systems in that they span a huge domain of contexts. There are portions in which nanoseconds are extremely important, and other parts where they matter very little. A modern IDE has to be able to parse large extents of code on a keystroke by kestroke basis. Making sure that the parsing code preserves nanoseconds can have a big effect. On the other hand, the code that sets up a configuration dialog does not need even a tiny fractioin of that kind of efficiency. +IDE's are interesting systems in that they span a huge domain of contexts. There are portions in which nanoseconds are extremely important, and other parts where they matter very little. A modern IDE has to be able to parse large extents of code on a keystroke by keystroke basis. Making sure that the parsing code preserves nanoseconds can have a big effect. On the other hand, the code that sets up a configuration dialog does not need even a tiny fractioin of that kind of efficiency. And, as an aside, the kind of efficiency the compile engine of an IDE needs is more algorithmic than cycle-lean. Cycle-lean code can increase efficiency by an order of magnitude; but the right choice of algorithm can increase efficiency by many orders of magnitude.