Reading Code Is Hard

re: Reading Code Is Hard

asdasdd — Fri, 29 Oct 2010 10:55:53 GMT

as<input type="text" />

Reading Code Is Hard, Part Two

Fabulous Adventures In Coding — Thu, 11 Oct 2007 21:38:41 GMT

I was thinking about this a bit more and talking with Larry Osterman yesterday, and I came up with some

Write-only variables considered harmful? Or beneficial?

Fabulous Adventures In Coding — Fri, 07 Sep 2007 01:30:22 GMT

I haven't forgotten that I promised to describe one more place where we insert an explicit conversion

Write Readable Code By Making Its Intentions Clear

Community Blogs — Fri, 20 Apr 2007 13:21:59 GMT

I don’t think it’s too much of a stretch to say that the hardest part of coding is not writing code,

Write Readable Code By Making Its Intentions Clear

you've been HAACKED — Fri, 20 Apr 2007 10:58:56 GMT

Write Readable Code By Making Its Intentions Clear

See Braidy Tester Read Code. Read, Braidy Tester, Read!

The Braidy Tester — Wed, 14 Jul 2004 18:45:00 GMT

Teaching the Skill of Reading Code

JeremyK's [MSFT] WebLog — Tue, 29 Jun 2004 08:03:00 GMT

re: Reading Code Is Hard

Petr Kadlec — Fri, 18 Jun 2004 12:56:00 GMT

And what about grep -w perfExecuteManifest ?

re: Reading Code Is Hard

Andrew Shuttlewood — Fri, 18 Jun 2004 11:58:00 GMT

If I get a lot of false positives (as above), you can chain the output of grep into another grep with -v

so

grep -r perfExecuteManifest | grep -v perfExecuteManifestInitialize >output.txt will prune them.

But I accept it's still an arse, you have to KNOW about all of the possible false positives before you can do this.

How do I debug a problem in someone elses code

Larry Osterman's WebLog — Thu, 17 Jun 2004 19:49:00 GMT