kamcoding

Month: July, 2014

Day 23

It’s extremely hot outside, but it doesn’t matter, we are really happy. You can congratulate us, yesterday we made our first pull request! Our mentors merged the changes into the integration branch. We’ve just started a new task – it’s creating a publicly accessible page, where various visualisations and reports will be available. That’s why at the moment we’re trying to get familiar with JavaScript. For now it’s less strange than we expected, but stay tuned… Who knows what will happen?

You probably are curious, what do we use to learn.

1. This.
2. That.
3. And sometimes that as well (beware, it’s in Polish).

Have a nice day!

Advertisements

Day 19

Long time no see!

What’s new:

– we got into another task – we have to add ahoy tracking to Species + API requests. This time it’s just pure experimenting, trying one method and then trying another. Everything works and after a while it doesn’t. But now it’s definitely not so frustrating – exactly the opposite, this is precisely how we imagined developer’s work.

– next week will be full of meetings. On Monday we probably will have a hangout with Team Participate and Team Code_Padawans. Can’t wait to see/hear them! Later on the same day we are going to attend Warsaw Women in Technology meeting. We’d like to say a few words about RGSoC. In the middle of the week we also plan to participate in huuuge summary conference call – with our supervisor Laura, our mentors Agnieszka & Simao and of course with our coaches. We are going to summarize our first month in the project.

Coming back to coding. Have a great weekend!

Day 14

It’s like neverending story – when everything seems to go fine, some kind of gem jumps out at us and screams: GOTCHAAAAA!

OK, let’s get to the point. As you probably remember, our task was to create a webpage in Species+ admin panel to view raw data collected by ahoy_matey. We were sure it’s relatively simple.

Our application uses CanCan gem. It’s an authorization library for Ruby on Rails which restricts what resources a given user is allowed to access. But CanCan actually surprised us. It did authorization using model, which name it tried to take from the name of the controller. But there was a difference between controller’s name and model’s name 😦 We had to communicate to CanCan very strictly about how our ahoy’s model is called.

Let’s be honest – without our coaches’ help finishing the task would be completely impossible. Thank you Tomasz & Piotr! You’re great!

So, at the moment we have our dream pages with raw data and figuring out how to make postgreSQL results table fully visible.

Have a nice weekend 🙂

Day 12

Coding, _real_ coding, at last! Since yesterday we work on creating new page (or pages – we still don’t know that) in Species+ admin panel to view raw data collected by ahoy_matey. Our page doesn’t need to be perfectly esthetic, but it has to show postgreSQL table and contain pagination. We discuss and try different solutions and at least one time it came out that collective work really rulezzzz. Karolina did something her way, Magda – a little bit differently. After merging the results we received *something*… and it seemed to work 🙂 Of course our page is still far from being excellent, but please be patient 😉

What else…? We still try to become familiar with Git. Without great success. Perhaps we just need more time. In the meantime we discovered another git online training 🙂

Day 10

Last Friday our gems finally started to collect all the necessary data.
But when we were comparing, what kind of information they generate, ahoy_matey came out to be better than impressionist. Surprisingly, it gives us more useful data, including user’s browser, operation system, device etc – while impressionist gives only ip 😦

So, we start new week of RGSoC in quite good moods. So far we learnt a lot about gems and their compatibility problems, but also about git. By the way, have you already seen that training?

Day 8

As we said yesterday, we decided to use impressonist gem. OK, it’s easy to say. We uninstalled ahoy (which left a huge amount of rubbish in the application source code), then installed impressionist… and, as usual recently, stacked on minor problems. Problem 1: WHERE exactly should we add gem’s code – which controller and model is the right one? Problem 2: when we restored the last app version without ahoy from our local repo, impressionist’s installation came out to be impossible. In the meantime our mentor Agnieszka finally managed to get the ahoy integration to a workable state.

At the moment we work on two separate versions – Magda with impressions, Karolina with ahoy.

We don’t know, what will be next.

We feel like Sherlock Holmes (not to be mistaken with Charlock_Holmes), chasing after strange errors and unexpected cases.

Wish us luck.

Day 7

So, it’s time to summarize our first week of RGSoC. We work on getting certain bunch of information about how do Species+ users behave. After a few days we already know one important thing: ahoy_matey gem (which seemed to be perfect) works properly with rails 4.1.1. and PostgreSQL 9.3, but not with the previous ones. While other teams started real coding, we spent the whole week struggling with one gem! It was a little bit frustrating, but we didn’t give up. And now we have to admit quite honestly – we learnt a lot. It brings us some comfort.

Today in the morning we had skype conversation with our mentor Agnieszka. After that we decided to try out another gem – impressionist. Stay tuned!

Day 5

Hello there!

We are spending another day with ahoy_matey.
Our project requeries form us understanding of relational databases. That’s why we are studying PostgreSQL and SQL issues.

For those who want to learn:
PostgreSQL

PostgreSQL Exercises
Postgres Guide
Everything about PostgreSQL
Books online about PostgreSQL
PostgreSQL course on TutsPlus

SQL

SQL on W3Schools
SQL on TutsPlus

And GitHub tutorial ❤

Day 4

Today is a day we called ‘frustrating Friday’.
We have some problems with ahoy_matey compatibility. And we still don’t know is it incompatibility with our version of PostreSQL, Ruby or Rails… We have no idea, where the problem actually is, and for all of a day we are trying to solve it.
In the meantime we read about differences between engines and gems.

With special greetings for ahoy_matey:
Sad_Panda_Chibi_by_mongrelssister

Source of the image.

Day 2

After the second day of RGSoC, we know that this gem ahoy doesn’t work properly in Rails 3.2.

Rails 3.2 do not support uuid and json. Our coach, Piotr, found postgres_ext, which  adds uuid to Rails 3.2, but doesn’t support json. We had to modificate migrations and use SQL.

It took almost c.a. 5 hours of our work… but the first pancake is always spoiled… 🙂