Difference between revisions of "How You Can Help"

From D Wiki
Jump to: navigation, search
(How you can help with D)
Line 15: Line 15:
  
 
Andrei
 
Andrei
 +
</blockquote>
 +
 +
 +
== how to better promote your own D projects ==
 +
 +
<blockquote>
 +
I hate the movie "Field of Dreams" where they push the idiotic idea of "Build it and they will come." No, they won't. There's a blizzard of stuff competing for their attention out there, why should they invest the time looking at your stuff? You need to tell them why!
 +
 +
Here's the frustrating typical pattern I've seen here for years:
 +
 +
1. spend hundreds if not thousands of hours developing something really cool
 +
2. spend 2 minutes posting a link to the repository on D.announce
 +
3. someone posts it to reddit. Ignore it
 +
4. get frustrated that nobody looks at it
 +
5. get bitter and quit
 +
 +
Here's the pattern that works a lot better:
 +
 +
1. spend hundreds if not thousands of hours developing something really cool
 +
2. spend 10 minutes writing the announcement to D.announce. Be sure to include:
 +
  who, what, where, when, why, and how
 +
3. someone posts it to reddit
 +
4. post the who, what, where, when, why and how on reddit AS SOON AS POSSIBLE after the reddit link appears. Stuff on reddit has a VERY SHORT shelf life. If it doesn't get action within a couple hours, it fades into oblivion. Identify yourself as the author, say AMA. The first one to post a comment tends to spark and set the tone for the discussion.
 +
5. check back on reddit once an hour or so for the next day, answer questions
 +
6. *****
 +
7. profit!
 +
 +
Walter Bright
 
</blockquote>
 
</blockquote>

Revision as of 07:56, 19 August 2015

Documentation

  • std.algorithm - see forum

Wiki

  • We need D as a second language sections completed
  • C and C++ need updating
  • we need more examples of how to shift idiom to speak fluent D
  • the Python page is started but needs fleshing out
  • and most of the other sections are empty.

One note about Walter's older C/C++ transition articles. They have good information on transition technicalities (e.g. "how do I do this thing in D that I used to do in C++?") but not a lot about the changes in coding style - making object copying not arbitrarily expensive, choosing struct vs. class, preferring pipelines and lazy to eager computation, etc. From what I see some folks come from C++, write their first D program in a stilted C++ idiom, and are left with the impression that the work is not worth the trouble.

Andrei


how to better promote your own D projects

I hate the movie "Field of Dreams" where they push the idiotic idea of "Build it and they will come." No, they won't. There's a blizzard of stuff competing for their attention out there, why should they invest the time looking at your stuff? You need to tell them why!

Here's the frustrating typical pattern I've seen here for years:

1. spend hundreds if not thousands of hours developing something really cool 2. spend 2 minutes posting a link to the repository on D.announce 3. someone posts it to reddit. Ignore it 4. get frustrated that nobody looks at it 5. get bitter and quit

Here's the pattern that works a lot better:

1. spend hundreds if not thousands of hours developing something really cool 2. spend 10 minutes writing the announcement to D.announce. Be sure to include: who, what, where, when, why, and how 3. someone posts it to reddit 4. post the who, what, where, when, why and how on reddit AS SOON AS POSSIBLE after the reddit link appears. Stuff on reddit has a VERY SHORT shelf life. If it doesn't get action within a couple hours, it fades into oblivion. Identify yourself as the author, say AMA. The first one to post a comment tends to spark and set the tone for the discussion. 5. check back on reddit once an hour or so for the next day, answer questions 6. ***** 7. profit!

Walter Bright