This blog is intended to follow my activities as I traipse my way through learning to be an adult. Hopefully this will encourage me to write more often for my family and friends and give me an outlet to talk about the things that mean something to me. All of the opinions in this blog are mine, unless otherwise stated and I welcome comments and critiques, as well as discussions. So lets make this a fun experiment.

Tuesday, February 5, 2013

Programing Headaches

So there are good days and bad days with my programing experiences. Good days I figure out what I'm supposed to be learning and manage to get a little closer to it, or actually successfully complete a piece of code. Then there are the bad days, days that I can't seem to do anything right. These days are so incredibly frustrating I just want to hit things and cry. It doesn't help when my computer is so slow that it takes 30 seconds for a word to show up on the screen when I am typing, but that isn't this blog post. So I'm working on something right now and I can't find the key words I need to understand something, which of course means I am spending %1000 more time on every little thing and far more than I actually should be. This is frustrating, so frustrating that it makes me want to say "screw it you stupid piece of S*&^$#%".

As it stands I have spend most of the afternoon on this problem and have absolutely no freaking way to fix this problem until I can ask Jayson. This sucks, quite a lot because I just wasted the whole afternoon on some jumped up piece of C*&%$. So I am nowhere near getting the things done that I need to get done and am so frustrated with everything I could kill someone, especially the jerk that ran me off the freeway yesterday. P.S. thank you grand theft auto for the brake turn, spin gas combo that saved my life and the lives of anyone I would have hit on the backlash from slamming into the cement sides at 70mph.

Anyway, so I am supposed to be making 3 separate functions and then calling them to load, permute and save some data. Ok. So I did this exact thing on fri. without the separate functions. Turning them into functions however seems to be my downfall and every time I think about this stupid thing I see red and really hate myself. I am trying to make it so I can call the various functions but they don't work, well thats fine go online and find out how to call functions. Please keep in mind that these functions are the same ones that I successfully managed on Fri. Oh btw there is absolutely no information on how to call functions online, as in it doesn't exist unless I'm using classes. So apparently this lower level of programing doesn't exist. Ok, maybe I just need to look at my functions again, oh, yeah functions don't exist by that name in Ruby yet everyone uses it. Ok, its war.

4.5 hrs later...
*Scream* just kill me please, because I clearly am the most stupid person on the planet because I cannot figure out how to make these "functions" functions, let alone call them into action. I've looked everywhere. Seriously everywhere. I don't know what to do next and I feel so incredibly stupid I can't even breathe. How on earth do people learn this cracked out excuse for a language? Its bad days like this that make me want to go into something that never requires me to think ever. I know that I'll have better days but honestly, I couldn't remember the feel of success right now. Yay, hopelessness.







Monday, January 28, 2013

Japanese Hiragana part 2

So I don't seem to be having many problems with the pronunciation of the first 4 columns of Hiragana. The 5th column has a little hard part, getting the 'u' at the end of "tsu". Otherwise it's going well, I am remembering pronunciation very well and am having fun with the column pattern.

In other areas, I am working on getting myself organized and trying to get into the way I want to be. I've set up a to do list with times and all kinds of stuff. I'm trying to look at it every day and check things off as I do them. Hopefully this will make it easier for me to remember to study enough and pay attention more often. I've cut down on my Netflix watching so that I am more in the moment and listening to mood boosting podcasts when I walk or do chores around the house. I got a ton of chores done today, desperately needed today, as well as lots of studying.

Focus gone, signing off.

Friday, January 25, 2013

Rails with Jayson

So today's lesson concentrated on learning to read the Ruby core library and then using a few as case studies. This evolved into a lecture about variables and stacks when I had a slight mental issue with a string method called String.new("string"). This little gem of horror creates a copy of the "string" so the original string is not changed, it seems that this would be an easy concept right? Ah but does it really make a copy or is it tricking my brain into thinking it makes a copy? Answer: both. Yes it is actually making a simple copy, problem was I was associating variables with the "string" they were representing.

P.S. an "!" means to force a change and not copy (using string.capitalize creates a copy of the "string" and capitalizes the copy, while String.capitalize! just capitalizes the "string".)

Once that was moderately beaten out of my head we moved on to String.succ. Which of course meant we had to go through all of this again. On top of which I didn't understand why there were so many different instance variables, why name is made into @name when it isn't used for another function, and the order of the rest of the function. Basically it was a WTF? moment, again. Once we slogged through that (which included hair pulling, temper tantrums and tears), I mostly understood the point and could probably understand the file if I pulled it up....Yup I understand it, mostly.

Next was a lecture and lesson on stacks and how that all works, using a debug gem so I'd be able to see what was going on under the hood of ruby. This blew my mind for longer than I'd like to admit. Yes I know about stacks and how one would use them... vaguely. So I had to learn more about stacks and how that works using the Time class.  Not to mention the Time class itself and the weirdness that are time methods. So now I understand stacks better. How then to decode the rest of this lesson? Well first off "<=" means lesser than or equal to. Kinda important little piece of s*&*^,    *cough* comparison operator. So setting the time expectancies understood but what is that magic that makes the year the beginning of the year and not 3 weeks in!? Oh right, its the meaning of the freaking class method of .utc (which has an acronym that is actually backwards).

So knowledge gained and being slowly absorbed into my poor borg brain. Even through the crazy temper tantrums and crazy need to put my head though a wall when working on this stuff I learned something today and more than I thought I did as evidenced by remembering most of parts of the lessons for today.

if cass.sleepy? and freaking_late? (time) then
    puts "Freaking Bedtime."
else
    puts "Nap time, oh god."
end