Makerspace: A Semester's Resource Masterpost

Overall my makerspace has had a great year. I't's gone by super fast - there's something to be said for just jumping in there, but there's a learning curve that can be a little hard to jump. So in case it can help anyone else, I'm going to write about some of the opportunities I've found and the stuff I've learned here!


FUNDING:

Codecademy, in a collaboration with Google and Donorschoose, offers codes worth $100 on a Donors Choose project to support a classroom program to every student who completes their tutorials through a school program. This is a great opportunity for ANY school Makerspace to get some funding while teaching kids about programming. Although the program advertises itself as solely for High Schools, there are options for all grades and schools, and it wasn't a problem for my middle schoolers. The program is closed for 2015 right now, but it pops back up annually, so watch that space!

I'm also going to be looking at the NCWIT AspireIt awards. I was a national runner up and regional winner this last year, which is how I learned about the opportunity (For other girls in high school or college - APPLY, APPLY, APPLY!)

Also, the teacher sponsoring my club was even able to set up a Donorschoose project, where we're trying to raise money to get a 3D printer for next year. If you want to fund the project, you can find a link here. If you're able to give support, any would be appreciated!

ACTIVITIES:

However, even though funding was limited, I was able to come up with ways to make the materials I DID have stretch, to groups ranging from a core group of about 20 students, to larger groups of up to 50-60 at one point. What I found worked really well was:

- Dividing the kids into groups, and assigning each group a different part of the activity. For example, I was able to spread my two Mindstorms kits across a large group by assigning each smaller group to build a certain part of the robot.

- Alternating activities between groups: While I was able to raise enough money with my earlier fundraiser to buy 15 Arduino Uno clones for the Makerspace, I was still limited in the number of computers we had to program them. To fix this problem, I divided the kids into two groups: one spent the first half of the time building circuits, and the other, programming. Then they switched, so everyone got a chance to try everything

-Large group discussion/brainstorming activities: During the weeks I was short on materials or planning time, I defaulted to activities that didn't need anything more than a pen and some paper, or computers. I took inspiration from a middle school SMU competition called Visioneering, which I participated in in the 7th and 8th grades. In the competition, teams of students are challenged to create plans for solving some problem with technology, no matter how expensive or "out there". For my adaptation, I had each table brainstorm a plan for improving the school using technology, which they had to share with a group at the end of the class period.

Those are just the ones that come to mind right now. Over the summer, I plan on putting together some guides to the various lessons/projects we did, and, ideally, I'll publish them somewhere online (though exactly where is TBD. I'll post a link here as soon as I figure it out).

PLANS:

For next year, I'm looking at trying to expand my program to merge with one at an existing elementary school in the area, though that plan is still very much in its "what if?" stage. I'll also have a chance to talk to the principal soon about getting the sorts of programs we'd need on the school computer. Plus, over the summer, I'll hopefully have a few more volunteers to assist me with planning meetings and keeping track of the budget. So overall, there's still a lot of work to be done, but I feel good about my plans as the next year comes around.

OTHER HELPFUL THINGS:

Don't be afraid to ask for help, information, or anything else from people who seem interested. You'd be surprised what you can learn.

Practice talking about your project. You should be able to give a compelling summary in 30 seconds.

The fancier the technology, the less time you'll have to do the activity (You have to account for the ooh-and-aahing).

If you're having fun, chances are everyone is.


Anyone have any comments, other suggestions, or anything to say? Please, comment below!

Makerspace: Chugging along!

Sorry for the dearth of posts! It's been a rough couple of weeks here, what with school, theatre, and even a coding competition (2nd place!), and the NCWIT Aspirations in Computing Affiliate Award Ceremony!

But mostly, I've been slowly pushing forward with my Gold Award project.
I've held 4 meetings so far this semester. I try to start each one with some kind of a question. For example, a the first meeting I asked what each student thought technology was, and what it was used for. ( I keep the questions open ended, so I sometimes get some... interesting answers.) Then I introduce an activity, and the rest of the meeting is devoted to that activity.

 The first one focused on the engineering design process. I built a ramp at home out of old K'Nex kits, and had students divide into groups to try and design a Lego car that could jump off the ramp from one desk to another. The group work turned out well - it's definitely something I'll continue. The kids really enjoyed the chance to talk more while they worked. Later meetings have been about programming, and more recently, robotics and game design.

The club is also making use of a Google Classroom to keep in touch outside of class. I like the Google Classroom setup, although I find myself wishing it was a little less of a bare-bones framework. I'd appreciate an easier calendar application, intersectionality with google hangouts, etc.

Finally, I was pointed by my sponsor to an assistant principle at my school who was interested in creating a Girls Who Code club at the school. This kind of thing requires a higher-up approval where I live, so it probably won't get started until next year, but it's a step toward getting a wider recognition of what I'm trying to do, and I'm excited to help.

Anyway, this is what the space looks like right now:

The new boxes and ramps are from some of the previous projects.

Slowly but surely, we're getting there!

Coming soon: I PROMISE I will finish my post on my Tic Tac Toe program soon - every time I start writing about it, I end up working on improving it again. Then I've got another book review from the opposite end of the AI spectrum - Ray Kurzweil's "How to Create a Mind." So stay tuned!

More Web Design: Learning Rails Online

So, if you haven't seen my other post, as a part of the application process for a more advanced Tech Theatre class in 11th grade, I need to have a digital portfolio.*

Now technically I could just have my every project hard-coded into each page using html and CSS, but that sets off every alarm bell I've got. It's just bad code. I don't want to have to type all that out over and over again! It would be much easier if I could create and projects without having to program each one in individually.  So, I visited my good friend Codecademy again to take a crack at one of their newer, longer, tutorials: Ruby on Rails.

* I have since been informed that a powerpoint would have been fine, but where's the fun in that?

I picked Rails over PHP or the other options because I've had more experience coding in Ruby than any other language (except possibly Java, through iTunes U's Stanford CS101 course, but that was a while ago). I wanted at least some sort of base to start from because, and let me make this very clear: I had no clue what I was doing. I'd never done any sort of web applications before. I'd never done any programming projects where I had to juggle multiple files or languages. So I figured if I was going to take my trial by fire, I might as well wear some sturdy shoes.

I installed Rails through Homebrew (a package manager that mimics linux) for my mac. All the files I  created defaulted into Xcode and not Textmate, which surprised me, and then I used Brackets to edit my views and stylesheets.

So like this, but with at least seven more windows open, and a cat lying on the keyboard.

The rails tutorial has a very, VERY slow start, especially if you already know how to code in Ruby. It's essentially a Ruby and a Rails intro all in one, and I couldn't find any way to skip. Prepare to spend a good hour on 'hello world!' type lessons before getting to the good stuff. And the good stuff is good, but I had one major problem through the tutorial - some of the code doesn't translate well to building your own app because it leaves out bits to simplify the tutorial.  Which meant I saw an awful lot of this:

Add your own hair pulling and incomprehensible screeching.

And don't get me started on associations. For the basic structure of my web app, I want each project to belong to a category, and each picture to belong to a project. It turns out that Codecademy's take on explaining how to create these associations... assumes a lot, in the best of cases. In the worst, trying to replicate the code structure just doesn't work because they leave pieces out.

Sometimes though, it's your own fault and you know it.

So, I supplemented my learning with this Rails Guide. The great thing about this guide is that it can act as a sort of cheat sheet. Every time I looked at something in the codecademy tutorial  and had no clue what was going on, I could look back to this page, and find the no-fluff method to getting done what I want to do. In my opinion, it does a much better job of explaining the structure of Rails than Codecademy. But the benefit of Codecademy is being able to type in the code for yourself and see the different files side by side in the simulator. For better or for worse, I really needed both.


Of course, neither of these things stopped me from spending hours on stackoverflow because my CSS wasn't updating as I refreshed the page, or my migration wasn't taking, or every single one of my pictures was apparently owned by every single one of my projects. That's just part of the learning process: you can't really, truly learn a programming language until you start to program something in it.

So now my website is finally coming together functionally!

CSS could still use some work though.

 I've started to look at options for hosting. I'm going to try out Heroku, because it's free to start out, and I've heard good things about it so far. Any thoughts or suggestions? Questions about the tutorials, or where to learn more? Ask away!

Teaching Basic Circuitry the Holiday Way!

If you've seen my last post here, you've probably seen this little bauble.

This is the final product created by the no-solder kit I'm selling to fund my Gold Award project. The idea is that the kit is easy to assemble as a kit to teach younger kids about Parallel and Series Circuits, while still leaving something cool for them to take home. Each bauble costs less than a dollar to make*, and all the materials can be bought with a trip to a craft store and an electronics store, so I'd say it's pretty successful!

*If you buy batteries online, as most coin batteries I've seen are insanely expensive at grocery stores. I bought 100 for $17 from this website.

Here's what you'll need: 

1 Miniature Glass Ornament

Some silver ribbon (I used Easter Basket filling)

2 Pieces of Wire

1 Lithium Coin Battery

1 LED

A hot glue gun

A pencil

Some tape (electrical tape works best)

Scissors

How to make your ornament:

Carefully pull the silver top off the glass ornament, then pull the pin out.

Use a pencil to push the silver ribbon into the ornament.

Put a piece of tape on the inside of the silver ornament top so that it covers the two holes. Poke one of the leads of the LED through the tape and through the hole so that the bulb is UNDER the ornament top.

Use the hot glue gun to secure the LED to underside of the lid so that the bulb sticks out by about half an inch. 

Then glue the lid back to the top of the ornament so that the LED is hidden by the silver ribbons

Loop one of the metal ends of the black wire around the shorter lead on the LED, and secure it with hot glue or tape.  Make sure the wire is directly touching the lead! Then, do the same with the red wire on the longer lead.

If you're interested in doing the experiments (which require 2 or more baubles), here are the instructions I'm giving out with the kit below:

PARALLEL AND SERIES CIRCUIT EXPERIMENT

Series circuits are created by wiring all the components of a circuit in a line. The electricity moves straight from one component to the next. They’re useful when you want a circuit to shut down completely if it’s damaged. 

Just connect the wires red to black for series, and make sure the red wire goes to the positive side of  the battery, and the black to the negative. 

What happens when you add more ornaments to the chain? Try touching a paperclip to both leads of an LED in the circuit. What happens? Why is this? 

Parallel Circuits are created when each component gets its energy directly from the same energy source. They’re useful when you want each component to work independently of each other, or if you don’t want damage to one component to affect the others. 

For a Parallel circuit, the black or red wires for each ornament connect with the black or red wire leads of the next LED. The last black wire in the chain goes to the negative side of the battery, the last red wire to the positive. 

What happens when you add more ornaments to this chain? Try touching a paperclip to both leads of an LED in the circuit. What happens? Why is this? 

Finally, to finalize the ornament, tape the other end of the red wire to the positive side of the battery, and the black wire to the negative. The LED should light up. If it doesn’t try swapping the wires or moving the LED’s leads. If they’re in contact with the metal of the ornament top, the LED won’t light.

I hope this lifts your holiday spirits! It's fairly durable (I was able to wear one on a necklace all day at school with minimal problems.) and it looks good. Try it as an ornament, a necklace, and augmentation to an ugly sweater, or just a shiny reminder to say "Happy Holidays!" 

And if you happen to make one, please, send me a picture at rach.s.thompson@gmail.com. I'd love to see it!

Makerspace, Part 2: The Plan.

Last week, I finally got to have my first meeting with the middle school Technology club I'm working with to create the Makerspace. We talked about what a Makerspace was, how we were planning to use it in the school, and the various bits and pieces of old projects that I brought to show what kinds of things could be made in a Makerspace. Basically, it was a condensed version of this post, with a few pictures from Big Hero 6 and Iron Man 3 as reference points.

Good movie...  but it was no Wreck-it-Ralph. 

At the end of the meeting, I had ever student write down on their slip of paper the top ten things they wanted to be able to make/learn in the technology club. Over the weekend, I looked through all the answers I got, and came up with the five main units that would be the most useful and interesting to kick off the Makerspace and the Tech Club. The Technology club has two types of meetings - "Class" meetings, which teach skills like the one's seen below, and "Business" meetings, where we'd focus more on the Makerspace itself, and where members would have time to share the projects they've been working on (THAT is for a different post). But the introductory skills are important for the students with little or no experience. So here's what I've put together: 

1. Programming

 This is the obvious one, but I've put it as the first unit because it's a vital skill so many of the other projects the students were interested in, and because it doesn't require expensive materials. I'm working on lesson plans for a programming intro class for Scratch, which will hopefully give enough of an introduction that the students will feel comfortable working on Codecademy tutorials or learning from other online resources

2. Robotics
These kids love robotics almost as much as I do. The issue here is limited time and materials. I'm planning on doing two classes with Mindstorms Ev3 - one for building, one for programming. I'd also like to incorporate robotics into an Arduino introduction later on - I have an RC car that I robotized with an Arduino that would make a good example.

3. Circuitry
While I'd actually prefer this unit before robotics, the littleBits are one of the more expensive items in the budget, and, while I have an Ev3 kit at home that I could bring as an example, the same isn't true here.

4. Computers
This is kind of a catch-all unit. Here I definitely want to have a class on the Raspberry Pi, but I also want to bring in some of the other Technology Club Alumni to teach classes on things I'm not as familiar with, like App programming and Web Design. (It's interesting to see how our individual interests were foreshadowed through Tech Club and the technology class. The ones who spent all their time on the iPod touches now program them, the ones who spent all their time tweaking Powerpoints and Tshirt designs have gone into 3D animation or computer graphic design. And yours truly MAY have turned in a final paper analyzing potential uses for robots that could create their own languages after researching this. I really should post it here if I can find it.)

5. 3D Printing
I have never had the opportunity to use a 3D printer, and I could not be more excited to learn. That's why this unit is last - I know the least about it, and I need that time to learn. I'm planning on getting the Printrbot kit, and using Google Sketchup and Autodesk inventor to do the modeling, since our school system already has that software.

These are the things we decided would be the most useful. I've said before that you don't need expensive tools to make a Makerspace, and I stand by that statement. But good tools make making more accessible, and especially in a school setting, that's important. And tools cost money.

About $1,300 worth of money, not counting shipping or storage.

I'm looking at a couple different ways of doing money-earning.  For the more expensive kits, I've talked to my sponsor about using DonorsChoose. It seems like a great program, and I'd appreciate the help in offsetting the cost. However, with finals rapidly approaching, we haven't had the chance to talk to the school administration yet. So I've started with some simpler money-earning opportunities. Right now, I'm creating kits for making small light up ornaments to teach younger kids about the basics of circuitry. The kits would also be good for making a string of lights, good for teaching Parallel vs. Series. Plus, who doesn't love holiday themed illumination? Here's a picture of the prototype. I'll be posting a tutorial soon.

I'm selling the kits to local scout troops as an end of year craft project and my goal is to raise about $100 to start off with.

And finally, while I can't expect to rely on donations, I had the opportunity over Thanksgiving break to collect some of my great-grandfather's old tools for use in the Makerspace, which I cleaned up and labeled.

It wasn't anything too fancy - just screwdrivers, wrenches, a level, things that would be useful for building or disassembling small projects. But that toolbox has officially become the first thing in the Makerspace.

It's a long road ahead, but we have a plan. Let the making commence!

PS: One last thing. One of our main concerns with the technology club is the participation of girls. I was one of two girls out of about fifteen people at the clubs inception, a ratio that improved a little  the next year, I suspect because both of us were so active in the club. Now, she's actually come back to help with my project. But we still see the same problem. There were only two girls at the meeting and about twenty boys. Do any of you have suggestions for getting more girls involved? 

Super Secret Special Project: Makerspace!: A Long Introduction.

I've finally caught up with my teasers! I've been pretty busy with school, scouts, other projects, and, yes, my Gold Award project, where I'm hoping to build a Makerspace at my old middle school!

Note: For the uninitiated (credit xkcd)...

A Makerspace, Hackerspace, FabLab, Techshop, etc... is a space devoted to providing materials, instruction, and community to anyone interested in creating. It goes hand in hand with movements like OpenSource, STEAM education, and free information. A Makerspace wants everyone to be able to make, and to find other people who make.

To give a little background - my middle school librarian was an awesome teacher, interested in sharing information, technology, and connection through the library. She started the technology club my first year at our school, where teachers could come and talk about the technology they wanted to use in the classroom (e.g. Google Earth Tours, iPod touches, online video-editing software, etc) and it was up to us to A) figure out how to use the technology, and B) teach the teachers once we figured it out. The club was only the beginning. By the end of the year, 13 of us were enrolled in the Independent Study Tech Team class, taught in the library, by the librarian, for an entire class period each day. The teacher brought some brilliant ideas to the class: 20% time, bringing in projects from other classes to try out the technology, etc. It was basically a maker class! The only thing we lacked was materials.

In the library, we had three things we could work on: Software on the computers (the basics of Windows 7 plus a few class specific things, like Alice), thirty-something iPod touches we rented out to classes, and books. This was a great starting point, but I kept having to bring in my own materials for 20% time to feed my interest in robotics and programming. The teacher introduced me to the idea of a Makerspace my eighth grade year, and the more research I did the more I liked it. The materials I've collected are important to the kinds of projects I get to do - I hate the idea that another kid somewhere won't get to learn about robotics because they don't have access to a mindstorms, or an arduino to learn on.

Ninth grade taught me how useful a Makerspace could be. If you've even taken just a quick look at this blog, you can see I took Tech Theatre, and made full use of the workshop we had available. That workshop is my favorite place in the entire school, because it has everything you need to bring a design to life. Tech Theatre may not be a class devoted to engineering, but I feel that, because of the workshop, and because of the self driven nature of the class and the projects, it does a better job of teaching problem solving, design, and engineering skills than the note-and-test heavy engineering-specific class I took.

I decided to try and find a nearby Makerspace - it turns out the nearest is an hour's round trip from my house. I got a tour to see how the space functioned. It was REALLY cool, but I noticed that it was definitely geared more toward the adult, experienced engineer in price range, classes and tools available, and supervision. That wasn't quite what I was looking for, so I contacted my old librarian to ask her thoughts on creating a Makerspace in Plano... and a few weeks later, she's my Gold Award Project Advisor,  I've sent a powerpoint proposal to the principal of the school, and I'm prepping one to send to my local public libraries! (See the powerpoint here, if you're interested)


What's the plan? Well, the main issue is cost. I spent a long time looking up the costs of materials I'd like to include, and, to say the least, cost was high. I'm planning on organizing a tool drive to try and get some of the cheaper items, like paintbrushes and screwdrivers, old toys to take apart, Ewaste, and the like. Some of the rest will be funded by club member fees, but for a lot of it I'm looking at funding online through Donorschoose.org, or something similar.


Another constraint is space. The area we're looking at converting is currently storage for books that get lent out in English classes for reading assignments. We get a grand total of one bookshelf for storage, so we'll have to use it wisely. This is a real model of the space I made in Sketchup. I'm betting the Technology club will be happy to have it. Right now, I'm still waiting on the final green light from the principal, which will hopefully come in the next couple of weeks. Then I can turn in my paperwork, and get the ball rolling! Expect to see more about this soon, and all the little mini-projects it entails.

(NOTE: I'm going to publish this as is, but it's a little outdated now. I've since had my project fully approved, and the first meeting with the students will be next week! I even had the chance to talk about my project at the Girl Scout Leadership Institute at this year's national convention. I'm super excited to get started. If any of you have ideas for fundraising, or know of good projects or resources for a middle school Makerspace, please comment below! I'd love to hear what you think.)

Useless Lamp - Mindstorms EV3

For our final project in one of my classes, we had to create an art piece based on a movement we studied. I picked Dada, and this is my project, Lamp. Here's a video of it in action.

I built the project using two mindstorms large motors and a pressure sensor. There are two halves to the mechanism - the "useless box" half, and the half that controls the lamp. The lamp in particular I used had a wheel switch that I had to to try three different ways of operating, finally taking it apart and reworking it as a button. The box decorations are made of vinyl and fabric I had lying around the house. I'm only going to talk about the mechanisms involved in making your own useless lamp. The rest is up to you.

Project: Set Design for Beauty and the Beast

I had a pretty impressive delay on starting this blog, and you can blame a fair mixture of social anxiety and high school theatre tech for that. My school doesn't have a whole lot of project based classes in it, but I go crazy if I spend all day doing reading assignments, so BAM, theatre crew.

This turned out to be a great choice for my mental health, but not so much for my free time.
I worked two shows (for a later post!) as well as taking the class. The director had decided that for our final show, we were gonna go with Beauty and the Beast. The Disney version. The Full version.

I was picked as one of eleven crew heads out of twenty-something crew, at which point I realized what I had gotten myself into.

Here's a rundown of what's taken over my last three months.

1. The Beast's Chair

For some reason I don't have a picture of it upholstered, but this was my first project for the musical. Me and two of my classmates were given some pictures of armchairs from other productions, and told to design and make our own. The chair itself is about 3ft. wide and 6.5ft tall, pretty fricking heavy, mostly because of the back. It's name is Dylan. See our selfie below.

The theatre director claimed it as her 'throne' in the scene shop. 

2. The Spiral Staircase

My next big project started when the tech director learned that I was in a higher level math class. I walked into the classroom and was immediately told "we need to build a spiral staircase, but it needs to start out being 6 feet wide and taper to 4 feet wide, go from *here* to *here* and curve like *this*." I didn't actually help much with the building of this, but the design was all mine.

3. The Rooftops

By the end, I designed and built three roofs for the show, two for Belle's house, and one for another building that served a number of purposes.  They looked very asymmetrical and cartoony, which was great for the audience, but meant we had to have three people to build each one, and even then they sometimes had to be rebuilt. Not to mention, they were heavy enough that we had to tie them to a batten and fly them to get them on the houses. 

4. Foam proscenium… thing?

I don't know why we had to have this particular flourish, and it was definitely my least favorite project of the show, just because it was so picky as far as measurements go so that it could be symmetrical. I designed and cut the pieces for the two layer frame for the proscenium arch. (At one point I had to recut something because it wasn't 'wavy' enough) The effect is cool, but that was a week of high blood pressure I could have lived without.

5. Maurice's Invention

I enjoy working with projects that have moving parts and electric components, so this was my main project throughout the production. It's named Ada, after Ada Lovelace, the first computer programmer. What I'm most proud of in this project is that nothing had to be purchased for it. Everything on the invention came from the scene shop or from set pieces from previous shows. Even the wheel attached to the axe came from our second bicycle (which was apparently in three pieces.)

I designed the invention, presented my design to the tech director, and then I worked with an assistant to build the thing. The box on the back held the 'log' to be chopped, and the top was attached by a hinge so Maurice could get to it. The actually chopping motion was supposed to be controlled by a plain DC motor, but the tech director couldn't get one. I ended up ghetto rigging a drill during hell week to turn the belt of the bike wheel and spin a pole attached to the bike wheel and the axe head, while the axe handle was bolted to the invention, which created a second-class lever and a pretty forceful chopping motion. This worked at every rehearsal, until opening night, of course. The Tech Director and I reworked it, and it worked perfectly every other night. 

The whole thing is long and heavy, and somehow (barely) rideable. It chops cardboard logs with gusto. It makes me prouder every day. Yay Ada!

5. The Castle

The castle was designed by the directors, but all crew helped build it, and it's really awesome to see it painted and everything, in it's entirety. It's all on casters (we had to push it forward during 'be our guest' as a special effect), and the west wing, stage left, is hollow underneath with an access door on the back. This was so that four of the crew could push it forward and spin it right before the beast's first solo song and show the balcony. It was an awesome show to work on, and apparently to see, as by the second night it was SRO. The actors did amazingly well, and I had so much fun working on it. Now just to wait for next year!