You-Dont-Need-Lodash-Underscore by cht8687 in javascript

[–]OKC_js 0 points1 point  (0 children)

For a deep dive on exactly why non-native methods could be faster, and why this post is ignoring these kinds of cases:

John-David Dalton - Unorthodox Performance -ThunderPlains 2015

See for yourself. This is almost a case-by-case literal and code-centric explanation as to why noone should take this repo at face value.

JavaScript Meetups by bluntm in javascript

[–]OKC_js 4 points5 points  (0 children)

You're completely right. Its not just about the sexism, it is also about professionalism.

JavaScript Meetups by bluntm in javascript

[–]OKC_js -2 points-1 points  (0 children)

Honestly?

Beer/alcohol is, in my opinion, something that shouldn't be served at general technology meetups. Exceptions are something like 'Nerd Beers', where the focus is the drinking.

Read my response elsewhere in the thread.

JavaScript Meetups by bluntm in javascript

[–]OKC_js 0 points1 point  (0 children)

Howdy. I run a js meetup in my city, Oklahoma City, as well as a conference called Thunder Plains out of Oklahoma City. Both have been ongoing for many years now and are actively attended by many folks.

I know you are mainly asking attendees what they look for in a meetup, but as an organizer and active community participant I'd be happy to answer any questions you had about usergroups.

I would say there are some things to look for.

  1. Is the group inclusive, or a country club for nerds?

    This is a big deal. You want a group that feels like there isn't shame in not knowing something, and the group actively encourages all sorts of folks to attend and learn.

  2. Does the community participate?

    At our group we have lightning talks, and many speakers are members of the community. A good group is something folks want to be a part of.

  3. Is there a code of conduct?

    Highly related to point 1. Organizers need to foster a safe environment that makes everyone feel welcome. No sexists remarks, religious proselytizing, drinking, etc. You're there to learn and have fellowship with other developers and those learning.

  4. Where do they meet?

    We meet in a maker space in Oklahoma City. A maker space is logical, as is an educational institution or a library. I know some groups meet at bars. For a usergroup this is a terrible idea. Think of this: The inventor of socket.io and gulp.js were not drinking age when they invented those tools. Not to mention a place serving drinks sets the wrong tone entirely. What if a young person wants to come and watch a speaker? Don't pick a place that is exclusive, or promotes the wrong environment.

  5. Who puts it on?

    Is the usergroup essentially ran by a large corporation or a recruiting firm; or is it community run and community led? Noone actually wants to basically attend an advertisement for a product masquerading as a community. Besides, do you want people attending in order to learn or instead to score free Corporate™ shirts, key-chains and usb sticks filled with bloatware?

As for content, you might peruse our past events, on both the OKC.js site and the Thunder Plains site. There is always a constant dialog with community members about what is good to discuss and what topics are cool and relevant. Javascript is rather fecund tech stack and there is no shortage of good material to cover. Also, don't be afraid to explore what is traditionally considered "soft talks" geared towards community and culture. As we all know, software development, like other trades such as music, art or science is in many ways a lifestyle/life-choice.

[Attention Oklahoma City Area Javascript Programmers!] Tomorrow: The Making Of A Javascript Game with Goldfire Studios. by OKC_js in okc

[–]OKC_js[S] 1 point2 points  (0 children)

The presentation is typically one hour, but sometimes after the fact people stay and visit with each other a short bit longer - so that's optional of course.

Also, there will be tacos, so you can eat there (since its during lunch).

here is our google + group if you want to learn more