8th Week

We made our third real demo, the component that was missing, was accepted. Now we started a new story, the next ones coming are migration of data. So this is was interesting,we were able to migrate some ofthe fields of the tables asked and we lready are clear about how to migrate the rest, well except the images.

I made a ruby parser that takes the csv files from the original db and coverts them into csv files that can be use on the new database. I learned what is a rake task, and how to do one, that is the way in which we are migrating the data.

Also this week, all the bugs that were found on the story that we worked previously into the other project were fixed, the good thing was that the bugs were about styles. It was a good week, also our trip to work on the client side is getting closer.

Seventh week

This week I just worked on a project, because we need to gain the confidence of the client, and make her fell sure that we know what we are doing,so for this week my teammate and I worked on two php components, that validates the downloads of products gave as a gift  with a promotion code, and also the other one was about a component that shows digital products bought by a customer and that still can be downloaded,one of those was accepted by the client. Also in this week my teammate and I learned that we need to stablish better acceptance criteria with the client, we need to be very careful on that.

Sixth Week

This week was about research and test spree extensions for static content management. Also I was able to start practicing more rails, making news added with the static content extension visible and dynamic linked into each album page.That was a challenge because my knowledge of rails in this moment is not as good as I want it to be. I take a walk through the checkout process of spree to make sure that we can answer to the client any question about it,  and I started programming one of the components of the project into php, so I'm learning also more php.

As part of this week I wrote the form required by the college and well, I also suffer a big headache testing on IE, that story on one of the projects was really stressing trying to make it look and work well on IE versions.

Template Method Pattern

From the Ruby patterns book that I'm reading, I'm doing a kind of summary of each pattern read. This is the first one. What  do we need to do to apply this pattern, well this is what this post is going to tell.

Steps: 

- Find out the basic flow of the process that we think that we can apply this pattern.

 -Define an abstract base class with a master method that performs the basic steps already listed, but that leaves the details of each step to a subclass.

So the base class defines abstract methods and on the subclasses we define the methods that are going to perform the real actions.

This is GoF pattern. 

Also something that clearly explains what is this pattern is:

"The general idea of the Template Method pattern is to build an abstract base class with a skeletal method. This skeletal method (also called  a template method) drives the bit of the processing that needs to vary, but it does so by making calls to abstract methods, which are then supplied by the concrete subclasses. We pick the variations that we want by selecting one of those concrete subclasses.

Non abstract methods that can be overridden in the concrete classes of the Template Method pattern are called hook methods. Hook methods permit the concrete classes to choose

1- to override the base implementation and do something different or

2- to simply accept the default implementation."

Bibliography:

Olsen, R. (s.f.). Dessign Patterns in Ruby.

Fifth week: Just 2 days

This week I just worked 2 days. The first one during the morning I worked with spree, installing an additional extension that my boss said. I got it working and also fixed the bug that we got when using another extension. Right now I’m really positive about this project, I think that we now have  a better understanding of spree to make a great demo to show to the client. During the afternoon, I worked on the story of the other project, kind of frustrating, make a site look and work properly on every browser is stressing. The second day I keep working on fixing design issues on IE and Mozilla Firefox. The goal for this week was to finish that story, unfortunately we miss a little bug, and some little issues of the images that are displayed with flash messages. So I don’t feel really happy about it, sometimes the learning curve of rails makes me get stuck.

On the other hand, for the apprenticeship program I keep reading the ruby patterns book, and I’m gonna continue with a tutorial of ruby on rails.