Well met! Come take a seat and I will tell you how I created my CLI Gem Project and somehow got through it. Fair warning it might be very lengthy. I haven’t mastered the art of being short and concise with my words. I will now try and explain my thought process on how I created my CLI Gem. (Note: I already see that there are some issues I’m having with my gem so I will be getting help on it before my one on one on Oct 16)
I don’t know how I got here But I did.
Well hello there, thank you for stopping by! I am almost done with OO Ruby and therefore about to start my CLI Gem which I will be writing many blog posts about, for that I am sure. This is just a quick post, to remind myself, and anyone else who is struggling as much as me that errors are NOT bad, but they are good! Even though I know they are important to code, and you need them, I still worry and freak when I see them. I get frustrated and think I’m not that smart. But once I calm down and read my errors, such as the one below, I see that they are telling me exactly what I need to do to fix it.
Well I didn’t think this day would have come so quickly or ever really. I have had such low confidence in my Ruby skills and I still do.
Boy, was I wrong. I thought because I didn’t have a job I could do this full time aka 8 hours a day 5 or 6 days a week. What I didn’t account for was my actual life and what I need to do for my recovery and my own sanity. I wish I had that ability to just hunker down and stare at the computer for 8 hours a day and study every day but I DO not and I’m not ashamed to admit that. I have been getting up earlier and studying more, which feels good. However, last week I got a terrible infection and sty in my eye which prevented me from looking at the computer screen for a week so now I’m back at it. I feel like I’m opening up a dusty book. Once I’m out for a week I really don’t know what I’m doing.