Tag Archives: code

Maintenance

Though a program be but three lines long, someday it will have to be maintained.

The Tao of Programming


iOS 4.1 security flaw

Brian X. Chen at Wired (http://www.wired.com/threatlevel/author/brian-x-chen-2/) reports a security flaw that allows bypassing iPhone code lock: simply “[…] tap the “Emergency call” button, then enter three pound signs, hit the green call button and immediately press the lock button. That simple procedure gives a snoop full access to the Phone app on the iPhone, which contains the address book, voicemail and call history […] (Full article http://www.wired.com/threatlevel/2010/10/iphone-snoop/).

🙂 also Apple has some funny things to do without jailbreaking…


Commenting code like real programmers

Real programmers don’t comment their code.  If it was hard to write, it should be hard to understand.

Anonymous coder


Bugs and features

There are no bugs, only unrecognized features.

Anonymous coder


The sense of virtualization

“Virtual” means never knowing where your next byte is coming from.

Anonymous coder


Patches for code

Don’t patch bad code, rewrite it.

Anonymous coder


Drunk coding

Never program and drink beer at the same time.

Anonymous


On code and comments

Make sure comments and code agree.

Anonymous


Laws of debugging

  1. Don’t comment or patch bad code; rewrite it.
  2. Don’t compare floating point numbers solely for equality.
  3. Don’t diddle code to make it faster; find a better algorithm.
  4. Don’t document the program; program the document.
  5. Don’t stop at one bug.
  6. Every bug you find is the last one.
  7. Every program is either trivial or it contains at least one bug.
  8. In God we trust; all else we walk through.
  9. Know Thy User.
  10. Let the machine do the dirty work.

Anonymous


Bugs and documentation

A bug in the code is worth two in the documentation.

Anonymous


%d bloggers like this: