Updates

Day 33 – 35 + Weekend

Ah, I have been remiss in my blogging duties. Sad day.

Things have gotten a bit more busy around here. Namely, I finished about as much of the Rails course as I’m going to and I’m starting on my final project. Ben, a former student from two classes ago, is going to work with me on this venture.

We decided to do it all in Node.js and Express. We are going to work on creating a game that can be played by multiple people while they use their phone as a controller. To do this we need a lot of real time action and Node.js and Express are really good at that. Rails is really great for creating deep websites with lots of pages, content, and big databases.

So Friday and all day yesterday we worked at my house. One of my roommates is an Express and Node.js wizard so he helped us get off the ground. A lot of our time is simple researching and learning how to do things. Which makes progress slow but we figure (and hope) that once we overcome the learning curve things should pick up.

I’ve found out that I really prefer to work at home lately for a few reasons: there are less distractions (except in the evening), we have access to someone who is familiar with Express (nobody really at the Dojo does), and I have full access to use the house’s 46″ tv as a second monitor. Woo!

Ok, I’ll try and keep up with my posting duties now that things are getting busy.

Advertisements
Standard
Updates

Day 22, Tuesday

Progress, at last.

I’ve finally achieved functionality on my CodeIgniter assignment. The message board part is now up and working. I’ve put together all the UI/UX for the rest of the assignment, I just now need to connect it to the database. That might take awhile and there are a few different ways I could pull it off.

Therefore, I left it for tomorrow. Time to take a good break.

As I theorized, because of my bush-whacking / forge a new path through the forest mentality, I’ve started to have a good grasp of how CodeIgniter works. There are a lot of really awesome tools and tricks that make it very useful. I’m interested to begin playing with Ruby and Rails. They say that its a big difference.

Apparently, in Rails, you just have to trust that a particular function or tool works. You dont necessarily need to know how it works. This has its benefits and disadvantages. You can develop a lot of applications very quickly. But it doesnt lend itself to customization and you can have a lot of people who are really good at rails, but in truth, terrible programers. I believe that is a distinct advantage of attending Coding Dojo. They knowingly force you to learn the basics and “the hard way” of doing things so that you not only understand but also appreciate the more advanced tools.

I also admit that I am 100% absolutely comfortable with having to learn a new language for my job. I have a solid grasp of the foundations and after that its just a matter of syntax.

Standard