Code Year Community

102 members  |  About this group  |   Syndicate content
View:   Faces | List

Discussion Survey: Library Staff and Code Year

by Carrie Preston on Mon, Mar 11, 2013 at 06:51 am

Apologies for cross-posting.

 

Apologies for cross-posting.

 

I am conducting a survey on librarian experiences with Codecademy’s Code Year program. The survey is intended for library staff who completed at least one Code Year exercise in 2012. You do not need to have completed the entire Code Year program to participate. You must be 18 years old or older to participate.

 

The survey should take approximately 15 minutes to complete. No identifying information will be collected and your participation in this survey is voluntary.

 

To complete the survey, please visit https://docs.google.com/forms/d/1njVvhkHCtTRuYk7nvVFJIDv3pbwRlp4MmQPWD9k3r8Y/viewform

 

If you have any questions regarding this study, please contact:

Carrie Preston

prestonc@ohio.edu

(740) 597-1973

More...

Discussion Sharing my Blog post about #codeyear and writng one's own code

by Bohyun Kim on Wed, Sep 12, 2012 at 03:02 pm

Hi all,

I wrote a blog post in ACRL TechConnect about #codeyear and wanted to share it.
It is about venturing to write your own code after these lessons and chosen examples.
Let me know if it is helpful! Are you all following along the code year btw?
I am way behind but still trying to do a couple of lessons every week wehnever I can during the weekend!

http://acrl.ala.org/techconnect/?p=1821

~Bohyun

 

Discussion PyCon!

by Andromeda Yelton on Thu, Aug 23, 2012 at 08:02 am

Last night I heard Jessica McKellar, a big shot on the Boston Python scene who's going to be one of the PyCon keynotes next spring, tell us all why we should go to PyCon.  tl;dr if you can, you should go to PyCon!  It sounds like it'll be an awesome time if you're at all interested in Python -- friendly to people at all skill levels, and this year it's focusing on education, so I think it'll be especially good for beginners and for people running any kind of code events at their libraries.

Last night I heard Jessica McKellar, a big shot on the Boston Python scene who's going to be one of the PyCon keynotes next spring, tell us all why we should go to PyCon.  tl;dr if you can, you should go to PyCon!  It sounds like it'll be an awesome time if you're at all interested in Python -- friendly to people at all skill levels, and this year it's focusing on education, so I think it'll be especially good for beginners and for people running any kind of code events at their libraries.  It's next March in Santa Clara: https://us.pycon.org/2013/

More...

Discussion Say hi!

by Andromeda Yelton on Tue, Jan 10, 2012 at 10:44 am

I thought it would be nice if we introduced ourselves.

 

I'm Andromeda.  Simmons MLS 2010, thought I'd work for an academic library doing electronic resources or something, found myself working at a startup doing ebooks and social media and web development and copy writing and pretty much whatever needs doing.

 

I thought it would be nice if we introduced ourselves.

 

I'm Andromeda.  Simmons MLS 2010, thought I'd work for an academic library doing electronic resources or something, found myself working at a startup doing ebooks and social media and web development and copy writing and pretty much whatever needs doing.

 

Before Gluejar I had a smattering of code here and there -- the semester of C++ I forgot from undergrad, some SQL and PHP from library school, some self-taught Python (via Google's Python intro, awesome).  At Gluejar I've done more Python and spent an awful lot of time pretending I know jQuery, which means I sometimes have to pretend I know JavaScript too.  So I thought it would be nice to actually know some JavaScript.  Also I am super-interested in librarians' tech skills and how we learn them, and in online communities, so Code Year seemed like a great way for me to learn more about those things.

 

I'm hoping this group will attract a mix of people with some code experience who are eager to help out, and people with minimal or no code experience who are eager to learn, and we can all hold hands together.

 

var conclusion = "Learning code is super-awesome and empowering";
print conclusion;
More...

Discussion Week 5

by Andromeda Yelton on Tue, Feb 14, 2012 at 10:20 am

So, who's on week 5?  Comments, questions, rants, brilliant insights, etc.?

Discussion Week 6

by Andromeda Yelton on Tue, Feb 14, 2012 at 10:21 am

And, for the people who are all the way up-to-date (or everyone else who catches up along the way), here's a space to talk about Week 6.

Discussion Week 4

by Andromeda Yelton on Tue, Feb 14, 2012 at 10:20 am

Can you tell I'm a teensy bit behind on CodeYear?  (Partway through week 5 myself, but I hear people are all over the map.)  Nonetheless, there should be discussion spaces for all the weeks to date!  Working through Week 4 right now?  Hop on in and share insights, ask questions, etc.

Discussion New Library Code Year Interest Group

by Carli Spina on Sun, Feb 5, 2012 at 11:08 pm

Exciting news: we have officially formed a new Library Code Year Interest Group. Jointly sponsored by ALCTS and LITA, this group aims to support ALA members who want to improve their computer programming skills and connect with other members with an interest in computer programming.

Exciting news: we have officially formed a new Library Code Year Interest Group. Jointly sponsored by ALCTS and LITA, this group aims to support ALA members who want to improve their computer programming skills and connect with other members with an interest in computer programming. This new group will not replace the Code Year community that has developed here, but we would definitely love to have each and every one of you join the new IG! You can check out the new group at: http://connect.ala.org/node/167971. Hope to see you there!

 

 


More...

Discussion Reference Document

by Frank Skornia on Sun, Feb 5, 2012 at 03:05 pm

I just whinged about this on Twitter. One thing that is bugging me a bit as I go along (especially with gaps of time) is trying to remember the syntax for certain commands. I don't have time to start today, but what do people think of developing a reference document that develops as additional syntax and commands are added to our repetoires?

I just whinged about this on Twitter. One thing that is bugging me a bit as I go along (especially with gaps of time) is trying to remember the syntax for certain commands. I don't have time to start today, but what do people think of developing a reference document that develops as additional syntax and commands are added to our repetoires?

I'll play with the idea tomorrow night after work and see what may work. Ideally it would be a document that can be referenced by the command and also by the week where it was introduced (people remember and look for info in different ways). Any ideas on this front are welcome.

More...

Discussion tips

by Andromeda Yelton on Sun, Feb 5, 2012 at 01:10 pm

Bohyun posted this super-useful blog post of CodeYear learning tips: http://acrl.ala.org/techconnect/?p=167  It has resources, advice on how to ask code questions to get the most useful answers, and a very clever spot-the-error game you can use to to quiz yourself.

Pages

What could be awesomer than a bunch of librarians who've signed up to learn to program at http://codeyear.org/?  A bunch of librarians helping each other learn.  If you're doing Code Year -- or if you're an experienced coder who wants to help out -- join.  Let's all learn together.

Subscribe to Code Year