Perhaps we just need to use a different word. Yes, it's "code4lib" but we don't necessarily need to use "coders" to describe ourselves. What I find most important about the community and its conference is that we talk about what we do at extremely deep and detailed levels... like urtext or source levels. So, yeah, that's where the code comes in. But I do sys. admin stuff and architecture stuff too, and yes, coding. Am I a "coder" ? Yeah, but I'm also a librarian... What I have to be able to do in order to do my job is trace the interaction of information systems down to their lowest level. Sometimes that's looking at and writing code, but sometimes it's shuffling hard drives and LTO tapes.
So "non-coders" are absolutely welcome and encouraged to attend, as well as anyone who wants to discuss his or her own work at these deep technical levels. I believe it is paramount that we include these so-called "non-coders", i.e.. sys admin folks, architecture folks, digital preservationists, etc. Where else could you go do talk to all these people in one room?
Adam Wead | Systems and Digital Collections Librarian
ROCK AND ROLL HALL OF FAME + MUSEUM
Library and Archives
2809 Woodland Avenue | Cleveland, Ohio 44115-3216
216-515-1960 | FAX 216-515-1964
Email: [log in to unmask]
Follow us: rockhall.com | Membership | e-news | e-store | Facebook | Twitter
On Nov 28, 2012, at 10:02 PM, Mark A. Matienzo wrote:
> Some discussion (both on-list and otherwise) has referred to "coders,"
> and some discussion as such has raised the question whether
> "non-coders" are welcome at code4lib.
> What's a coder? I'm not trying to be difficult - I want to make
> code4lib as inclusive as possible.
> Mark A. Matienzo <[log in to unmask]>
> Digital Archivist, Manuscripts and Archives, Yale University Library
> Technical Architect, ArchivesSpace
This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication.