Catching Up on Life Things

My interest in programming has not waned over the course of these last months, though I consistently hit walls and take extended breaks from learning anything new. It is the harsh struggle of learning something without the looming threat of deadlines or the presence of a mentor.

While I feel as though I haven't made much progress on my own, I have taken steps towards securing my learning capabilities. I've enrolled in courses at a new STEM school locally. Well, sort of locally. I commute an hour to attend, but my degree concentration is Computer Science and Game Design. I am well on my way to having a well-rounded education on software engineering with a focus on what makes games what they are. I would have never imagined pursuing a Bachelor's degree in Comp Sci when I graduated from high school.

My first semester left little time for me to pursue anything programming-related (damn prerequisites), but now that the semester is over, I've been cramming everything I can get my hands on about C, trying to beat the clock on these last two weeks of winter break before I start back in with a Python introduction course. My school won't teach C, but will instead jump from Python to C++ to Java. It doesn't bother me, though. C and C++ are both powerful in their own ways and I'll only benefit by learning them both. I figure I'll just skate through Java and apply the programming theory I learn to the other languages I know.

Still, I've come to realize that blogging about programming was helpful while I was actively posting about a couple of years ago. While I work on a personal project related to MUDs, I'll start trying to more actively discuss what I'm learning. So, yay! Activity!

Other life-things going on? I'm happily married now. My husband and I live with my best friend and we play Overwatch together A LOT. I lowkey enjoy Widowmaker but I'm a Zenyatta main. Might be getting back into GW2 or World of Warcraft (???) if school and projects allow, but it's probably not the greatest idea to do either of those things, considering I already moan about not having time to do stuff! I've also discovered that having just a few years of art experience has made me very valuable at school, and I'm glad to have a bit of versatility. I've done more art for game projects this semester than I thought I would and it was a lot of fun. I may post some of those up here. Since the last time I posted, I found a new favorite book series (Patrick Rothfuss's "The Name of the Wind") and I have written an enormous amount of prose for my own characters, as well as designed some content for the eventual MUD I will host.

Will I get around to posting again today? Who knows! But the next post I make will definitely be more interesting than this one.

It's Almost 5 o'Clock...

....Which means I'm fiending for my commute home so I can work on other things.

Things that I need to do:

1. I need to kick myself in the ass and stop using my shitty modem as an excuse to not work on my project. I have an Amazon Web Services server running a guild website for my GW2 guild (which has been painfully inactive lately). I should just load it up there and use that instance as a host.
2. Once I'm done kicking myself in the ass, I need to break the damn code I've been pouring over so I can see what errors I can cause and, consequently, fix.
3. I also need to continue working through the programming projects in the textbook I have (yes, that one written by K.N. King that I was working out of ages and ages ago). I post my progress on these on GitHub. I think I mentioned that last week sometime.

I was working on one project that had a do loop in it, but my logic was obviously flawed, as the loop fired infinitely. My biggest question about loops has to do with the variables... And I may post up a thought process about them so I can work out the details of how they work. I'm thinking once I have that down, loops will come much easier to me.

Also on my list: working out some actual form of balance and continuity for the project I'm working on. I have a lot of features that I want to add to the base code I have and not much in the way of structure for adding them. There are huge-scope projects, like a different login system, and not-so-huge-scope projects, like adding in a racial selection menu to character creation. Content is taking a seat on the back burner until I can get some other details in place, but I've already printed up some material that should help me with that once I can spare the time to work on it.

Now, if WoW would stop sucking up all my time, I'll be in good shape.... *starts chanting "I'm not addicted" softly, feverishly*

[untitled]

I think about this blog frequently. I think about the different directions I've pulled it in; about all the directions I've been pulled in, myself! I ought to be more regular here.

I ought to be more regular in studying the things I want to pursue, too. Here's the hard truth though... When you're not in high school or college, but in the school of the self, there is no grading scale to push you forward. There are only two states you can be: Are you where you want to be? Or aren't you?

For me, I laugh at programmer jokes because I understand them. But can I sit down and write a program? Well, maybe a really short one. It might be good for a couple of computations, but you'll have to use the console to run it. I have a hard time calling myself a "programmer" at this point.

If I had spent the last year or so working nonstop on programming languages, namely C, I'd be able to say a lot more for myself than that, I think. But this isn't a pity party. This is recognition of the truth. If I had worked harder, I would have made more progress.

I took a few detours here and there, and dabbled some in HTML/CSS. It was a good feeling to be able to build my company a website, and, in turn, host my own website for a guild I own in Guild Wars 2. I've been commissioned for a third website by my father's band. I won't say that my time learning HTML and CSS has been wasted. Even so, I'm not very good at it, and other web developers will make me feel stunted because I don't know Javascript or PHP. I started learning PHP too, but got overwhelmed with keeping these languages straight.

Now, after all this time, I'm back in the C seat. There are several reasons for this decision: I have an applicable chunk of code that is open for manipulation. Every time I make headway in a chapter of a book, I go look at this code to see how much more of it I understand. This is my way of quantifying my progress. Can I write a program? Not yet. But I can start making a little more sense of how this program is written and that is loads more than I could do before I worked through that chapter.

I keep my Github updated with recent programs I've written with the goal of working through each programming project at the end of a chapter. Some chapters have 8 projects, but lately they have had upwards of 12 - 15. It's slow going, especially when I have a wedding to plan, a full-time job to work, and all I want to do when I get home is mindless stuff. But when I write a program, it goes there. Find my Github at this link, or in my bookmarks page.

I also want to expand on that bookmarks page a bit more. As I learn things and teach myself how to do more things, I want this to turn into a resource for other people in the same boat I'm in. Those who want to learn how to do this stuff because of a calling or an interest, but don't know where to start. I was inclined to delete the posts I made that were off-topic from C, but I will leave them. It just goes to show how sometimes, distractions happen. And even if you look back at them with some regrets, you still have the experience to show for it.

I hope to be able to post things that are less dreary and more fun in the near future. Fingers crossed!!

Anecdotal Advice

My tunes for the night. This soundtrack is so amazing. The game is great, too. I thoroughly enjoyed it, and I look forward to playing the second game the same studio produced and released recently, called Transistor.

I promise I didn't come here to babble about video games, much as I'd like to. Instead, I want to babble about the furthering of ones' knowledge and skill.

This has been a recent discovery for me. I described it when I first felt it as "a desire so strong to achieve a goal that the relatively unenjoyable steps that need to be taken along the way are no longer unenjoyable". When I questioned my fiancé on what a feeling like that could possibly be, he merely named it "motivation". That's when I realized that I had not been truly motivated to do something for a very long time. Long enough to forget what it felt like.

That was in 2011. At the time, the feeling applied to my artwork, which I was using as an outlet for brainstorming a story that Andrei and I were working on together. I became enamored with the concept of MUDs after being introduced to one, and in 2012, I spent all of my time learning as much as I could about them. The desire I had to learn about them made me voracious for any information I could find, though it was quite thin by the time I started looking (most MUD information was out-of-date by 2007, with the massive popularity of emerging MMOs at the time). As I learned more about MUDs, I only became more fascinated by them. The majority of the old codebases were written in C, so I took the natural next-step and picked up C to try to fully understand them. The knowledge certainly helped when I started trying to script short programs into the MUD I build for!

Progress on that front has been halting, thanks to several projects I have on my plate that have been vying for priority. Now that I've made the overall decision to focus on HTML/CSS, I feel the same motivation driving me forward when I get stuck. I've grown to call it "possibility", personally. If I give up on whatever I'm working on, the possibility of anything coming of it will die. And, really... Anything is possible.

But, enough broad anecdote. What does that kind of motivation look like? Outside of the forward-driving force that is ones' own motivation, it looks something like this:

• Scouring shelves at bookstores for used and new books that could hold useful information
• Hunting for online resources; magazines, white papers, newsletters, blogs... anything.
• Stepping away from the games or TV shows a little earlier at night to fit a little bit of reading in before bed
• Keeping a digital copy open on the phone/tablet/computer on the off-chance that a 15-minute span of time pops up to allow for some quick reading
• Writing a lot of code
• Making lots of mistakes
• Reading or talking about those mistakes and finding industry advice on how to avoid them
• Making more mistakes, and hopefully, some visible progress

At least, that's what it looks like for me. I was lucky enough to stumble upon a used book published in 2004 for $6 that focuses on web standards for HTML and CSS. Inside, the author made heavy reference to his blog, so I went to see what he had to say. The blog hadn't been updated in a year or so, but even so... Thankfully, HTML and CSS haven't changed too much in the past 10 years, and the changes that have been made are very helpfully documented on the W3Schools Website. With that being the case, this blog is a fount of information. Additionally, the author often references a great deal of other resources. While reading through his blog, I found myself bookmarking every other page I visited for the quality of content I read. Some things were a little confusing, being marketed to web designers who have been in the industry for years. But, that unenjoyable feeling of being confused? It didn't last long when I reached a point in those articles when things began making sense. If I had given up and decided to come back when I had more experience, I'd have robbed myself of the opportunity to understand. It took more effort to continue reading something I legitimately didn't get, but the payoff was far greater.

This has been an incredibly rambly way of explaining why it's a bad idea to give up. If something seems out of reach, there are times that you give yourself an excuse to not work as hard. It is tough to keep the motivation going. But to throw the towel in because something is too hard or you don't get it is the wrong approach -- instead, figure out why it's too hard or why you don't understand, and go from there. And if that is way too much work, then start asking yourself if you've chosen the right thing to take up your time.

Some of the HTML/CSS references I found are listed below, for anyone interested. I wish all a wonderful night or day, whichever the case may be.

---

• SimpleBits.com Archive (aforementioned Blog)
• A List Apart
• ImpressiveWebs
• Smashing Magazine