Skip to main content

Coding Resources


There's a resource page attached to my blog here. It's where I'm listing all of my tools I'm using to learn to develop code. There are many links on that page to a few different languages, but my focus is on Visual Basic at the moment, so some of those links are going to be stagnant for me.

Resources

As it stands right now, there are four resources in my arsenal that is teaching me how to write and understand the programming language Visual Basic.



1. Microsoft Visual Basic 2010 Comprehensive book


This book is one a friend had at work laying around in one of her bookcases that she had from a course she took in college a while back. She let me borrow it. I spoke to some others in the office about where to start, and they suggested the book. Many of the developers I work with don't actually have formal 4-year degrees, which surprised me. They simply got certified in some programming languages and began working. I've only made it to the third chapter, but many of the concepts are already becoming clear in how VB works. It does an excellent job of explaining how to use the software and some common coding practices. I asked about the age of the book and was told this would actually not be a hindrance at all. It's better to learn how stuff works from an older book, and then when you see the updates, you appreciate them and realize how it helps in the long run.



2. Codefights

In addition to reading the text mentioned above and doing the exercises there, I'm also participating in a website called codefights.com. It's actually really great. There's no real instruction for how to code, and its intended for people who already have a base in coding, I think. The website is forcing me to lookup answers and understand syntax and concepts in order to post solutions. The company I work for has even started a friendly challenge to see who can get the most points. Obviously, I won't stand a chance in that department, but I actually get to work on little assignments other developers are working on, and that's pretty cool. I also get to see how frustrating a wrong piece of code can make something not work and feel that rage. :) Still, it's great practice, especially for those who are already programmers.



3. Pet Project


My supervisor strongly urged this one, and to be honest, I haven't started it yet. The goal is to learn by doing something that I completely control: no schedule, no specific requirements, just a simple program. In my case, it is going to be a simple time sheet program that tracks time. In doing this, I should be able to learn more about a practical use of the code. Since I haven't started this part yet, there's not much to show. Still, I have heard several people and blogs mention that having a side or "pet" project is a great way to keep stretching yourself to learn.



4. Fellow Coders

Last, I work directly with several different developers every day. At any given time, I ask them general questions, and when they're working on something they have a little extra time with, they let me sit in with them to understand what they're doing and how it's affecting the programs I test everyday. My supervisor and other leaders are great resources as well. Even the IT director is stepping in and pointing me in the right directions. It's really great to be a part of this team. There's going to be some information I obtain from them that's not documented, and it may very well be extremely specific to my organization.





Process of Learning

In essence, no one is really giving me a direct step-by-step guide of exactly what to do, and I'm not attending any formal classes. This is largely self-directed. My supervisor and another leader at work has explicitly told me to use the book and create a side project. Everyone is standing behind that information, so that is what I'm going to focus on first. I was also told to keep messing with Codefights, so I'm going to be doing that some on the side as well. Ultimately, I'm in charge of my own schedule and learning, so self-discipline is somewhat crucial. I'll keep everyone posted on where I'm at.

Comments

Popular posts from this blog

Bigger Picture

I've learned a big part of development since I've been a part of this team. We have meetings. Some seem long-winded, some seem unnecessary at times, but I've gotten something from all of them in every case. There's a lot of communication involved in this role. I focused on a lot of technical, but there are many soft skills involved to make it successful. Below is a summary of some of the things I've learned in just a few quick months. 1. Know When You Don't Know There's nothing wrong with not knowing. There are developers on this team that I've heard everyday say, "I"m not sure how to do that, I need to ask 'so and so'." I feel I'm part of a great team, and maybe this type of honesty isn't the norm. In any case, it's refreshing to see that type of behavior. It's also encouraging to see someone who has been here for many years not afraid to admit when he/she doesn't know something. No one is going to kn...

New Pet Project

Okay, I've got my next great idea for my pet project. It's a little more complicated, but not terribly. My biggest complaint I had when I transferred from the Detailing Department to the Customer Service department was the loss of my trusty HP48G calculator. This thing was awesome! You calculated feet and inch calculations with formulas. The format was feet.inches and sixteenths. For instance, 14.0608 = 14'-6 1/2". The formulas removed parts of the inputted number and converted them from a foot to a number to add and subtract, and then reconverted the number to a foot answer to display. I and a colleague created several excel sheets that essentially did the same thing, but it just wasn't convenient and didn't flow very well. So, I'm going to create a program that looks close to this calculator. In addition to the addition, subtraction, multiplication, and division of feet-inch numbers, there were formulas that calculated roof slopes, weights, and...

Pet Project Progress

Well, I've started my pet project, and I've got a GUI laid out. It's a little slow going, but it should work well in the end, I think. I'm sure there's going to be lots of feedback and many different ways I could do things. Right now, however, I'm limited to what I am learning in the text. As promised, here's the screenshot of my first program. Help? I'm trying not to ask too many people how to write any of the code yet for a couple of reasons. First, I haven't learned any code yet, and I likely won't understand a word of what's being told to me. Second, I'm afraid that what I'll be told I'll understand at that moment, but since I didn't have to work  for it, it won't get burned into my memory like the knowledge I have to seek out. Those long hours searching usually scar you to the point you never want to forget those lessons again. Function Since I don't have too much to show, I'll just explain what th...