Automation Abstraction


For all things web development you have to be able to test them and confirm that they work. With the progression of AJAX and DOM altering JavaScript testing these web applications has become more and more of a chore. Unit tests and frameworks provide a certain level of quality assurance from the back but the user’s experience needs to be confirmed as well. The last four years of work at Broadcom has afforded me a number of opportunities to diversify and expand my skills palette, but no matter what I do I always find myself back in the role of a tester, unfortunately.

Continue reading “Automation Abstraction”

Progress Being Had

Adobe AIR™ loading... I occasionally get the opportunity to revisit code and rewrite applications i’ve written previously. Without fail i can always tell which of the applications was being used by me directly and how often i was running it, if not by the quality of the code… by the progress monitor i implemented. There are usually three monitors, and i can see each of them standing as a checkpoint to the next.

  1. DONE!
  2. Iterate through with some character dropped on the screen
  3. A Percentage completed bar that updates

Each one has its benefits and usefulness, so i figured id take a moment to step through each of them and where i use it, as well as how i coded it for the latter two.

Continue reading “Progress Being Had”

Ruby, oh yea, its on Rails

I nearly forgot yesterday that Ruby has a train following it about. It has been growing in popularity over the last few years as it has become more and more well known as the language used behind a growing number of applications, such as campfire for instance. I have no complaints about it though, its actually a very useful language. My problem, as is often the case, falls on ignorance and the terrible practices of fearing languages.

When someone approaches me and asks me if I know Ruby on Rails I have to answer, quite politely the first time, no. I don’t know Ruby on Rails any more than I do QCodo, PHPCake or any other of the dozens of web frameworks. The attachment of “on Rails” to Ruby has really ruined, at least in my mind, the possible momentum that could be enjoyed by Ruby as has been enjoyed by other languages like, Perl or Python. The fact that these later languages names begin with the letter P should not lead anyone to believe that they are P-opular. All of the languages that I have experience with have their place in my heart and a place in my development practices. From my point of view, pinning “on Rails” onto Ruby weakens the message that many of us have already taken to learning.

Continue reading “Ruby, oh yea, its on Rails”