End of first week of class

The first week of Coding (Programing) Immersion class was a little information overflow.   Our homework for the week was to create a simple website with HTML and CSS.  I did not completely finish it as I have to know the reason why something work a certain way.  I could not just copy and paste stuff from other websites and play with it.  Also our end goal with this class is to able able to create a website with Ruby on Rails.  So I went through the tutorial on creating a Ruby on Rails website.  That way I could make notes on it and notate the reason why and how a line of coding was being used.  I may not have finished the project, but I have a much better understanding of coding a website with Ruby on Rails which also uses HTML, CSS and JavaScript.  I am okay with that.

Usually we have Friday off, but we had a field trip to ThoughtBot and then one of the senior programmers there came back to class with us and gave us some good advice on Developer Survival Tactics.  It was a great presentation.

Here are some of the notes:

  1. Get involved in Open Source.  Since everyone looks from a different perspective, you may find an error or see a way to improve a file.  The developer will not know something is wrong unless someone points it out to them.
  2. Open Source allows potential employers to see your involvement and will put you ahead of the list of potential employees.
  3. Do not be passive.  In other words continue learning and keep up with the changes in the industry.  Shoot for one technical book a quarter, one new technology a year and 2 hours of practice per week (not work).
  4. Blog for yourself as you will forget a lot and you can go back and find something you had forgotten about and be able to use on a project you are currently working.  This is great for employers to look at to see what you have done and how you present it for others to be able to read.
  5. Code review.  Always have someone look at it, as chances are they will find something you missed and you may find something can use.  And you should review someone else’s code.  *Also if your co-workers and boss to review your code, if the company does not do code reviews . . . RUN!
  6. Always offer praise and improvement tips.
  7. Always reconsider your decisions as it is still relevant.
  8. Get social.  Attend the local Ruby users group and volunteer at hack nights to other beginners.
  9. At last and most important, get away from the computer and spend time with friends and family!!

I hope this helps someone and I know I would not have thought about some of this without someone pointing it out.  😀


2 Comments (+add yours?)

  1. sounja
    Apr 27, 2015 @ 22:52:28

    Congrats on surviving your first week of class:) You mentioned the importance of getting involved with open source. Did the speaker mention how to do that?

    Liked by 1 person


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Grit Flow

courage, resolution, strength of character

life as seen by me

how my mind works????

The Wacky World of River Hayden

Yes, I am weird. Yes, I am proud of that.

Love Yourself Again

A safe space of solace, understanding, and healing

homemade naturally


Ctrl. Alt. Believe.

One Tech Novice. One Programming Boot camp. One Heck Of A Journey!

My Free Zone

My space unit about my life,the people around me and the happening's.


My words will either attract a strong mind or offend a weak one.

padrespaleale's Blog

Musings and reflections on an ordinary life.

%d bloggers like this: