From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Introducing Myself, Looking to Learn
Date: Wed, 04 Sep 2013 09:41:42 -0400 [thread overview]
Message-ID: <49492.1378302102@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 04 Sep 2013 07:22:14 +0200." <20130904052213.GA4049@grml>
On Wed, 04 Sep 2013 07:22:14 +0200, michi1 at michaelblizek.twilightparadox.com said:
> 1) Find something you do not like.
Exactly. This is the point a lot of people miss.
Personally, I mostly stick to "badly written Kconfig entries" and
"stuff in linux-next that makes my Dell laptop misbehave", because
that's stuff I can actually test/report/fix, and stuff that ticks me off. ;)
> > it's like
> > saying, "i really want to write a book, but i have no idea what i
> > should write about. can you give me some ideas for a plot? and
> > characters? and possibly an ending?" yes, it's that silly.
>
> Isn't this called "writer's block"? To me this does not sound like a silly
> thing to say at all.
Writer's block is when you can't find a rhyme for the 23rd line, or can't
figure out how to make your villain drop out in chapter 5 so he can re-appear
in chapter 9. If you need ideas for plot, characters, and ending, you're
not a writer.
Horror writer Steven King was once asked "Why do you write such dark scary
stuff?". He replied "What makes you think I have any choice in the matter?"
Now that dude is a *writer*.
And quite frankly, unless somebody have similar feelings about coding, they
probably shouldn't be hacking the kernel.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130904/2aab0075/attachment.bin
next prev parent reply other threads:[~2013-09-04 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SNT146-W615B5F3B1F38B082C8AB4DC8310@phx.gbl>
2013-09-03 19:29 ` Introducing Myself, Looking to Learn Varad Gautam
2013-09-03 20:22 ` Valdis.Kletnieks at vt.edu
2013-09-03 20:35 ` Varad Gautam
2013-09-03 21:24 ` Valdis.Kletnieks at vt.edu
2013-09-03 21:44 ` Robert P. J. Day
2013-09-04 5:22 ` michi1 at michaelblizek.twilightparadox.com
2013-09-04 13:41 ` Valdis.Kletnieks at vt.edu [this message]
2013-09-05 10:06 ` María Soler Heredia
2013-09-04 13:55 ` Valdis.Kletnieks at vt.edu
2013-10-28 10:40 ` Matthias Brugger
2013-11-14 3:50 ` Anand Moon
2013-09-04 1:00 ` Augusto Mecking Caringi
2013-09-04 1:33 ` Arlie Stephens
2013-09-04 2:28 Rakesh Ganimineni
2013-09-04 2:44 ` Greg Freemyer
2013-09-04 13:11 ` Varad Gautam
2013-09-04 13:06 ` Varad Gautam
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=49492.1378302102@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).