Last post I discussed objects and their behavior. This post will cover the attributes of an object and how to manipulate them to cause a certain behavior. Every object has attributes. To make this clear, I looked up the definition of “Attribute” on Google and here’s what it said:
Ruby’s object oriented programming is hard for me to get my head around. To help me understand OO Ruby better I’ve decided to write a mini-series solely focused on the concepts behind the programming.
I’ve found when learning anything, it’s best to look up the definitions of the words themselves. What is Ruby programming and what’s it used for? Let’s ask Google:
Coding a project from scratch can be quite an undertaking and it’s easy, normal even, to get overwhelmed by all the many things that go with creating something from nothing. I hope by the end of this post, you will be more confident in your ability to really get the job done and to do it well.
Like anything else, projects are best accomplished by breaking them down into smaller steps. Before you even begin to code, you must plan several things in advance to have on hand for reference. Picture the project as this mass jungle of things to do and only you, the explorer, can find the right path by creating a map of which direction to take.
When I first began coding about one year ago, I kept thinking to myself, “When I’m a developer, I will understand this concept/language/tutorial better.” Little did I know that by typing that first:"Hello, World!"
and deciding to continue from there, I was already a developer. I could go on to explain what exactly a developer is but I’d rather keep this blog post about what to do and what not to in your coding journey. Coding is, after all, a journey and not a destination. I would like to keep this short and just give you a little help for how to give yourself room to be human while learning to be a developer.