From: "Lluís Batlle" <viriketo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] not understanding bugs.
Date: Thu, 29 Jan 2009 18:42:22 +0100 [thread overview]
Message-ID: <45219fb00901290942l7f1b649bx945df30fdc6aed6a@mail.gmail.com> (raw)
In-Reply-To: <8b2aa58f3e8a4b5ff62cca0f851b17b0@quanstro.net>
Same here. I totally feel like erik about bugs and writing code.
2009/1/29 erik quanstrom <quanstro@quanstro.net>:
> from the link
>
>> But that's what happens when there is no incentive
>> for people to do the parts of programming that aren't fun.
>> Fixing bugs isn't fun; going through the bug list isn't fun;
>> but rewriting everything from scratch is fun (because "this time
>> it will be done right", ha ha) and so that's what happens, over and over again.
>
> something must be wrong with me. i like fixing bugs.
> writing a big pile of code always seems daunting.
>
> - erik
>
>
next prev parent reply other threads:[~2009-01-29 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 17:36 erik quanstrom
2009-01-29 17:42 ` Roman V. Shaposhnik
2009-01-29 17:42 ` lucio
2009-01-29 17:42 ` Lluís Batlle [this message]
2009-01-29 22:51 ` jimmy brisson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45219fb00901290942l7f1b649bx945df30fdc6aed6a@mail.gmail.com \
--to=viriketo@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).