videlalvaro · August 29, 2015 14:19
diff --git a/gistfile1.txt b/gistfile1.txt
 REASON FIVE: You’ve found a bug in Cairngorm.

 If you find a bug in Cairngorm, there’s a really good chance it’s too
 early for you to be using it in mission critical projects. I state
 this with confidence, because many years ago I was a C developer who
 kept finding bugs in Kernighan and Ritchie’s C compiler. Every day,
 I’d find something wrong with the compiler – in fact, come to think of
 it, I think I was responsible for finding some real clangers in the
 Pascal compiler on SunOS as well, back in the day.

 Well, I say bugs … more often than not (in fact, come to think of it I
 don’t think I’ve ever successfully filed a bug against a compiler)
 they turned out not to be bugs. But they almost were … had it not been
 for the mistake that *I* had made! In fairness, I think Ali found a
 bug in the Java compiler once, but then he also refused to allow
 iteration::two to accept a tax refund from Inland Revenue, because he
 found a flaw in their calculations when we were subjected to a routine
 VAT inspection. It takes a special kind of pedant to find bugs in
 compilers, and flaws in Inland Revenue VAT calculations. Hope that
 this isn’t you.

 Seriously; I don’t want to suggest there haven’t been bugs in
 Cairngorm, and when we’ve been through early betas, like any other
 software products, we’ve allowed the occasional bug to slip
 through. However, the Cairngorm releases that we make publically
 available, compiled as SWCs … we use those a lot. We eat our own
 dogfood. There are a lot of folks in the community using them, and if
 you can’t get the basic login sample that we ship to work then I’ll
 hazard a guess that it’s a flaw in your system setup, not a bug in
 Cairngorm.

 If you’re getting frustrated that you’ve found a bug in Cairngorm, and
 you don’t know what the error message means – there’s a pretty good
 chance that a little bit more time spent up at REASON ONE, writing
 some more sample applications and experiencing compiler errors while
 you take your baby-steps, will help you steam past the configuration
 problems you’re probably experiencing with your particular Cairngorm
 sample application.

 from:
 http://web.archive.org/web/20060901102626/http://weblogs.macromedia.com/swebster/archives/2006/08/why_i_think_you.cfm
	REASON FIVE: You’ve found a bug in Cairngorm.

	If you find a bug in Cairngorm, there’s a really good chance it’s too
	early for you to be using it in mission critical projects. I state
	this with confidence, because many years ago I was a C developer who
	kept finding bugs in Kernighan and Ritchie’s C compiler. Every day,
	I’d find something wrong with the compiler – in fact, come to think of
	it, I think I was responsible for finding some real clangers in the
	Pascal compiler on SunOS as well, back in the day.

	Well, I say bugs … more often than not (in fact, come to think of it I
	don’t think I’ve ever successfully filed a bug against a compiler)
	they turned out not to be bugs. But they almost were … had it not been
	for the mistake that I had made! In fairness, I think Ali found a
	bug in the Java compiler once, but then he also refused to allow
	iteration::two to accept a tax refund from Inland Revenue, because he
	found a flaw in their calculations when we were subjected to a routine
	VAT inspection. It takes a special kind of pedant to find bugs in
	compilers, and flaws in Inland Revenue VAT calculations. Hope that
	this isn’t you.

	Seriously; I don’t want to suggest there haven’t been bugs in
	Cairngorm, and when we’ve been through early betas, like any other
	software products, we’ve allowed the occasional bug to slip
	through. However, the Cairngorm releases that we make publically
	available, compiled as SWCs … we use those a lot. We eat our own
	dogfood. There are a lot of folks in the community using them, and if
	you can’t get the basic login sample that we ship to work then I’ll
	hazard a guess that it’s a flaw in your system setup, not a bug in
	Cairngorm.

	If you’re getting frustrated that you’ve found a bug in Cairngorm, and
	you don’t know what the error message means – there’s a pretty good
	chance that a little bit more time spent up at REASON ONE, writing
	some more sample applications and experiencing compiler errors while
	you take your baby-steps, will help you steam past the configuration
	problems you’re probably experiencing with your particular Cairngorm
	sample application.

	from:
	http://web.archive.org/web/20060901102626/http://weblogs.macromedia.com/swebster/archives/2006/08/why_i_think_you.cfm