Learning Java...

I now know what they meant when they were saying that Ruby and Python are languages that are designed for the programmer vs. the computer, and how they make programming fun. Initially, I thought "how can programming not be fun?" However, after studying Objective-C and Java, I'm pretty clear on what they were talking about.

Java, from my understanding, so far, is a "lean" language, so you have to import "modules" that are already packed into Python and Ruby. In Java, you  have to write "import java.util.Scanner" to allow the user to input information, whereas you can just create a variable to accept the input in Ruby and Python. There are other little things like declaring types for variables and only being able to use one type of object in arrays, that make programming in Java...different.

The cool thing about declaring a type of variable, though, is that you decide what kind of variable you want to use ahead of time and you don't actually have to write your number in a decimal form, if they don't have numbers following the decimal. This is good for programming because you are thinking through the type of result that you want, which avoids using integers, when you want a float and having to go back and put in the decimals if you forget.

Another built in feature in Ruby and Python is the error messages. Although, you can resolve that situation by using an IDE, it comes built in to the other languages and coding in Java requires you to *sigh* download a IDE like NetBeans, free of charge and install it on your computer, when you're first getting set up.

Things that you can do using Java that you can't use Ruby and Python for? Compiling programs into .exe and other files that you can run as stand alone software (I think you may be able to do this on python, with some extra effort...Cython?) and building native mobile apps for android, which is huge. I think that with the popularity of mobile devices, not being able to use a language to build native applications for them is a pretty big disadvantage...if you like making stuff for other people to use. Even though there are plenty of things you can still build for people who are sitting in front of computers or for things that use Raspberry Pis or Arduinos. For me, the most exciting thing right now, as far as development is concerned, is making things that can be used no matter where they are on many different kinds of devices. I really hope that something can be done about this...and soon [ yes, I know about Ruby Motion :) ].

Challenges with learning2Java that aren't about the language itself:

1. The writers of the books. I'm not literary expert or anything, but the way that they write/speak is hard to follow. The way they say things is not fun, at all. I don't know if it's just me or what, but I had such a hard time reading the books that I decided to watch youtube videos first so that I could get a general understanding of what's going on. It's not like I don't like to read or I just picked books at random, either. I did an internet search to try to find the best books to learn with, but yeah...
2. Leaving this hanging: public static void main(String []args). Yeah, you really can't do that. It's not cool to tell me that you're going to explain something later, and then wait to talk about it at the end of the book. Sorry. I NEED to know. [ note to self: why haven't you googled this, yet? ]  How about walking me through it and then going into more detail later. I understand that "public" means that it will be available to other code, they explained that "main" means that this is the operating class that the compiler will look for, and from studying Objective-C, I think that "void" means that a function will not return anything, but I have no idea what that means for a class or if this is even the same thing in Java, and "static"? I need all of this explained and I need to be clear that I'm thinking in the right direction on this. That "String []args" part also needs to be explained, especially since I keep seeing those square brackets moved to different places in different code. How am I supposed to concentrate on what you're trying to teach me if this keeps coming up unexplained?

This probably sounds like a lot of complaining, but it's just my growing pains. I'm definitely going to take advantage of all opportunities to learn new things. [ ...especially Java, since it's the dominant mobile platform and I definitely want to develop for it...even though I have an iPhone ;) ]. I'm just getting started with Java and Objective-C, so if I start saying things, in the future, like "I don't see what people's problem with Java is" or "actually, Objective-C is pretty cool, I'm glad I learned it before I started Swift" don't be surprised. :)

I think that I'm going to go study a little Ruby now. 

...because Ruby.

Coding and Stuff...

Last week, I started getting a little bored with programming in just ruby, so I decided to go back to learning a few other languages. I watched the Google Class on Python and I picked up the Code School Objective-C tutorial, again. I find that studying other languages gets me a away from the syntax of the languages and more into the larger concepts involved in programming. In the beginning, I just thought that you should just learn one language and get really good at it, and then maybe pick up some others a little bit later down the line. What I have found is that once you think you have a decent grasp on the basics of one language, it's productive to pick up another language, with the same paradigm [i.e. object oriented, symbolic, functional...]. This is works for me, because it forces you to really understand the concepts involved, it breaks up the monotony of studying the same thing over and over, and, pretty much, without fail, every author brings a unique perspective which leads to new insights on programming in general. Recently, I've had a chance to start reviewing the code of other programmers who are just starting out and it's made me realize how important it is to learn to actually program versus just being able to code in a language.

Speaking of which, I heard back from the company that I wrote the Mars Rover program for and I am happy to report that I have done my telephone interview and will be visiting the main office next month for the final stage in the process. I think that I am a very strong candidate for this company and I am super excited about the prospect of working there. On Friday, I went to the Atlanta office and meet one of the developers there. He was super cool and made me feel really good about the job and my chances of actually getting it, so...that was positive. Among the things that I love about this company are lots of travel, flat management structure, the fact that you have a voice in the things that you work on, and the people working there are "my type of people."   I can't wait to go up there. My entire experience with this company has been awesome. I can't think of a better place to be for my first, possibly only, programming job.


Which brings me to: I just started learning Java. I have to learn Java for Algorithms I, as well as for this new position, should I get it. The algorithms class starts next week, but if I get this job, they will also teach Java in training. This will give me a leg up for the job and also allow me to develop mobile apps for android, which is something that I'm definitely interested in.

Java is an object oriented programming language, so it's not a big departure from what I already know. The syntax and the things that it requires, such as the requirements for declaring variables, are a little bit uncomfortable after starting [restarting] my programming education using ruby and python. I'm pretty sure that I'm always going to prefer ruby and python to any other languages, but I'm learning to appreciate Java and at the end of the day it's more about the applications and building cool stuff.

The Mars Rover Project

Last time I posted, I was talking about upgrading my professional marketing materials, i.e. LinkedIn, because one of my friends told me about an entry level programming position. Well, they contacted me the next day and the interview process has begun. My first tasks are to watch a video, fill out a questionnaire, and choose one of three programming problems to solve. There were three choices, the first was one involving a transit system, the second was one that calculates taxes and tariffs on goods and prints out a receipt, and the last one was to write a program where you hypothetically help NASA track rovers on Mars. I think we all know which one I picked. :)

The first one, I skipped, because writing a program about a train system didn't interest me enough to stop there and the second one wasn't that exciting to me, plus I have two other friends in the process who are both doing that one. The last one was right up my alley: writing a program to plot the position of Mars rovers.

I love astronomy. The extreme speeds and grad scale of the universe is one of the most fascinating things that I can imagine. I took several astronomy classes as an undergrad and since then, I have kept up to date on most of what's going on in the field. So naturally, I jumped at the opportunity to pretend like I had a job with JPL. I've already started working on it and I am thoroughly enjoying it. When I first looked at the problem, it seemed a little bit overwhelming, but it is way too interesting and fun to not do it. Once I started working on it and breaking it down into smaller pieces, it became manageable and much less menacing and it is starting to come together.

I hope that I never stop getting excited when I get my programs working.  I like puzzles and I do many different types of them, but I never find myself getting extremely pumped because I solved one. It's way more fun to code. Don't get me wrong, I do feel satisfaction in completing puzzles, but when I make programs work, I get extra excited. It's more like scoring in sports, than solving a puzzle.

... I guess you had to be there.

UPDATE: I've watched the video and turned in my program and questionnaire.

Pulling it all together...

I'm feeling good about where I am with my coding, I started a new book on Rails this week, called Pragmatic Agile Programming with Rails 4. I'm kind of wishing that I had done this before I repeated the Michael Hartl tutorial. This book is really enjoyable and I'm taking my time getting through it. I just finished chapter 6, today. The demo app that they started with in this book was different from the other tutorials and books that I have read, in that it was much simpler and clear.

I found out over the weekend that I can't dual boot Linux with my Windows 8. After being frustrated with the compatibility issues with Ruby Gems for Windows, I decided to do whatever it took to get Linux working. I spent the better part of Saturday morning and early afternoon working on this to no avail. I gave it a half-hearted attempt when I first got this computer,almost a year ago, but it didn't work out because, at that time, you had to disable the secure boot to get it operating and I didn't bother to do that. Apparently, this no longer an option. I really don't understand why Microsoft is doing this. Are they banking on all developers, that aren't currently using Apple or Linux, exclusively, to just switch over to using their development tools? I'm contemplating trying to switch my OS to Windows 7. At this point the only reason that I'm using Microsoft is because of Photoshop, Rosetta Stone, and the years of work that I have on my external hard drive that I carried over from the computer that had before this one.

A few months back a started taking a Stanford MOOC course on networking. I learned a lot about how networking works, in theory, but I started getting real world experience this week, when I had to change my password, because one of my neighbors has been leeching off my WiFi signal. I had been putting it off, because a.) it wasn't a serious issue, and b.) I didn't feel like resetting the passwords on every device in the house, but they finally forced my hand by hogging up all of the bandwidth, which led to additional googling and experimentation with my router.

I've also decided to start getting my professional stuff, like my LinkedIn and resume updated, so that I can seriously start looking for a job doing programming. I've been writing a real summary for my profile. Last night a friend of mine asked if I would be interested in interviewing for a position at ThoughtWorks, so that also forced the issue a little bit, although, I have been meaning to do this stuff for a while. The problem is that I enjoy programming so much, right now, that I just really want to keep learning it as a skill and I end up not devoting as much time as I should to the "career" side of coding. I'm starting to think that I may end up just doing freelance work.


PS- I didn't get that Code for America Fellowship. :(