Hello World. It's me, Ariel.
Javascript…
the ellipses say it all.
I mean, it is just day 1. But it’s definitely hard getting used to its idiosyncrasies after Ruby. -0?! That must be the most creative number I’ve ever seen. And 3 equal signs is just too much. Typing out .equals is almost faster. At least it would be a little more english-y than a row of ===.
But. I do like the return of semicolons, explicit returns, and (kinda) explicit declarations. I know. I’m weird like that.
Reinventing the Wheel…
…using a wheel. Ha.
After the longest assessment we’ve ever had (2 hours!) this morning, we continued on to RailsLite, aka our introduction to handling server requests/responses. All I can say is that after just 1 day of it, I’m glad the Rails guys blazed that trail for me, haha. Even with several layers of abstraction built in already (Ruby, WEBrick, and some of the Rails functions), things that seemed simple before suddenly required serious thought. For example, parsing parameter hashes. Sure, the straightforward params[key] = value pairing was simple enough, but once you add in multiple layers of nesting ( params[key1][key2].[key_x] = value ), how to construct the proper nested hash?
More details…
DiscoverIT
To continue with my series of really terribly named Rail projects, we made a RedditLite spinoff called DiscoverIt. (Can you believe it actually took a thesaurus to come up with that awful name?) The project itself was relatively straightforward until the end, but afforded good practice with setting up a shell of a site, complete with user sessions, ability to submit/edit/remove content, etc. The “cross-posting” feature was a cool new thing in that it introduced us to yet another amazing ActiveRecord feature, the ability to not only auto-populate foreign keys, but even create rows in many-to-many tables, based purely on associations. Once again, I didn’t really think it would work, but why do I ever doubt ActiveRecord?
More details…