Changes

Jump to: navigation, search

How to hack code4lib

1,135 bytes added, 18:50, 12 August 2016
with demise of turntable.fm in 2013, Code4Lib Friday Jams appears to have moved. Cite: https://twitter.com/bot4lib/status/411539434962554882
Originally by Declan Fleming, Director of IT, UCSD Libraries (BigD in channel), heavily edited by the community
Budget willing, this year will be my third code4lib, one of my favorite conferences ever. I remember what it was like to be new and wondered if I could write a short piece that would help new people to the community get as much out of the conference as I do.
The conference back channel on IRC is the most invaluable tool available to help you quickly get the feel for the conference and the people attending. Most technical people have the attention span of a gnat at times, and the channel helps keep a conversation flowing when the presentations get slow. Be warned that the level of discourse on the channel is very similar to how a group of friends would be talking around a table full of drinks. The topics range from inside jokes about bacon and sad facial hair to esoteric explorations of the RDF expression of specific pieces of metadata. The channel is also very useful for seeing where groups are going for lunch or dinner. You can find more information about IRC and how to get on it via the [http://code4lib.org/irc IRC page on the main Code4Lib site].
 
=== Or get to the #code4lib IRC channel (and other discussions) via Slack ===
 
There is also a Code4Lib Slack team, which includes a feed from the Code4Lib IRC channel. You can see what's going on in IRC here, or post a message to the IRC channel. You won't be able to send commands to Zoia (the Code4Lib IRC bot). You do need to be invited to join the Slack team initially and you can use [https://docs.google.com/forms/d/120Dw1JjLxPJB9VTGl0mUY7Ot6yg6YNY1RZUISJFzdwk/viewform?c=0&w=1 this Google form to request an invitation]. Once you've joined the Slack team, join the public channel #irc to view the IRC feed.
=== Listen 90% of the time / Talk 10% of the time ===
code4lib is jammed with characters who are passionate about some aspect of our profession. Ask a question or two then sit back and bask in the output. Don't worry, you'll have the chance to talk about what you are working on when your companion stops to drink beer.
=== If you don't have a lot to share, just at least try to be friendly funny ===
My dirty little non-secret is that I love code4lib but I'm not a programmer, or even a sysadmin anymore. I'm a manager of these type of folks and I love hearing what's new. I often don't have much to offer in terms of pythons or rubies, but most people can appreciate a sense of humor.
One group that gets beat up on a lot is vendors. There's a healthy debate that comes and goes in the channel about whether it's good to have a place to vent, or if making vendors the butt of jokes limits their interaction in the community. One of the great strengths of the channel is that the norms are constantly in flux and openly discussed and debated.
=== Don't be too sensitive === Of course, political correctness can sway too far to the conservative, and what fun is that? Don't always assume that the jibe you took in the channel is meant personally. It is usually safest to always give the speaker Give the benefit of the doubt. So many non-verbal cues are missing in this medium, it is just a virtual conversation after all. === Be willing to laugh at yourself #code4lib IRC users ===
I've found that making fun Non-verbal cues are missing in IRC, so give the speaker the benefit of myself is a safe outlet for being bitingly cleverthe doubt. And once A perceived jibe you've shown people that you don't mind being a targettook in the channel may or may not have had cruel intent behind it. You might ask the speaker to explain the comment, they'll let their hair down and pick on or if you too. Besidesdo feel slighted or uncomfortable, why not beat everyone feel free to ask one of the punchfolks listed in zoia's "@helpers" command output in private who should be able to help.
=== Don't be intimidated by what looks like the "in crowd" ===
=== Take a sip from the firehose ===
There are lots of places where things are happening, allowing you to choose the mediums of engagement you are most comfortable with and interested in. Definitely get on the [https://listserv.nd.edu/cgi-bin/wa?SUBED1=CODE4LIB&A=1 email list]. In addition to that, Code4lib has a [http://code4lib.org blog] to stuff in your feed reader. But if you want to see what's going on in code4lib check out the [http://planet.code4lib.org planet] aggregator of blogs from code4lib folks. If you have a blog and want it listed there ask jrochkind in [irc://freenode.net/code4lib irc]. You can also follow [http://twitter.com/code4lib code4lib on twitter], or consider following code4lib twitter users via code4lib lists from [http://twitter.com/eby/lists/code4lib eby] or [http://twitter.com/mjgiarlo/lists/code4lib mjgiarlo]. There is also a [http://www.linkedin.com/groups?gid=134499 LinkedIn] group you can join for more "professional" networking. A [http://reddit.com/r/code4lib Code4Lib subreddit] was also recently added. If you like to work to music and share with the code4lib community, check out [https://plug.dj/code4lib-friday-jams Code4Lib Friday Jams]. If you're interested in being in the know about the annual Code4Lib Conference, then you should get on the [https://groups.google.com/forum/?fromgroups=#!forum/code4libcon code4libcon Google Group].
114
edits

Navigation menu