Not entirely to Hal's point, but perhaps agreeing somewhat
in-principal and perhaps commenting more directly:
Because Keep Ruby Weird's identity leans toward the cutesy and the
ironic, and because - for better or worse - these kinds of things are
often correlated with less experienced software communities where
chasing fashion and fad displaces foundational techniques, KRW might
be less palatable to anyone who might be burned out on the cutesy and
irony - especially with perhaps more pressing issues that attention
might be paid to.
I'd like to see a Ruby event in Austin again. But I've skipped KRW
because the cute and the ironic tendencies mean that there a greater
probability that I won't see anything terribly edifying. That
prejudgement is very likely a weakness on my part, but there you have
it. I expect a greater preponderance of clichés from events that
identify with the cute and ironic that those that are focused on
problem solving rather than concerns over social aesthetics.
So... Is it possible for Ruby developers in the region to be
interested in a space and time reserved for learning and teaching
without indulging in the same old tired clichés? Or is it a necessary
facet of promotion and marketing that the cute and the ironic be
indulged?
Can an event with broader appeal, and one that is welcoming to all
levels of professional Ruby work, be done? And I guess, is such a
thing even welcomed and necessary?
Perhaps said otherwise: An event that is perhaps a little more
dignified might attract an audience that has greater diversity.
I realize that this might sound harsh to anyone who doesn't see a
problem with the KRW identity, but I feel it's important to express
the real downside of indulging such kinds of things.
KRW - to me, from the outside - strikes me as a leaning toward the
Brogrammer side of things, and I tend to stay away from those things
for not wanting to have to be reminded of its prevalence and the
difficulties that it creates in getting new, fresh ideas and
improvements under way.
On the other hand KRW is a specific kind of thing, and it's free to
express itself in any way that it wants, and it's not my place to say
what it should be. KRW isn't beholden to anything but itself and it's
own values, and that's fine. I'm not entitled to be served by KRW any
more than KRW is required to answer to me. But these are my critiques
nonetheless.
And I think it's critical in communities of practice to have these
kinds of discussions and negotiations of meaning openly and without
attempt to muffle them in any way.
Elixir is not an answer to what ails Ruby these days. And it would be
valuable to put heads together with folks who would like to see new
life breathed into Ruby and to start to address traditional problems
that make the exit to other platforms attractive rather than digging
in and fixing the mess we've created - and to learn to avoid doing so
again in the future (possibly on the next trendy platform).
I wish there were an event in Austin that is welcoming to all of Ruby
culture, and is focused not on promoting trendy traps, but on digging
in to software development, design, and architecture, and doing it
with Ruby as the language.
I wish there was an event that is committed to breathing some life
back into the core of the Ruby community in Austin, and ideally, to
avoid the clichés of the past and to talk about more than banging out
web prototypes for web startups (not that there's anything wrong with
that - unless it's the only thing on the docket and reduces diversity
accordingly) and tinkering with robotic kits.
Maybe it's just an event that needs to be organized by the community
rather than left to an events company or even the LSRF (but ideally
with the support of the LSRF).
Anyway, that's my two cents.
Apologies to Hal for usurping his commentary here to deliver something
of a harsher message.
Nonetheless, there's hard work to be done in Ruby and Ruby community,
especially in recovering from Rails, and helping companies, projects
and teams remediate the problems exacerbated by it. I hope that we can
dig into that work as a community.
Best,
Scott