> You might be interested to google "fundamental attribution error".
After a briefly read on Wikipedia, I'm glad you pointed that out. I'll
read more.
Any other comment I could make on that seems to open too many doors
to discussions
not related to Clojure, but thank you for sharing.
As for the
On Tue, Dec 21, 2010 at 7:47 PM, Tim Robinson wrote:
> In my humble opinion, I don't think what you're experiencing will get
> any better, but here are a few thoughts:
>
> 1. You can still enjoy the community by changing your expectations and
> adopting 1 single rule (which I constantly try to rem
I think it's a pretty complex problem to solve. Although one could re-
word a statement to be polite, it's still just window dressing what
are still potentially just thoughtless arrogant statements that still
insult people within the community.
In other words, I'd rather someone say "Why would you
Great Kevin,
you just poured more oil on the fire...
Code is not the only thing about Clojure. Getting newbies on board is
needed and if they need pointers fine with me. There has to be a place to
jump start people. This mailing is a starting point and has to be somewhat
friendly.
I myself can
Some good guidelines to foster communities:
http://freenode.net/channel_guidelines.shtml
On Dec 21, 1:15 pm, David Nolen wrote:
> On Tue, Dec 21, 2010 at 8:36 AM, Jay Fields wrote:
> > I was involved with Ruby and Rails in the early days. The Ruby mailing
> > lists / conferences were always kind
On Tue, Dec 21, 2010 at 8:36 AM, Jay Fields wrote:
> I was involved with Ruby and Rails in the early days. The Ruby mailing
> lists / conferences were always kind / helpful and the Rails lists / confs
> were always hit and miss. There were plenty of great Rails people, and
> enough jerks to upset
Simpler solution: Don't feed the trolls. We know who they are.
On Tue, Dec 21, 2010 at 5:36 AM, Jay Fields wrote:
> I was involved with Ruby and Rails in the early days. The Ruby mailing lists
> / conferences were always kind / helpful and the Rails lists / confs were
> always hit and miss. The
Well, I'm glad to have you in the Clojure community, Jay. I come from
a Ruby background too, and I've enjoyed your blog over the years. Your
interest in Clojure has helped me get other Rails developers at work
excited about Clojure.
On the topic of community attitude, I agree with you.
great, yet another email on the list so unrelated to clojure that not
only does it contain no code, but no reference to code. if you need to
whinge publicly please do it on your own blog. if you don't feel like
the clojure community is giving you the love and support you need then
I am sure rails w
I would like to think is a symptom of the growth of Clojure. More
Clojure users from different perspectives and attitudes means more
potential for conflict. But some attitudes only causes noise: in
particular people who requires without counterpart and think Clojure
is like Visual Basic and this gr
Jay,
[snip]
I agree with your observations. The last few days have indeed been
kind of upsetting. I hope everyone follows your suggestions.
> Also, what happened to Rich? It seems like many wasteful discussions could be
> more easily put to bed by his response
> instead of the current "here's a
I think those are fine points. And to reciprocate, I think it's important
when you read someone's comments to give the writer the benefit of a doubt.
Sometimes it helps to read between the lines. If you can tone down your
emotional reaction to a comment that feels unpleasant, you may find th
I was involved with Ruby and Rails in the early days. The Ruby mailing lists /
conferences were always kind / helpful and the Rails lists / confs were always
hit and miss. There were plenty of great Rails people, and enough jerks to
upset anyone.
I read this (Clojure) google group pretty frequ
13 matches
Mail list logo
