Weeks 13 & 14

160530 – 160613 — Total classroom hours 20(ish)

Yep, I fell behind again. Whats a guy to do? I’ve been making some killer progress (regardless of the low hour count for the two weeks). By the end of week 13 I had completed the Bloccitoff project, as well as the extra user stories that my mentor assigned to it because of my quick progress. At the moment it’s not much to look at, but it functions, and once I get some more front end developing under my belt I’m sure I can class it up in no time.

I completed most of my work over the weekend and after my mentor approved the checkpoint was pleasantly surprised to see the my ‘work completed’ progress bar on my Bloc homepage had moved tremendously! Basically, since the parameters of the curriculum are that I complete two projects, after the first project is completed I am two thirds of the way through the course (with the foundation coursework being the first third). For me, being able to get through the first project that efficiently confirms that I actually have a solid understanding of what I’m doing.

With this project taking me under two weeks, I cant imagine the next one taking me any more than a month. There are things I can improve upon, which will slow me down a bit, but I am pretty confident that even with that I will be done in 4 weeks or less. I didn’t test as much as I should have with the Bloccitoff project. I was so eager complete the user stories and move past the big problems that the testing fell by the wayside. I am going to be adamant about testing for this next project. Bloccitoff was proof to myself that I have a pretty solid grasp on the concepts, so now it’s time to start the good habits.  

With my timing as it is I now have to get serious about a personal project. I knew going into the course that it would be ideal for me to have a personal project, and now it looks like I’ll have the time to potentially complete one with the guidance of my mentor. Again, I’ve been thinking about this since I started, but have had a hard time coming up with something that is a) unique and b) potentially useful to the general public. After this weekend I’ve got and idea that fits both of those criteria and has a pretty simple user interface, which is also something I felt was important. Its also going to deal with automatically geolocating the user and measuring long/lat distances. Im pretty excited to get working on it, and I miiiiiight start it before Im finished with the next school project.

Last week most all my time was dedicated to the IPAs and APIs Hackathon put on by Avery Brewing and Mondo Robot. This was my first hackathon, and I was initially tentative about joining because I didn’t feel my programming experience was comprehensive enough. Luckily the lead coordinator of the hackathon convinced me to join and I had a great time. I entered as an individual, so I was assigned to a team. The team consisted of me, a UX designer, and a Java programmer. Basically, the Java programmer was the only one who had enough coding experience to get anything done, and since I don’t know a lick of Java, I wasn’t much help in that department. Luckily the UX designer had solid mock-up tools so we were at least able to show what we wanted the front end of the program to look like. Gaining experience working as part of a group was my main goal entering this competition, and I was very happy with how the three of us worked as a team. Our energy was always high and we communicated very well. At the end of the hackathon we were all proud of what we had accomplished. I would highly recommend everyone participating in a hackathon, regardless of where they are in their programming experience.

Week 12

160523 – 160529 — Total classroom hours 14.5

What a week! I went full steam ahead into my first project, Bloccitoff (which I have changed to ToBoom for fun). Roughly 15 hours into it I have completed 5 of the 9 checkpoints! Now, there are a few caveats to this, like the first checkpoint basically introducing the project and I’m sure the stories will get more complicated as I go, but so far I am very happy with my progress. 

Right out of the gate this project introduces a new gem, Devise. It seems to be an industry standard for sign in credentials, so I’m happy to be working with it, but at the same time it’s throwing a lot of curve balls at me. Initially I would really struggle when obvious tests were failing or actions were not completing as they should, but as Ive gone along I’ve come to realize when that’s happening it probably something to do with Devise, and after a bit of reading (and Googling, and Slacking) I tend to find the problem. All in all its great to have one gem take care of so many things, and I’m sure that the more I use it the more comfortable I will be with it and its intricacies.

Picked up a few nuggets this week, with the first being the Mailcatcher gem. I read so many ‘how to get Devise up and running’ online tutorials that I can remember exactly where I picked it up from, but it’s great. One feature of Devise is its email confirmation function, and where mailcatcher comes in is that you can set the parameters of the Devise to send to a particular SMTP, start the mailcatcher server via the terminal, and then point a browser window to http://localhost:1080 and watch the confirmation emails come pouring in.

I also was told of some great testing strategies this week while Slacking out a few problems. The first came about when I was testing what should have been a simple user verification test, but it just wasn’t working. I could see in the error that it was looking for a certain parameter, but no matter where I included it, the test wasn’t picking it up. I ended up running this command:

bundle exec rake db:test:prepare

which reset the db and, like a magic wand, the test passed on the next attempt. I ran into another issue just last night where I was getting a simple failure, but had no idea what part of the test was failing. This seems to happen often enough that I needed to find a solution, so I started digging, and posted the question on a few Slack channels. A fellow Bloc classmate introduced me to the command:

tail -f log/test.log

this gives a detailed output of what is happening at the db level and ultimately what is causing the failure. What I struggled with for hours before I was able to more accurately troubleshoot and we found the solution in a matter of minutes.

AND! The last nugget I came away with this past week was confirming that at some point getting up and stepping away from the problem can be an excellent strategy.  I have a hard time doing this, as I always feel that I’m so close, a mere syntax correction away from the ever elusive ‘Aha moment.’ But earlier in the week, after digging myself into a pretty deep hole, I decided that I needed to step away and get some fresh air. After about an hour I returned with a fresh attitude and -kid you not, the first new Google search I performed showed what I thought could be the answer. Thinking it too good to be true I plugged it into the code, and BAM It worked! I just shook my head in amazement and continued plugging along.

It’s been a good great week. It’s a great feeling to see a problem and at the very least know what pieces need to come together to solve it. I’m not saying I did it all from memory, but I definitely gave it a solid effort, then would fall back on my previous project or the coursework to fill in the gaps. Very excited to continue pushing forward with this project.


Weeks 10 & 11

160509 – 160522 — Total classroom hours 23.5

Still a little behind on the posts… Week 10 was pretty standard, no excuse for not getting a post up. I thought that I would have finished the foundations section by the end of week 10, but I saw pretty early on into the weekend (when I get 70% of my work done) that I was going to have a checkpoint or two left. I got hung up on something, which at this point I cant remember what it was, and I figured that it would be most efficient to hold off until my mentor meeting on Monday to resolve it. Once I got that dealt with I only had two more serious checkpoints left, both dealing with API’s, so I just accepted I’d have a light week this week. I’m still ahead of pace (that status bar is a blessing and a curse, haha!) and had some non-school code things I wanted to work on.

It turns out that the very last checkpoint in the foundation block is basically something that should be done with my mentor. Luckily my mentor and I spoke about which project would be best to start with during my last meeting, so I started digging into that. He suggested I work on Bloccitoff, which is a self-destructing to-do app. My gut reaction to the thought of doing another to-do app was not great, but I trust his judgement, and I know I can make this one better than others that I have already done.

Although I was able to setup the base structure of the app on my own, it appears that Bloc wants our mentor meetings from now on to consist mostly of pair programming via screenshare. I don’t want to get too deep into this first project before I discuss it with my mentor first. I have been reading some things about pair programming and am intrigued at the concept. I’ve also talked to some people about it, with mixed but passionate, opinions. The 30 minute meetings go by so fast as it is, I’m curious as to how much we will really be able to accomplish pair programming, but I’m game to try.

Along with setting up the base structure of my app I also started incorporating Waffle.io, an open source project management software. It’s probably not necessary to utilize a project management software when working primarily by myself, but the more familiar I am with it when I start the job hunt the better off I will be. Waffle takes a second to get used to, but with minimal setup, understanding how it incorporates with Github, and how formatting git branches can streamline the process, its pretty slick.

Oh! Hey! I’m done with foundations! Thats probably supposed to be a pretty big deal, technically it probably deserves a blog post all of its own. But I’m not big on celebrating, and I still have quite a bit of work ahead of me. I will say this, I have been very happy with the program so far. It hasnt been perfect, but any time I felt something was not quite as great as it could be, I always reached out to Bloc in one way or another and they welcomed the feedback. The coursework seems to have the right amount of depth, I can converse among my peers when Im at meetups other events. They still make you dig for certain things, which I appreciate and definitely feel has made me a better programmer. So, yeah, pretty happy so far. Oh, and I signed up for a hackathon APIs and IPAs for June. I was a little hesitant considering my small knowledge base, but the event organizer I was speaking with seemed pretty confident that I would benefit a lot from it, so I figured why not?

Weeks 08 & 09

160425 – 160508 — Total classroom hours: 29

Oh what a few weeks it’s been! My mentor took a vacation, which meant that my program was frozen for a week. I could have just taken the week off, I think I could have easily made the argument that I had ‘earned’ a week of just doing nothing and catching up on Netflix. But, I don’t sit around well, and the finish line for the foundation section is within sight, so instead of chilling for a week I decided to keep up the momentum and crank through some checkpoints.

There seems to be a rhythm starting. With just about every new checkpoint there needs to be either an entirely new table or a column added to an existing table. New models, new controllers, partials, polymorphic relations, it’s been pretty wild. I’m starting to feel confident in performing these repeating actions on my own. I’ll see what the coursework is heading towards and I’m able to work a few steps from memory, then confirm my actions by scrolling down the coursework webpage. Whereas at the beginning of the Rails work it felt like I was typing voodoo magic, now the connections make sense to me, I understand the logic behind the coursework code and the assignments are becoming a bit less stressful. I’ve heard many times that programming is about muscle memory and repetition. Its tough to trust that, especially at the beginning when everything is so new, but it seems to be working out that way.

If you’ve been reading the blog you know that I have a husband and wife power-programming team (Corey and Emily Davis) is  in my corner and they are eager to talk about my progress every time we get together. We’ve met up a few times over the past two weeks and it is so incredibly helpful to be able to talk to them about what I’m doing. They’ve given me some great input when I’m stuck on something small, but even when I’m not stuck on anything, to be able to just have a programming conversation is invaluable. It’s a bit of a confidence boost to be at a point where I can simply talk shop with other people. This also leads to discussions about different approaches to problems and challenges. Every school has a slightly different approach to teach programming, and having the input from other industry professionals -including my mentor- is making me a bether programmer than if I just had my blinders on and was cranking though the classwork.

The end of the the foundation block of checkpoints is in sight. I only have 5 checkpoints left, which in theory means that I could be finished by the end of the weekend. I’m definitely going to give it my best effort, but I’d be pleasantly surprised if I actually get it all done. I’m excited to get into the projects, this Reddit clone project had been a great learning experience, and Im sure I’ll be referencing it quite a bit during the projects. I haven’t really dug into any of them to see what I want to do first. I’m trying to keep my eye on the prize and keep my focus on this foundation block. I’d like to get some experience with APIs, as I’m interested in being able to take advantage of user-ready data. My mentor mentioned a path that he felt utilized Bloc’s project curriculum in the best way, so I’m also curious to hear his input on it.
All in all things are going very well and I’m eager to see what the projects will be like.

Week 07

160418 – 160424 — Total classroom hours: 15

This last week was as close as I’ve come to just smashing my forehead against the keyboard and calling the week good. That sounds a little dramatic, and it is, but the bright side is that I’m seven weeks into the program and its the first time I’ve been this frustrated, so I take that as a good sign. What caused this frustration? RSpec, seeds.rb, and before_action filters. Each were their own beast, and because I was trying to push past (around) the errors to continue making progress on the coursework, it was all a bit of a mess by the time I had my mentor meeting.

The RSpec and seed.rb errors were tied to each other. I could see from the test failure readouts that the tests were failing because of a validation error. I tried to just bypass the error by commenting out the failing test, but the next step in the coursework was to re-seed the database and that action was failing for a similar reason. It appeared this would have to be addressed. I assumed that there was a typo somewhere so I started working backward through the coursework. After digging back 6-7 checkpoints and not finding the error it dawned on me that it would probably be more efficient to work back through my git commits until the I could run a db:seed command and not have an error thrown. That was a much better use of my time, the kicker being that by the time I had found the general timeframe of the error I had to pick up shop and leave for work.

Once I got done with work (and thinking about this error for most of the day) I still had a tough time identifying what I had done incorrectly. At this point -for the sake of finding the error- I had commented out my own work and copy/pasted most of the coursework into my text editor. And still the error persisted. It was at this point that I decided to reach out to my mentor. We went back and forth with several messages. Me trying to accurately describe the error and the steps I had taken to resolve it, him trying his best to diagnose a problem of which he only has my error diagnostics to go on. We went back and forth for a few messages, and we came to realize that in my attempt at error diagnostics and commenting out lines I was commenting myself in circles and had actually ‘solved’ the problem very early on in the process. I guess the lesson is that at some point its probably not a bad idea to stop, keep any obvious errors that may have been found (typos, syntax, etc), un-comment everything and start those tests from scratch. That technique would saved me a lot of time. Now I know.

The other big hiccup for this last week were the before_action filters used to identify the role of particular users signed into the app. All I’m going to say is that these filters are kind of a beast. Most of the ‘unofficial’ documentation that Google concerned itself more with the strong opinions of people who have used it than the actual techniques to use it effectively. I get the sense that people are either all about these particular filters, or absolutely despise them. Being that Im pretty green I don’t have a strong opinion either way, but let’s just say I hope to not see another one anytime soon.

That’s a pretty thorough synopsis of last week. It was definitely an exercise in patience and error diagnostics. I was happy with how farI was able to get on my own in regards to error solving, so I feel like that’s solid progress. Here’s to a new week and fresh start!

Week 05

160404 – 160410 — Total classroom hours: 17.75

Rails. Hours and hours and of rails. I don’t know why, but for some reason I thought that there would be a ‘break’ from the rails portion of the Bloccit project and I would have time to review it. That’s definitely not the case, I mean it’s all Rails until the end of the foundations block. But, what Bloc is doing with its curriculum is pretty helpful in that the rhythm is to work on a new section of Rails, then as the assignment you repeat those steps you had just worked on to implement another feature. I appreciate the teaching strategy, it allows me to do as much as I can from memory, and then when I get stuck I can review the checkpoint material. During the checkpoint material there are definitely moments where it feels like I’m not doing much more than transcribing into my text editor (I use Sublime with a bunch of add-ons that my good friend Corey helped me set up) what is in the Bloc browser. But, I’ve found that even doing something as simple as changing the letter used as the variable forces me to be conscious of what I’m typing and what the code is doing.

One thing I have had a little trouble with this week is the Codewar-based ‘Programming Reinforcement Checkpoint’. I spend 4 hours on only one challenge on Saturday and I still have some work to do on it before it’s even close to being done. After that I still have the other two challenges to complete. I don’t have a problem challenging myself, and I know that even the process of finding the resolution is making me a better programmer, but at some point there is a concern about how much time I am spending on each problem. I mean, 4 hours, that’s nearly one quarter of the entire time I have for the week, spent on one third of one checkpoint. Thats a lot of fractions in one sentence, but basically I feel like it’s taking me too much of my time.

Because the actual coursework is focussing on Rails, these three (Level 6) katas are the first time I’ve worked with Ruby since the last (level 7) katas a few weeks ago. I guess I have a hard time understanding the thought process as to how solving three katas at level 7 qualifies me for anything at level 6? Whatever reasoning Bloc has, its not working for me. The way I see it, there are several ways to approach a problem like this. I could just punt through the level 6 katas, probably having to run every step of the process by my mentor. I could just complain about it, how it’s not fair, too hard of a challenge, etcetera. Or, I could grab the problem by the horns and figure out how to resolve it. I’ll be doing the later. I plan on taking the next few weeks and working on more level 8 & 7 katas, on my own time, outside of class, until I have worked up the knowledge of Ruby to more efficiently solve the level 6 katas that Bloc has assigned.

No educational structure works perfectly for every student. I feel that curriculum is an outline of what needs to happen in order to accomplish a larger goal. Its up to the student to make that curriculum work within their own style of learning. So far I am very happy with what Bloc has had me do, and I will happily work a few extra hours a week on my own to fill some gaps. At the end of the day the goal is to get a job as a programmer, any and all experience I can obtain along the way will only help me achieve that goal.

Week 04

160328 – 160403 — Total classroom hours: 18.25

I was excited to start this week’s work with rails. I feel like I have a relatively good handle on Ruby (emphasis on ‘relatively’) and Im curious to see what this infamous Rails beast is all about. It started out, as most lessons into new territory do, with a few checkpoints of setup. What I find most interesting in this new endeavor is how even the most simple tasks can throw me for a loop. One aspect of the workspace was to set up an account and push the project to Heroku. It probably took me an hour to get a successful push to Heroku. When it was all said and done, and after abandoning the initial setup to start from scratch, I realized that I had not properly setup the git process (I added only the single README.md file, instead of add all) and that was preventing it from pushing properly to Heroku. So much of this whole programming ecosystem is about precision. Miss a comma, add an accidental spacebar stroke, give the monitor a weird look, and you’ll get an error. But what I love about it is that in almost all errors lies the solution to the error, you just have to know where to look.

Ok, so now everything is pushing to Github and Heroku properly, time to get rolling. Theres a lot of infrastructure to setup: controllers, routing, models, proper paths. To be completely honest, Im not confident that its all sinking in as much as Id like. There were definitely some points where I was typing what I saw in the browser into iTerm and crossing my fingers when it came to testing. About half the time the tests would fail when they were supposed to pass. But, as Ive come to learn, a failed test is a learning experience. When a test fails it forces me to ‘wake up’ from the copy/paste trance that I was in and find/resolve the problem. As Im digging through the last 5 minutes worth of code Im revisiting the exercise -usually multiple times- and its sinking in that much deeper.

I had some trouble with models (which are new to me) and git (which is not) this week, which was probably the biggest hurdle I overcame. The assignment for Checkpoint 28 was to take what I had learned in the lesson and create two new models that would reference each other. Sounds simple enough, after all, I had literally just spent the last hour and a half doing exactly that. I had some trouble, I tried to edit an existing table, I tried to remove a table, I tried to go back in git and start from scratch, but every attempt was failing. I was not surprised to be struggling with the models, but I really thought I had a handle on git and it was not responding the way I thought it would. The problem with the models was merely a matter of knowing how they can be manipulated, particularly the order of events that has to occur for edits to take place. And what I learned about git was that if you leave the changes you have made in the current branch uncommitted they will follow you around no matter how far back you go in the git history. Both resolutions came from my mentor

Don’t let the previous text fool you. As many problems as I have solved this last week I feel like my handle on Rails up to this point is weak at best. Once I complete the Rails checkpoints I plan on going back and reviewing the entire section again.

Week 03

160314 – 160320 — Total classroom hours: 14.75

This week the focus was on finishing the terminal-based address book app, address-bloc. Relatively speaking, it was a simple app, but it was a great example of the relationships between the specs, models and controllers. Having to make those elements and connect them to one another by hand (something Rails does automatically) helped drive home how each component worked contributed to the larger whole. This week’s checkpoints also dealt a lot with git and github, as every checkpoint and assignment needed its own respective branch. Its building good habits and muscle memory, constantly committing changes, pushing them up to github, and merging branches to master.

As much as the focus was on address-bloc, I spent nearly half the classroom hours on the Programming Reinforcement checkpoint, almost seven hours this last Saturday. Its pretty wild to think that it takes nearly seven hours to complete three challenges. When merely breaking down the numbers it’s a little crazy, but the time goes so fast when I’m actually working on the problems. Once again, the Programming Reinforcements are selected katas from the website Codewars, I see a pattern here and don’t expect that to chance any time soon. I appreciate the challenge, the first was titled Tube Strike with a math concentration and then a pretty standard if/then statement. The other two were Character Counter and Most Frequent Item Array, which definitely had me spending a lot of time on Google. After the Tube Strike kata, I believe I solved the frequency challenge first and was then able to apply a lot of that code to the character counting challenge. If anyone is interested, here are my solutions:

Character Counter: http://goo.gl/tLlsvP

Most Frequent Item Array: http://goo.gl/PCiphT

Tube Strike: http://goo.gl/f5JyBC

Since starting the program Bloc has changed the purpose of the Programming Challenges from purely extra credit to -what I gathered from the notification- mandatory, if I want to take advantage of their career placement assistance at the end of the program. Initially the change made me a bit nervous, but what it’s done is forced me to take the challenges seriously and push through any thought of giving up and moving on. Even as it is, it’s a little tough to spend hours on random challenges when theres curriculum to still be attempted as far down as the page will scroll. But I know that working through the Codewars challenges is actually more like the actual working scenario of a programmer than the classwork, so that keeps my drive up and the Google searches flowing.

Week 02

160314 – 160320 — Total classroom hours: 18.25

The first thing I did last week was physically write down my goals for the upcoming week. And when I say physically I mean clipboard, paper, and a sharpie. It wasn’t elaborate, only two items:

  • Complete Bloc up to Checkpoint 16
  • Upload blog post by Sunday PM

By Wednesday the list had been updated to:

  • Complete Bloc up to Checkpoint 16 17 20
  • Upload blog post by Sunday PM

The clipboard is on my desk, leaned against the wall, just above and to the left my eyeline to my laptop. Its always there, keeping me in check. I can’t remember the last time I’ve made and actual checklist for something, but I think it’s important for this program. I’m steadily keeping ahead of the course-designated timeline, so its good to have some kind of set parameters, otherwise it could seem like I’m just wandering around a dark cave of hashes and arrays with no flashlight.

I updated the goals as I progressed through the week because I realized that a majority of them were dealing with setting up a workspace, which I already had, so I knew I would cruise through them pretty quickly. At this point (Sunday AM) I’m just beginning Checkpoint 20, but I confident I will be able to complete it before end of day.

There were some solid programming challenges this week. I actually spent a fair amount of time on the ‘Extra Credit’ Checkpoint, which as of this week has been changed to Programming Reinforcement Checkpoint. In these checkpoints Bloc utilizes the website Codewars to reassess programming principles they covered in the previous checkpoints. They were relatively simple challenges, in that the ‘answers’ weren’t much more than 3-4 lines, but they kicked my ass a bit.

After spending 2 unsuccessful hours on one particular challenge I enlisted the help of the husband and wife super programmer team Corey and Emily Davis. Together we found a working solution and then I worked backwards to see where my attempts had failed. At some point -especially early on in the learning process- I feel that it is more efficient to be given the answer and then work through it to see where my attempts went wrong. Both Corey and Emily are great teachers who thoroughly explain every step of their thought process while helping me find the solution, they are an incredible resource to have.

I am starting to dive into the first project-based checkpoints where we build an address book. The foundation lessons are really coming into play, and writing the tests before the code to make the tests pass (TDD) forces me to fully consider what I want each block of code to do. I have done similar projects with another ruby education program, but it was a lot of just trying to mimic what they were doing into my own text editor and get the tests to pass. What I was actually having the code do was not sinking in. Both the pace of the Bloc curriculum, and having done something similar before, are big factors as to why I feel more confident in the application that I am building now.

I haven’t dug too hard into what will be happening next week, but by just looking at the roadmap it looks like I should be finishing up the address book app and complete another Programming Reinforcement Checkpoint. As the curriculum gets more difficult I doubt I’ll be able to keep my current pacing, but I’ve definitely given myself a solid start so I’m not too concerned about it.

Week 01

160307 – 160313 — Total classroom hours: 14

The first week of Bloc is under my belt and I’m feeling pretty good about it. My mentor is engaging, enthusiastic, and timely to both answer my questions/comments and approve my submitted assignments. The infrastructure of the learning platform seems well thought out. The main homepage is referred to as the ‘Roadmap’ where it is easy to see progress and what still needs to be accomplished to reach the goals for the week (which is determined by the pace chosen at the beginning of the program).

The curriculum is setup as such: text-based explanation of the subject, code assignments to confirm understanding of the subject, then video ‘answers’ to the code assignments. Within the explanation of the subjects, as well as the assignments, there are often links to help explain things in more detail. They also encourage Googling any questions you might have during the process. To some this may seem like laziness on the part of Bloc, but every programmer I’ve ever spoken to has told me that Google is always the second tab open on their browser and that knowing how to search for answers is just as important a skill as knowing proper syntax.

I was able to surpass my weekly goal of 5 checkpoints, primarily because I have been doing a lot of prep work before starting the program with Bloc. The first 5 checkpoints were things I have learned before, and I was able to cruise through them pretty quickly. Then things started picking up and I was finding it pleasantly challenging. I was submitting assignments nightly, and my mentor typically had them approved and commented upon before noon the next day.

My goal with this program is to push as hard as I can, and not take a break until there’s a good stopping point in the curriculum, which is what I accomplished this week. I made it through checkpoint 11 (Ruby: Advanced Classes) which seemed to me to be about as far as I wanted to go before discussing my process with my mentor. I’m not simply blazing through assignments, just to check them off the list. I work a problem until I feel that I fully understand it, and at this point I’ve compiled enough questions that I feel it would be best to take a break until I can run all of them by my mentor.

I feel great about my progress so far, and as long as the meeting on Monday evening goes well, I’ll have some good momentum going into Week02.