kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Introducing Myself, Looking to Learn
Date: Wed, 4 Sep 2013 07:22:14 +0200	[thread overview]
Message-ID: <20130904052213.GA4049@grml> (raw)
In-Reply-To: <alpine.DEB.2.02.1309031736160.7922@oneiric>

Hi!

On 17:44 Tue 03 Sep     , Robert P. J. Day wrote:
...
>  it's somewhat absurd to say you want to get involved in kernel
> development, then ask *others* where you should start.

I guess it sounds absurd because he missed how open source development
works:
1) Find something you do not like.
2) Try to understand what is going on.
3) Try to think of ways to solve it.
4) Ask for opinions.
5) Implement your solution.
6) Post it. Depending on how others react you might decide to redo parts or
   even start from scratch (or maybe even abandoning it). It could also
   happen that somebody else takes your idea and solves it in a different
   way. Bad things could happen as well, like everybody ignoring you because
   they do not care about your problem.

This is in contrast to school/work environments where others tell you what
you have to do.

> 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.

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com

  reply	other threads:[~2013-09-04  5:22 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 [this message]
2013-09-04 13:41             ` Valdis.Kletnieks at vt.edu
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=20130904052213.GA4049@grml \
    --to=michi1@michaelblizek.twilightparadox.com \
    --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).