highwaytorails

[highwaytorails]

The final blogpost... maybe...

Sigh... Summer of Code is OVER! 

This might be our last blogpost...

Or it might not be...

As of right now, we're sitting in a cafe somewhere in mitte (the mitte of nowhere), using free internet to write this final post since we can no longer write our blogposts from Absolventa. 

Yesterday was pretty amazing. We spent the morning implementing a new feature with Carsten (a new model), and we were once again blown away by his ability to quickly program complicated code and test it simultaneously. We will do this too one day! We promise!

We had a great final lunch with the whole IT team at our favourite noodle place on Prenzlauerallee, and then headed back to the office to put the final touches on our app. It was already pretty awesome, but we had to fix the ReadMe's, figure out a few command line things, and build the gem. So, we quickly scoured github for our favourite ReadMe's as examples (Devise and TimeCop), and made ours better. 

Then, we built a gem. Yes, that's right. A gem. You can find it here and install it in your very own app if you like! At the time of writing, it already as 56 downloads but we've been assured that these are all just bots. 

As 5:30 rolled around, we started to get nervous, and ran out to buy cake for our Absolventa going-away-party-type-of-thing. Together, we stood up in front of our co-workers, red-faced and a little bit scared, and talked about our best and worst moments at Absolventa. We thanked the IT team and Absolventa profusely for all of their support and kindness and amazingness and everything-good-you-can-possibly-say-about-anyone-ness, and were then presented with THE BEST PRESENT IN THE ENTIRE WORLD. Not only did we each get a 15 euro gift certificate for Amazon, but we also got a gift certificate for BUILD AN APP WITH COREY HAINES, our new favourite Ruby celebrity. Thanks guys! We can't wait to watch more of Corey wandering around his house sipping tea. 

THEN, (a lot happened yesterday) we headed back to the IT corner to demo our app. Duana and Julius from Soundcloud, and the Rails Girls Nina and Maja came to check it out as well. A surprisingly large amount of people came, and even though a few told us afterwards that they had no idea what we were talking about (welcome to the world of IT!), we were happy with how it went.

It was also the perfect opportunity to award Christoph, Robin, Ronald, Daniel (thanks for coming Daniel!), Markus, Felix, and Carsten with their presents. We made Felix and Carsten t-shirts, and the others got honorary Rails Girls framed certificates. Here's Christoph with his!

After saying goodbye to Absolventa, we headed out for drinks. Carsten's old job had a ritual of drinking white russians with every launch, so we headed to local Big Lebowski watering hole, aptly named "Lebowski's". It was an awesome evening, and we wish that we'd done it more throughout the summer. 

Final (weekly) wrap up:

We're a bit sad it's all over, but at the same time, it just means this is the beginning of a new and exciting chapter. We learned so much over the summer, and were exposed to an exciting, complicated, and inspiring world we never knew existed. For this we have, first and foremost, Absolventa to thank. They provided us with amazing coaches, a fun and comfortable learning environment, and endless hours of silly chats on the Dev skype chat. We're gonna miss you all!

Thanks also to the organizers. We know this was a volunteer job for most of you, and you somehow all managed to remain friendly, kind, and helpful throughout the whole thing. To Fanny, our supervisor, you are amazing, and your emails and constant support and words of encouragement cheered us up every single day. 

And Tobz... what would we have done without you? There are no words. 

Wow... we're done with summer of code. 

We bet you're all reading this and thinking, "oh no, now that Tam and Susanne are no longer coding together on Event Girl, what will we do for entertainment? What blog will we possibly read that has the same level of intellectual stimulation and adequate amount of ridiculous pictures and cat and DevOps gifs?"

Have no fear internetz, we have new blogs now:

tamlearnstocodewithoutsusanne.tumblr.com

susannelearnstocodewithouttam.tumblr.com

They're not, so to say, fully functional at the moment, but don't worry, they will be soon, and you can continue to follow our coding adventures.

Now... there's nothing left to say... so please excuse us while we dance in three months worth of ripped up index cards. 

[highwaytorails]

Day 63 - 30.9.2013 - Last Day!!

Ok people, it's our last day of summer of code!

But unfortunately, our IT department is so awesome, that we haven't had time to write a blog post.... and now we're going out for drinks. But don't worry, we'll write you all a proper blogpost tomorrow that will talk about our whole experience and maybe even have a few pics. 

See you tomorrow! Don't go anywhere!

[highwaytorails]

Day 62 - 27.9.2013 - Fine-tuning (der Feinschliff)

It's our second to last day! How strange! Just think, this time next week we'll be... well... we don't know where... but... we won't be here, that's for sure. 

This morning we started off by looking at our app... gazing at it in all its glory... and wondering what else we should do. We finished off the cron job and rake task yesterday, so we could rip up our second to last index card.

Only one more to go! (and it's basically Carsten's job anyway...)

So we started fine-tuning. We changed the email format a bit so that the email's subject can be set by the user, and also so that they'll be informed as to whether or not their event occurred (which is kind of a big deal...) We also made various aspects of our app more user friendly, and cleaned up the ambiguous terms a bit. (Matching Direction = Forward/Backward.... we assume this makes sense to no one but us). Along the way, some of our tests started failing, but we managed to clean these up in no time. Oh yeeeeeeah.

We also went for lunch with Julius today, our guerrilla coach, and gave him his present! All the RGSoC women in the building signed a mug for him (with fancy porcelain markers) as a thanks for all his hard work and his whiteboard sessions. Thanks so much Julius! We hope to keep learning with you after the summer is over!

Oh, and we deployed to Heroku a couple a times... no biggie. 

Weekly Overview: WE DID ALL THE THINGS! This week was pretty cool, we got to see our app in action, and the rake task and cron job (something we've been talking about for ages) were finally implemented. We were also incredibly distracted applying for jobs, thinking about jobs, asking people to hire us... you know how it is... Speaking of which, please hire us. 

Goals for next week: Don't accidentally delete everything...

And, so we don't forget:

write GitHub ReadMe (gem and app)

fix pagination

release the gem

connect remote side app 

try not to cry :(

[highwaytorails]

Day 61 - 26.09.2013 - Cron Job, Rake Task, being sick

It's getting cold in Berlin! We long for the days when we were stuck to our office chairs and all the fans were running on the highest possible level.

But let's not complain about the weather. Our App is up and running (on staging, though) and even Susanne's mom has access to it now. 

The cron job we had kind of already finished yesterday, with the help of the whenever gem. Turns out, heroku might have something against whenever. We'll fix that tomorrow.

So this morning we started off with implementing our rake task, which in turn will be called by that cron job. Our rake task lives in lib/tasks/matcher.rake and looks like this:

It is calling our run method from our matcher class (the heart of our app). If we now type "heroku run rake matcher" alarm mails get sent out! Let us know if you want to get one too!

That's it for today. Two moar days and we'll be like this: 

Sniff.

[highwaytorails]

Day 60 - 25.9.2013 - Kleinigkeiten, Heroku-Spaß, Cron Jobs

Today was self-imposed bug fix day, so we spent the morning looking through some of our github issues and picking out what we thought was a priority. Susanne fixed the bug in our expected event form that didn't recognize Incoming Event titles selected from a drop down, and Tam fixed the selected dates calendar so that when an event is selected for today it's considered to be active (before it wasn't). 

Then after a lovely lunch at the local noodle place, we noticed that our ol' twitter buddy Corey Haines had released a coupon code on twitter valid for the first 20 ppl who downloaded a "Build an App with Corey Haines" episode. We quickly signed up to cleancoders and popped in the code and now Tam has episode 1 and Susanne has episode 2!!! (The first 5 minutes of episode 1 involves Corey wandering around his apartment drinking tea... it's awesome). We tweeted thanks, and of course, he tweeted back. 

Following this excitement, we took a look at Robin's feedback from his exploration of our app last night. After signing in to Heroku, we noticed he'd added a few strange events...

What were you doing last night Robin???

Anyway, we made the changes, and our app is now better for it. Thanks! One of the suggested changes was making an Incoming Event button in the nav bar (before you just clicked on the Event Girl logo and that directed the user to incoming events). We did this, and then we wondered... what will happen when we click on Event Girl? We decided this was the perfect opportunity to make a dashboard, so we quickly made a controller and views and came up with this:

Looks good, hey?

We then headed back to Heroku, and took a look at the mailer. Turns out, emails weren't being sent, which is because Heroku requires the SendGrid add on for that. We installed it, configured some stuff, and now Event Girl is sending out emails again. Awesome. 

Now we're on to Cron Jobs, and hopefully they'll be running like clockwork tomorrow.

[highwaytorails]

Day 59 - 24.9.2013 - Helloooooo Heroku!

We were still buzzing this morning from our meeting with Chad Fowler last night, and the IT team was eager to hear about everything we learned. We got a lot of great ideas for our upcoming lightning talks and are officially more excited about talking in public than we were before. Thanks Chad!

After the stand-up meeting this morning, we all decided the gem was done, so we ripped up the gem index card. Carsten then suggested we get to work on refactoring our code, deleting white spaces, and fixing indentations. So after spending much of the morning (and then some) going through all of our code and changing various things (and of course running rspec periodically to make sure we didn't royally screw ourselves), we could safely rip up our 3rd to last index card.

Then.... we deployed to Heroku, which is incredibly exciting and in theory means that the entire world can see our app... but... sorry world, it still needs some work so we're going to keep the address secret for now. However, we've entrusted Robin to play around with it this evening and test out the usability, as we're so used to looking at it we've potentially lost a sense of what's intuitive and what's not. Thanks Robin!

So, that's about it for today. We only have 2 index cards left! Tomorrow: Rake task and Cron job. And... maybe someone will hire us? Please?

[highwaytorails]

Day 58 - 23.9.2013 - Gems, issues, movin' on

AAAAAND, it works!

We're moving on from our gem now. On the weekend Tam managed to figure out the gem code (with lots of outside help), and also wrote it in python! (.... with lots of outside help). And after a crash course today from Carsten about what gems are, how they work, and what they do, we're ready to move on. 

(this is Carsten teaching a bunch of us about gems)

BUT, we did say that there was some serious lacking in the area of gem explanation... so perhaps we need to clarify what we did and why. Sigh....

SO. The gem module - also known as the .rb file in the gem. This is what was confusing us, because when gems are generated, there's a really annoying comment in the module that says "Add your code here". We didn't know what went in there, and all the blogs we read also just said "pop your code in here and then build your gem!". It was very annoying. 

Our big problem was that we didn't really know what our gem would do. At times we thought that our gem was just a pretty packaged version of event girl, which didn't make sense to us. Turns out, our gem enables another app to communicate with Event Girl which will be running on an external server (probz Heroku). In our event girl gem, the code we wrote was a method that makes a post request. It's called "send_event". It requires a user to define a url for the event to be sent to, an api token, and of course a title. That's all it does! Once the gem has been included in one's app (or in the console), a person can type the method with the parameters, and then an event is sent to event girl, it pops up in the incoming event index, and a successful return value is printed out in the console. It's pretty cool to see....

Another problem we had, was imagining where this method would be used. Basically, we're not supposed to care. It's not our problem. BUT, it can be used anywhere in someone else's code when they want to send an event to Event Girl. 

So that's it! Our biggest hold up was probably that gems are totally new to us, even though we use them all the time. But we didn't know what went in there, and why, and of course when it came to writing a method which included an HTTP post request, we were just completely lost and didn't even know that was the direction we were meant to go in. 

But now it's all done, we can aaaaalmost rip up the index card (but Carsten wants us to test it first), and then we can probably move on to rake tasks??? Cron jobs???

Anyway, now we're off to meet Chad Fowler, our speaker coach, and we're going to get our lightning talks for various important events ready! 

[highwaytorails]

Day 57 - 19.9.2013 - gems 'n meetings

We're in the midst of gem frustration.... we spent the morning trying to figure out our gem and what code actually goes in there, but to no avail. All the blog posts online explain how to create a gem with some terminal commands, and then they all stop when it comes to the module part and say 'ok, add your code in here', and then they type the build command. 

WHAT GOES IN THE MODULE!? Seriously blog people... be more specific. Once we figure it out we're gonna write a big long post about it and explain how it works because there's seriously a huge gap in knowledge happening and it's INCREDIBLY ANNOYING. 

SORRY ABOUT THE CAPS BUT WE'RE FRUSTRATED.

Then we gave up and had lunch. Robin, however, was super nice and tried to explain it all to us, using a whiteboard and everything, but we still don't really get it. 

After lunch we headed to Soundcloud to meet Kate Ward, who is a site reliability engineer at Google. She was incredibly nice, and talked about what it's like to be a women in IT. She's been coding since she was 9! We're jealous. 

Then we had another learning session with Julius where we learned about encryption and once again feel the need to encrypt our emailz.

Just a quick note: many thanks to Soundcloud for being so supportive of the summer of code, and for letting us non-soundcloud interns tag along to all these great events they are having. We hope we can keep participating once the summer if over!

Ok, that's it. We're both not in tomorrow... which I guess means we have to do our weekly roundup.....

Weekly overview: We did not... do all the things. :( In fact... we did very few things in part due to being distracted by our job hunt. Which means next week is gong to be very very busy. 

Goals for next week: Do all the things for realz this time.

Oh, and we're going to have a launch party on September 30th. Stoked. Please hire us. 

[highwaytorails]

Day 56 - 18.9.2013 - building gems, fixing issues, bookclub

The summer is drawing to a close, the weather is getting colder, and our days here at Absolventa are almost up. With our future unemployment just around the corner, we spent the morning writing some cover letters and freaking out about the fact that we will soon hit the job market, and compete against each other. Of course, we're very nice people, so we're helping each other out with everything, and wish the best for each other. *sniff* (please hire BOTH of us)

We have 4 index cards left, so Tam started tackling the card to clean up and refactor code, and also fixed a few random issues floating around on github. It was pretty awesome to see a git commit with so many changes (although most of them were just annoying white spaces....)

At lunch, Susanne was super fleissig and went to the 7 x 7 bookclub at Soundcloud. The Ruby chapter is now done, next week, Io! 

After lunch we BUILT A GEM. It's not working yet... and we haven't executed the build command yet... but the 'initial commit' has been made and it's pretty exciting. This is what Susanne looks like when she's working.... look how much she cares about our app!! It's almost terrifying...

Now, we're off to watch some more IT Crowd with the IT department.. and we'll leave the hardcore gem work for tomorrow. Bis dann!

[highwaytorails]

Day 55 - 17.9.2013 - Our app kinda works!

Oh my god. The construction was loud today. So following our stand up meeting, a couple of us headed downstairs to the conference room to work from our laptops. Unfortunately, migrating to postgres was not something our laptops were prepared for, so we had to migrate aaaaall over again. This, of course, is good practice, and we might just be pros at it by now, but it's annoying. Luckily, Tam already had brew and Xcode installed so things went relatively smoothly, Susanne, however, was not so lucky, so much of her morning was spent sitting... and waiting... for Xcode to install and for things to work.

Tam in the meantime tried to get the test working for when a remote_side_id is automatically assigned to an incoming event. This didn't go so well, so we had to turn to Carsten for help in the afternoon. However, THAT part of the app is now done, so we got to rip up an index card. Only 4 more to go!!!

(Notice how crisp and clean this photo is? It's from Susanne's new smartphone!)

Then we uncommented a mysterious piece of code in our Incoming Events controller that sends an alarm if an incoming event title and an expected event title are matched. We thought, hmmmm, what if this works?

So we created an expected event with an alarm, created an incoming event with the same name, and then.... GOT AN EMAIL! (sorry for the bad pic)

We gasped with excitement, and Carsten promptly told us that he'd miss "the occasional super-excited 'huh!' come October. " Awwwwww.

Tam then played around with the clickable columns again, and Susanne tried out some stuff in the console (specifically to do with the tracking of our events, as it was confusing us a little bit but now we think we're no longer confused......)

In other news, turns out Rails Girls Paris are going to be having a workshop while Tam is in Paris for dotRB, so she's going to join and... gaaaaasp, COACH. Scary stuff. Let's hope she has help. 

And of course the most pressing news of all, is that no one has hired us yet. Please hire us. We want to keep learning! 

[highwaytorails]

Day 54 - 16.9.2013 - merging and testing

First thing's first. This morning we immediately merged our postgres branch from friday into our master. Now, we're both no longer using sqlite, are rockin' the postgres, and are totally ready for deployment to Heroku. 

Unfortunately, our app isn't.

For most of the day, we sat down with Carsten and wrote tests for our incoming events controller to check for xml and json files which will be the standard format sent by remote sides. This took a while... we're still confused by tests... and haven't really done any controller tests for a while. The biggest problem was allowing a remote side access to the create section of our app despite our logged_in requirement. But, now it's all up and running and our tests are green. Then we merged, and Travis stopped complaining that event_girl is broken, which is a relief to all of us.

In other news, please hire us. 

[highwaytorails]

Day 53 - 13.9.2013 - more APIs and sneak peeks to the future...

It was very very loud today. The windows of the building are about to be taken out and replaced, so construction workers were tramping around, putting up dust protectors, and drilling various things. Most of the office is now squished into a few select corners, and everyone is wearing their headphones.

In between comments about how loud it was, we researched APIs a bit more. Carsten wrote us a nice long email last night answering some of our questions, and today he told us 'this is a perfect opportunity to test.' So we took a look at our incoming events controller, played around with it a bit, and then decided this was something to leave for Monday. 

We then moved on to migrating our database to postgres. Following Ryan Bates' example in his Migrating to PostgreSQL screencast, we first made a new branch on github, then we updated brew, updated our postgresql, changed our database.yml, installed the pg gem, did a rake db:migrate, and everything worked! It's just that easy. Now our app is ready for Heroku. How amazing is that! We just need to connect a few dots and then it'll be ready for the world to see.

Weekly Overview: The beginning of the week was going pretty well, we created MVCs with the snap of our fingers, and our app got prettier. However, being stuck on the API is pretty annoying. We feel blind, not knowing where to go or how to get there. Felix, however, says we're almost done, and the next few tasks will fly by. This week we also started the job search, and have a few leads.... (however, please hire us)

Goals for next week:

[highwaytorails]

Day 52 - 12.9.2013 - APIs, book clubs, and googling

We're a bit stuck at the moment...

And distracted....

This morning we tried to fix our API issue and sat with our heads in our hands for a while trying to visualize exactly how an API works, specifically, how it will work in our app. The way we understand it, a user signs in to our app, creates a remote side application and generates an API token. They copy and paste the API token somewhere into their own app (we don't care about this part), and then their application uses the API token to access our app and send our app incoming events. So, the part we're stuck on, is how our app then receives these incoming events from an external app. We can't explain much more than this yet. We have code, we're just not sure what it does, how it works, and how to check to make sure it works....

So unfortunately the rest of the day was spent googling and trying to figure out what it all means and how to implement it. Everyone but us seems to think it'll be a piece of cake.

Just after lunch we went to Soundcloud (again....) for a 7 Programming Languages in 7 Weeks book club. This week and next we're doing the first chapter (Ruby), and then we'll be on to Io. 

So, yes, distracted. Absolventa's jobnet was just relaunched, much to the excitement of everyone and especially the IT team. It looks pretty awesome. So there was cake and champagne. Now all the windows are being taken out of the building so all the desks are being moved around and Susanne is freaking out. "I can't work like this!" she says...  We'd love to talk about more but we're about to be literally pushed into a corner away from the windows...

[highwaytorails]

Day 51 - 11.9.2013 - model tests, clickable columns, API tokens, winning contests

Like all good programmers, our day started off with some rspec tests. Unfortunately, not like all good programmers, they took up most of the day. The tests were for our remote_side model, and we thought that we had to test the method that generates and API token for us. We weren't entirely sure why we had to test something that Ryan Bates had done, but we tried to do it anyway. After many frustrating hours, we called Carsten for help, and turns out that since the method is a private method, we don't have to test it at all. Sigh.... but this didn't stop Carsten from showing us how to do it anyway. 

We then had to quickly fix a test for our incoming event controller which now incorporates our forward matching direction. We thought this would be very difficult, as it once again made us briefly revisit our scopes, but all we did was adjust our factory and the tests passed. We hope this was the right way to go...

Periodically throughout the day we were also frantically checking our emails and twitter because of the RGSoC game. Each team was sent a picture of a fish, giraffe, unicorn-seahorse and octocat, and each team has the same pic as another. Without sending the pics around, we had to find the team with the same picture as us (using descriptions etc...). After receiving numerous emails from teams all over the world, we figured out we were paired with the punchgirls from Argentina, and we came in second place! Now we gets lots of cool books and rails girls swaaaaag. 

Then Tam went on a bit of a detour trying to figure out how to make our index rows clickable. Thanks to some fancy cut and paste javascript and css, our tables are now awesome.

Meanwhile, Susanne was off trying to figure out our API token. We need to make it so that a machine can access our website with its API token as well, not just people using their passwords. This is kinda difficult... and shall be continued tomorrow. Then, we'll be able to rip up an index card. 

Now we're writing the blogpost. And Carsten's talking on the phone...

[highwaytorails]

Day 50 - 10.9.2013 - Remote side, views, API tokens

Today was kind of a cool day. It was one of those days where we realized just how far we've come, and simultaneously how far we have to go. Last night we started setting up the RemoteSide MVC and ran into a few template errors. But this morning, we were relatively quickly able to diagnose the problems, and then when faced with other little problems, diagnose those too (mostly extra s's or missing s's). Back at the beginning of July this would have derailed us for hours, but now that we're chugging along the highway to rails at a good speed, we flew right on by. That means we got to rip up an index card:

We also managed to set up an API token. This was pretty difficult, as we're but poor newbies and had no idea what an API token was, or what an API was. Unfortunately, the internet doesn't really seem to understand that beginners need beginner explanations to such an important topic, so we googled for a long time. We couldn't really visualize what an API is, or who uses it, or why. This is a pretty good article for those of you who are just as confused as we are. 

So now, when a new remote side application is entered into our app (at this point just via a name), an API token is automatically generated for them. (Thanks for the code Ryan Bates!)

Then we had a bit of a chat with Carsten about what our app will look like in (hopefully) two and a half weeks. This freaked us out a bit and we feel like this (Tam thought we were almost done, looks like we're not):

(gif courtesy of DevOps Reactions)

In other news, last night we headed to the Travis offices to celebrate their all-round awesomeness and support for the RGSoC. There were balloons, gifs, and cake (which was amaaaaaaaaazing. We want more please inchworms!):

Also, no one's hired us yet. So please fix this issue. Thx.

[highwaytorails]

Day 49 - 9.9.2013 - Play by Play, Haml, CSS, Client side

This weekend both of us were busy bees: Tam got some CSS beauty done and Susanne introduced Event Girl to Haml. Our first task today therefore was to merge our two awesome branches into our even more awesome master! 

Then we continued with watching an episode of play by play with programming masterminds Corey Haines and Aaron Patterson. In this episode both of them are - just like the two of us - working on an event tracking system. Theirs is almost as good as ours. Good job guys, you're well on your way! While we're watching we tweeted Corey Haines and Aaron Patterson and to our surprise Corey tweeted us back. We believe that our coaches, or rather the entire IT department, are jealous of our new tweeting buddy. 

After we calmed down, we continued working on our index cards. Next up: Creating a Client Side MVC. This feels like the good old days (two months ago) when we were just starting our app. But now we are playing around with Haml and Simple Form as well. 

Another very important thing that happened today: We put up a new link on our blog that is called "HIRE US". It's pretty self-explanatory. Please click on it - and hire us. Thanks!

[highwaytorails]

Day 48 - 6.9.2013 - test 'n MEEEEEEEEEEERGE

We're not quite sure what to think about today. So many things happened, and there's no way we would have been able to do (most of it) ourselves. So, huge enormous mega bombastic thanks to Carsten. 

Before lunch, we headed back to our scope tests to figure out wtf was going on there. At this point, it feels like a lifetime ago.... Our 'today' scope wasn't working because our SQL database was interpreting it wrong, so we had to change the syntax a bit. By lunchtime, all the tests we had written together were working.

Then after lunch, we tried to write the last few tests by ourselves, but discovered that one of the ones we had written before lunch wasn't working anymore. This, is a stupid time issue that is hard to resolve and doesn't make any sense and is dumb. Punkt.

We came super close to writing the test for an alarm to be sent if an incoming event is NOT found, by ourselves. We were so close we could taste it! But... it was wrong, and after sending Carsten a crying emoticon, he came over to help us. 

Then.... all the stuff for the matching branch was done, and we could finally MEEEEEEEEEERGE. This is what it looked like:

1) We type git merge matching

2) Carsten explains stuff to us

3) There's a merge conflict

4) The merge is successful and we drink a beer

Weekly Overview: We felt dumb this week. Things were moving a bit slow, and we needed a hell of a lot of help from everyone. Tam felt like "a useless piece of shit", and Susanne as well. Maybe we jinxed ourselves last Friday when we said "This week was amayzing. We finally feel like we’re getting to the core of our project and are starting to feel like developerz." Sigh... so naive....

Goals for next week: Finish up the rest of the index cards, which includes creating a client side library, something to do with API tokens, and perhaps a rake task? We should also probably start reading up on deploying to Heroku and changing to PostgreSQL. We should also maybe learn to stop jinxing ourselves, but you have to celebrate the little things, right?