[erlang-questions] Support for newcomers and the popularity of Erlang

Jesse Gumm <>
Mon Mar 19 18:29:21 CET 2012


The obvious exception to inline code of course being long modules.

The benefit to short inline snippets is that it might gain attention of
someone more quickly, and from there you have him/her hooked. Then you can
start posting pasties and gists accompanied by long descriptions.

You have to catch the fish before you can filet it, so make the bait easy
to bite.

--
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866
www.sigma-star.com
@jessegumm
On Mar 19, 2012 12:17 PM, "Wojciech Knapik" <> wrote:

>
>
> On Mon, Mar 19, 2012 at 5:53 PM, Jesse Gumm <> wrote:
>
>> I think all of us have at some point or another posted something that had
>> no responses. I know I have.
>>
>> I find, especially in the mailing list context, that for members for whom
>> their best answer is "I don't know" you're less likely to get a response
>> than if it were a more traditional forum.
>>
>> Further, it really helps to pare down the question to its simplest form,
>> requiring the least amount of work from the members of the list. In my
>> case, I tend to make too-long narratives that require too much reading on
>> the part of the contributors who undoubtedly just mentally skip over it in
>> "tl;dr" fashion.
>>
>> When that happens, it's my fault for not asking the right question.
>>
>> So my general recommendation is to make an effort to ask concise
>> questions, and include code snippets directly in the post rather than
>> posting links to  pastebins, etc. (after all, link clicking is additional
>> effort).
>>
> Thanks, I'll keep that in mind. Concise questions and inline code from now
> on ;]
>
> WK
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120319/7146e74d/attachment.html>


More information about the erlang-questions mailing list