PSA: make it easier to help you

This is a colorful metaphor, but I don’t understand how it applies here. A starving person is in danger of dying, while someone asking for help here and getting some pointers instead of a polished solution is in danger of… doing a bit of reading and thinking, I guess? I don’t consider either of those activities harmful.

In any case, my interest is mostly in helping people who wish to invest in learning Julia. What you describe is essentially free consulting, which I am not motivated to do. If you are, that’s great! I just sincerely hope that it never turns into an implicit or explicit expectation on this forum, because I suspect it would just make a lot of people quietly limit their involvement here (and I would be one of them).

I think that we have each clarified our positions, and this discussion is going in circles now. Note that this page is a wiki now, so anyone can edit it (I think). Feel free to add to it and make it more friendly; I would just appreciate if it was kept concise overall.


This place is the most helpfull and people here in general are the friendliest I ever experienced on any discussion board I have been in decades.

There are a very small number of some minor rudeness and not so friendly answers here to find, still those answers are targeted to help the questioner.

An even smaller number of participants seem to be offended (slightly or more or less) by some wordings which could be considered as rude or sloppy. Sure I do suppose these numbers are small, but at the end, this is all about technical questions and solutions, and not about psychological or mental issues.

It is possible to try harder and harder to even make the most sensitive people feel comfortable here, but at the end, there will be less people who will go through this effort and try to help the original technical question.

Nothing against more friendliness but it is more important to have fast and competent solutions. For this we need the technicians and nerds out there, who, in some cases :wink: , are missing some love and empathy for the one who asked the technical question but now got the technical solution.


OK, think instead that a new coworker says “I didn’t have lunch, I’m starving! What should I do for dinner?” If you send that person a link to LMGTFY “places to eat nearby” or hand him a fishing rod and a recipe book for cooking fish, that’s not a great response. There’s certainly a spectrum - you could say “this burger joint around the corner” or “come over to my house and I’ll cook for you.” To be clear, I think the vast majority of people on this forum (you included!) do these later things. I think you might say (yes, I realize this metaphor is getting super tortured), “Come over to my house - I’ve got all of the ingredients for a great meal, I’ll show you how to cook it,” which to be clear is super kind and above and beyond - you’re interested in people learning to cook for themselves, and that’s admirable (and again so I’m clear, from my perspective, your contributions here are constantly among the most useful on the forum). But for someone that was looking for options for fast food near work, this might seem a little aggressive.

Probably true. I’ve just made a couple of small edits to this end - take a look and let me know. I think it’s still quite concise, but adds just a little bit more social padding :slight_smile:.

Edit: should probably mention that I adapted @ElOceanografo’s text from here for the beginning.


It would be great if you did not try to base this discussion on stories and metaphors like this, because they are not very pertinent and just muddle the whole issue.

Eg a coworker is someone I have an ongoing cooperative relationship with in the workplace, enforced by social standards and the business culture of our common employer, which does not apply to most people on this forum. If you relate to total strangers you just met online and your coworkers the same way, that’s fine, I don’t.

Again, I am not sure I am decoding the metaphor correctly, but I don’t think that participating in a technical discussion in a civil manner, consistent with the community guidelines, can be construed as aggressive. We may just have to agree to disagree about this.

That said, I don’t think it is helpful to label behavior “rude” and “aggressive” (you have used both labels in this discussion) just because you would do it differently. The implication is that people who give help here, but do not go out of their way to be extra friendly by your standards, are rude and aggressive.


For example, when i see the first post of someone, i always start welcoming to this Discourse, and then i switch to response mode. If i have time, i try to untangle what the asker wants, if its possible and it’s in my attention budget, while also asking for more information and better formatting (in a lot of cases, the next comment is someone posting this thread). if there is enough information provided, then a preliminary response is made. iterate until solution is found.

Sometimes, even if no response can be given, and specially if its the asker’s first question, a post from someone in the community can make a difference, as essentially we are just people behind a keyboard (or smartphone).


I’ve shared an adaption of the post on the Go Forum. Thank you for the inspiration.


Cool! Nice to see this message spreading. Some formatting suggestions for the first point:

  1. If you put four spaces before paragraphs after the line break, including the code block, they will look like they’re of the same element of the ordered list.

    Like this.

    Or this
  2. For showing quoted code, wrap your example in 4 backticks, so that your triple backticks show up, like this:

    func add(x, y int) int {
        return x + y

    Tamas put a link in the original post of this thread to a different post about formatting discourse posts that’s super.


How about explicitly stating that a MWE sometimes or oftentimes can identify the source of evil itself?

1 Like

The original did contain something to that effect, but it was removed in edit 6 by @non-Jedi.

While there is a lot of useful advice that could be added to this post, I am still concerned that the longer we make it, the less of it will be read.

The post had been getting super long at that point, and I also removed a bunch of other stuff that might be considered helpful. The philosophy I employed was generally only to keep direct, actionable items and remove reasons/motivation and other commentary; the main reason that e.g. you should include a MWE is fairly obvious.

For what it’s worth, I have no personal objection to adding anything back in that people think is worthwhile, but I do believe that the longer the list gets, the less of it is actually read.

By the same token, the longer this thread gets, the less likely it is to be taken seriously by novices seeking help. How about splitting off the OP from the subsequent discussion?

Only the first post is meant to be read (the wiki part), the rest is discussion for that. Should we split it? I don’t know how wikis work on Discourse.

I agree with this. I think the items collected in this post (now a wiki, technically) convey the message rather well.

This is not meant to be a very detailed guide for every possible eventuality, just something that gets 90% of the common problems that prevent people from helping. FWIW, I am totally happy with people adding stuff, but even happier when they make it shorter. :wink:

My point was that this whole thread must look intimidating and confusing to a novice coming to the OP for advice. Threads have been split before, so I’m sure the top could be split off from the rest.


I am thinking about adding something along the following lines:

Instead of asking for translations of code in other languages (Matlab, Python, R, …) to Julia, it is recommended that you just explain what you are trying to do. This helps as it allows more people to respond (fewer people will know the other language well enough to understand what you are asking for); also, not all constructs have a direct mapping to Julia so context is useful.


I think this is a good point, but I might say “instead of just asking… it is recommended that you also explain…” Or something like that. I 100% agree with the sentiment, but having example code in a different language can often be helpful.

Then again this might undermine the clarity of the message, so feel free to disregard.

This seems like a specific kind of XY problem. Maybe better to just include a brief point requesting that they provide context for their question–what and why they’re trying to accomplish in an overall rather than local sense?

I’ve also been thinking: would it be better to simply link to something like Stack Overflow’s “How do I ask a good question” and limit this guide to things that are specific to Julia/this forum?

In principle, linking to a guide like that could work; in practice, I am not sure that the people who need it most would click through 2 links.

1 Like

I agree. And also, though I think that post has some useful guidance (and could be linked to at the end as “further reading” or something) your post has a bunch of additional julia- and discourse-specific stuff that I think is really valuable.

we should have a database of FAQs resolved and link new users if they have similar questions. in many cases, similar questions are asked and we don’t have a compilation of answers in one link to make the interaction faster and avoid redundant replies/troubleshootings.

Hmm I think that the search function and the “relevant topics” feature when creating a new post covers that already. I am always a bit reluctant to maintain multiple source of information.
Not sure if someone who does not utilise these existing features will find their way to an FAQ :see_no_evil:

1 Like