Skip to content

Instantly share code, notes, and snippets.

@amaseda
Created May 5, 2015 12:52
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save amaseda/efdf83f427f48fcd998f to your computer and use it in GitHub Desktop.
Save amaseda/efdf83f427f48fcd998f to your computer and use it in GitHub Desktop.
w07d05 hw
The transition from Ruby to Javascript hasn't been as jarring as I expected it
to be. As the teachers mentioned a number of times, it's true that by knowing one
programming language you will pretty much be able to understand
80% - 90% of another. While matching methods between Ruby and Javascript
hasn't been too tough (although it's taking a lot of getting used to), wrapping
my head around control flow and the call stack has been a bit more difficult.
There have been plenty of instances during JS homework assignments where the
code takes on a life of its own. Variables and functions are declared left and
right, mysterious and undecipherable errors pop up on the screen
and what was meant to be a simple timer app ends up morphing into a crazy
Rube Goldberg machine. On top of that, the need for callbacks makes knowing
when and how to call functions less straightforward. I assume once we dive into
classes and object oriented programming, this will become less of an issue.
But so far, keeping code organized in Javascript has proven to be a lot harder
than with Ruby.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment