On Fri, Nov 26, 2010 at 1:00 AM, David Vasek <va...@fido.cz> wrote:
> /* Sorry for the noise, I simply couldn't resist. */
>
> Write in C ("Let it Be")
>
> When I find my code in tons of trouble,
> Friends and colleagues come to me,
> Speaking words of wisdom:
> "Write in C."
>
> As the deadline fast approaches,
> And bugs are all that I can see,
> Somewhere, someone whispers:
> "Write in C."
>
> Write in C, Write in C,
> Write in C, oh, Write in C.
> LOGO's dead and buried,
> Write in C.
>
> I used to write a lot of FORTRAN,
> For science it worked flawlessly.
> Try using it for graphics!
> Write in C.
>
> If you've just spent nearly 30 hours,
> Debugging some assembly,
> Soon you will be glad to
> Write in C.
>
> Write in C, Write in C,
> Write in C, yeah, Write in C.
> BASIC's not the answer.
> Write in C.
>
> Write in C, Write in C
> Write in C, oh, Write in C.
> Pascal won't quite cut it.
> Write in C.
>
Epic. You got more of these ? :)
