Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
My Résumé
Nicole Moore
5203 Chrysler Drive
Apt: 608
Detroit, MI 48202
I’m a programmer and graphic designer with a long history in Adobe Photoshop, as well as Livejournal (2002, onward).
<b>Outside Contractor - Hilton Gardens Inn, Detroit, MI</b> — 2008 Assisting then-Human Resources Manager Sandra Collier with writing up and fact-checking the payroll list.
<b>Impactor - Mervyns California, Dearborn, MI — 2006</b> Clearing the sales floor and straightening merchandise during sale hours; returning merchandise to its proper location, on the right floor.
<b>Code School (Now part of Pluralsight):</b> Electives Mastery, HTML/CSS Mastery;
<b>Team Treehouse:</b> (;
<b>Oak Park High School (1999 - 2004)
Oakland Schools Technical Campus (2002-2004)</b> Oak Park, Michigan 48237, Royal Oak, Michigan 48073;
<b>University of Saint Francis - Fort Wayne, IN — Majored in Pre-Medicine. (2004 - 2007)</b>
<b>University of Michigan - Dearborn - Dearborn, MI — upcoming</b>, concentrating in both Pre-Medicine and in Computer Science; Proposed Entrance Year: Winter 2019;
<b>Skills:</b> I began programming in and of itself after March 2nd, 2004, when I first opened my Livejournal account, though I didn't realize it at the time. Other experiences include zip and country code swapping, add-ons, and friend tagging in Foursquare.
Over the last decade they've each overhauled their layout formatting, and mission statements, but in the beginning for Livejournal, all formatting of entries was done entirely by the account holder. This exploration included tags -- such as those for text decorations like italics, bold, and underline -- header declarations, and importing external cascading style sheets to personalize your Livejournal to a great extent instead of just choosing a prepared layout. A perfect example of this type of web design is Mark Zuckerberg's plain formatting of text in <i>The Social Network</i>'s opening scenes.
I began Livejournaling after that point (2004 as opposed to 1999, when Brad Fitzpatrick first created the site), but soon enough in time that Style 1 involving a text box for CSS was still the norm (it's now mostly a defunct option by early to mid-adopters and requires you to know where it is to utilize it) and each journal entry as well as the overall layout still needed direct formatting for text decoration. The same goes for implementing multiple windows to refresh and check any CSS you've applied to your journal layout style. So, from the beginning, I was unknowingly being introduced to HTML and CSS.
This was during my senior year of high school when I was attending Oakland Schools Technical Campus - Southeast in Royal Oak, Michigan for a three-hour-a-day course called Visual Imaging. As I stated in my first article written on LinkedIn, at the time, I wasn't actively looking to learn anything about computers and didn't realize that nearly everything I did in my free and academic time involved working closely with both the internet, as well as programs such as Adobe Photoshop and Quark Express (now also defunct).
Once I started college, I focused mainly on goals toward medicine, as that has been my goal for the majority of my life and, at first, I didn't see any reason to pursue computing in any way.
This ambivalance changed in February 2013, however, my sister asked me to try out Team Treehouse because she thought learning to program would be something I would enjoy. I found Code School on my own, as well as General Assembly, but my sister's encouragement led to me finally having what could be called an 'oh yeah...' moment about what had been floating around the periphery of my life for such a long time I never noticed.
With her assistance, I became involved in the Girl Develop It! - Detroit Meetups for various subjects ranging from responsive web design to learning more about utilizing Git in the command line, as well as through graphical user interfaces such as Github for Windows and Github for Mac, GitExtensions, TortoiseGit, and SourceTree, GitKraken, as well as Tower, two Git GUIs I'm very fond of. I have been working on Git longest of all, but have been beginning with Ruby, Ruby on Rails, and Java, as well as some beginner's work on R.
I'm looking to continue learning many different languages and tools and am fairly astute in the formatting mechanics of Javascript, though Sitepoint is helping me expand into the technical and other aspects through their Javascript: From Novice to Ninja manual by Darren Jones (
In the roughly five years since beginning lessons on Team Treehouse's site, as well as Code School (now absorbed by Pluralsight, which I have used less frequently) and much more recently General Assembly, I've begun branching out into Sass and even Objective-C, the last of which has been quite a challenge.
I have really been enjoying how exciting figuring out aspects that leave me stumped has been and have noticed that if something doesn't make sense as explained by one outlet's format, there's a huge chance that I'll find an explanation that works for me in another arena; once I go back to the original explanation later on, I have found that it will then make sense.
Switching between learning styles has allowed me to see each aspect in multiple viewpoints, which allows me to grasp a concept sooner and more easily than doggedly pursuing the same directions for weeks on end. I've also had to be more flexible with feeling as though not finding the answer all by myself is not considered cheating, as formal school rather pounds that idea into students, leaving someone like me really reluctant to go searching for an answer someone else already found.
StackOverflow and Project Euler both avidly encourage research to be shared and through working in their forums I'm now comfortable with this concept not being anything other than sharing of information between informal partners.
Another view that has changed since I started was making myself comfortable with my brain's style of learning and accepting the score-related consequences of needing to see code formatted in the example being asked about rather than blindly guessing over and over in a vain attempt to get all the points for the exercise.
I am more at peace with the idea that what I see spelled out for me is easier for me to grasp than beating myself over the head about a rigidly defined code and what are truly arbitrary numbers.
The information to be learned is far more important than the points awarded for what would amount to me being supposedly psychic. I have an affinity for visuals with particular regard to color and shape; I’ve been working with Adobe Photoshop since my Junior year of high school and still enjoy creating graphic images for both professional and extracirricular reasons.
I am also now well-versed in the Git Distributed Version Control System and enjoy working with HTML/CSS and several languages, such as Javascript, Java, and Ruby. I am now focused mainly on learning Back-End and Security through Team Treehouse's Developer and IT training topics. When Elance and oDesk originally started, I took the aptitude tests for both Git and Adobe Photoshop and tested as proficient in both.
<b><u>Character and Social, Professional References</u></b>
Julia Markey,
Angela Alles, {* Talia Selitsky, (
Nicole Exel-Rodriguez (
Aisha Blake ( */}
Jeseekia Vaughn (
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.