Hello, Gary,
On Mon, 1 Jun 2015 13:16:51 -0700
"'Gary Campbell' gary_at_numin8r.us [fc-solve-discuss]"
<fc-solve-discuss_at_yahoogroups.com> wrote:
> I’ve always found that reading someone’s code to find out what they are doing
> is kind of like looking at a wave form to find out what they are saying, or
> maybe at a memory dump of pixels to find out what they are writing. So I
> think I’ll pass. But I do remain curious.
>
Well, the Joel on Software did note that "Reading code is harder than writing
it":
http://www.joelonsoftware.com/articles/fog0000000069.html
However, like he noted in that and in the sequel article -
http://www.joelonsoftware.com/articles/fog0000000348.html , it is a useful
skill to acquire and prevents you from completely rewriting your code every so
often which is risky and costly.
As opposed to machine code, source code is meant to be human-readable, and some
people can make sense out of machine code too using disassemblers and debuggers.
Also see
http://shlomifishswiki.branchable.com/Self-Sufficiency/ .
Regards,
Shlomi Fish
--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
Buffy Factoids - http://www.shlomifish.org/humour/bits/facts/Buffy/
Sophie: Let’s suppose you have a table with 2^n cups…
Jack: Wait a second! Is ‘n’ a natural number?
Please reply to list if it's a mailing list post - http://shlom.in/reply .
Received on Tue Jul 14 2015 - 06:57:50 IDT