Team Ruby's secret (Exception Notification) 
- Starts On
- July 01, 2016
- Finishes On
- September 30, 2016
- Last Activity
- September 30, 2016
September 30, 2016
Team Ruby's secret (Exception Notification)  — at September 30, 2016 19:59 UTC
We can't believe that the three months had passed so quickly , we still remember the small details of our very first day as if it were only yesterday .There will be something missing next weeks , our daily logs, our weekly calls with Linda <3 ..... but we're happy , I guess we made our first step in building our future .It was the strangest but definitely the best summer in my whole life .We only have one wish for RGSoC 2017 , we really hope to see more women getting into tech and more teams from Egypt applying to RGSoC to have an amazing summer as we did .
Team Ruby's secret (Exception Notification)  — at September 30, 2016 00:24 UTC
technically today is almost the last day of work and tomorrow we have our RGSoC ending celebration, so today was all about gathering what we've done , thinking about how we could've been done better , although we haven't done much , we certainly learned a lot , we have plans to learning more and contributing more . also , we kept working on our script for the talk of the conference
September 28, 2016
Team Ruby's secret (Exception Notification)  — at September 28, 2016 21:27 UTC
today we didn't do that much ...I had finished my lectures late at college.
-Still working on the generator.
-We had our weekly call with our lovely supervisor Linda <3
-We had the wrap-up call with Linda and our mentor and remote coach.
We are really sad that the summer of code has come to an end and we haven't finished our project yet but we decided to try to continue working on it in our spare time.
September 27, 2016
Team Ruby's secret (Exception Notification)  — at September 27, 2016 23:11 UTC
turning the gem into an engine turned out to be not such a great idea cause this means that the gem won't support Sintara anymore , so as an alternative solution we're creating generators but still the generators are not working in the dummy app .
Adding more to the script of the talk of our conference and practicing the script and calculating our timing
September 26, 2016
Team Ruby's secret (Exception Notification)  — at September 26, 2016 21:54 UTC
4 days left for the end of this wonderful summer .The 3 months have passed so quickly :( .We're really happy that we got the chance to be part of RGSoC 2016 <3
Today after finishing our lectures at the college :
-we continued working on the script of the conference.
-we're working on a generator to do the job of saving the exceptions but it hasn't worked yet.
-we searched for some Bootstrap dashboard templates to use them but we still have to finish the generator first.
September 23, 2016
Team Ruby's secret (Exception Notification)  — at September 23, 2016 21:58 UTC
Today is the last day of our summer vacation ,tomorrow we're starting college .One thing that we learned from RGSoC is that we should study for the sake of learning not for only getting high grades , of course we want to get high grades but after that summer that won't be our main goal anymore . Learning new things is awesome <3
for today :
1)we worked on database
2)we watched some tutorials talking about creating dashboards but we still need to dig a little bit into bootstrap to implement the features that our mentor wants.
3)we worked on the script of the conference's talk .
to do :
- creating a generator
-using bootstrap to help us with the dashboard
September 22, 2016
Team Ruby's secret (Exception Notification)  — at September 22, 2016 22:32 UTC
Today , we had a call with team Loadtocode regarding our conference talk and after the call we did some planning to the talk and brainstorming some ideas on the script , we also contacted our coaches to have a call regarding our project to see what's going wrong
September 21, 2016
Team Ruby's secret (Exception Notification)  — at September 21, 2016 21:10 UTC
Now we are stuck . There is something which we can't figure out regarding the dashboard .We now can catch exceptions and store them , the problem is that the gem supports Sintara and Rails, and the method we used supports Rails only . We are trying to ask on the helpdesk , trying to prepare calls with our coaches and our mentor . Hope we can figure that out soon :D .
During the past days we've been working on Nada's laptop only because the terminal on mine was giving errors for almost every command I type , it was driving me crazy but today , thanks God , I managed to fix it .
September 20, 2016
Team Ruby's secret (Exception Notification)  — at September 20, 2016 23:53 UTC
Today we went to the Portuguese embassy to get our visa and finally we got them.we had our weekly call with our lovely supervisor Linda .Lastly , we're putting plans on organizing Rails girls events here in Cairo and hopefully, we'll be able to achieve this goal soon
September 19, 2016
Team Ruby's secret (Exception Notification)  — at September 19, 2016 21:51 UTC
Today , we worked on our 2nd blog post with mind freezing and very slow internet connections but that didn't stop us and here we are sharing our happy moments with you ladies <3 .
We also talked with our remote coach that was in charge of Rails Girls Cairo before .We discussed the possible ways of how we can re-activate the work here in Cairo once more and getting more and more girls into tech.
September 18, 2016
Team Ruby's secret (Exception Notification)  — at September 18, 2016 22:20 UTC
We decided to work today to make it up for the long vacation of the feast .
1) We read a blog about getting started with a rails gem-engine.
2)We added a model to the gem and tried to run it but it gave an error which we couldn't understand but still searching.
3)We did some modifications to the gem .
Basically what we are trying to do now is searching for a way to save the exceptions , a way that would work without giving errors .
September 16, 2016
Team Ruby's secret (Exception Notification)  — at September 16, 2016 19:40 UTC
We are finally back , full of energy , after enjoying our feast .We are still working on the engine , having some scattered ideas here and there . Today we did the following :
1) read a blog about rails logging and error handling.
2)turned the gem into an engine, building a controller and a model.
3)build a new notifier that saves the exceptions but it still needs some modifications.
4) mounted the gem "exception-notification " in the dummy file of the engine.
5)yesterday , we happily had a call with team LoadToCode , we mainly talked about the outlines of our coming talk at RubyConfPt .
September 10, 2016
Team Ruby's secret (Exception Notification)  — at September 10, 2016 05:39 UTC
we kept working on the engine , we were able to catch the exceptions and add them to a database just like the project is supposed to be , the problem is that the menthod we used in different than the method used in the gem , so still we're trying to figure this out
September 08, 2016
Team Ruby's secret (Exception Notification)  — at September 8, 2016 22:57 UTC
Now we are in a steady state , we didn't make any noticeable achievement today , just working on the engine . We also read about Mongoid and checked out the codeschool course about it . The best part about what we are working on now is that we are trying to build something from scratch , it makes us happy as if we're building our homes or renovating our rooms .
September 07, 2016
Team Ruby's secret (Exception Notification)  — at September 7, 2016 21:37 UTC
-After watching different tutorials about mountable engines and how to create them in the past days , today we wanted to sum up all the info we gathered , so we read the rails guide for engines and it really made us more concentrated and focused about what we are trying to learn .
-We divided our work on the dashboard to two levels :
The first level : working on how to catch the exceptions and store them in a database.
The second level : working on Rails admin panels .
-We started working on the first level today , building our engine , hoping we could finish great part of this level before our feast.
September 06, 2016
Team Ruby's secret (Exception Notification)  — at September 6, 2016 22:53 UTC
Today our PR was finally merged after long days of hard work . We're focusing on creating the Dashboard for our gem "The exception_notification" , we started breaking the project into small chunks and talked with our mentor to make sure we're on the same page. Definitely, a lot to learn but the good thing is that this time, we have a clear vision.
Today we learned about :
Engines and mountable Engines
Rails admin panels
September 05, 2016
Team Ruby's secret (Exception Notification)  — at September 5, 2016 22:23 UTC
Today and the following days we are going to focus on learning new concepts that would help us build a Dashboard -our main challenge- so today we started by watching a Railscasts talking about mountable engines , we tried to explore Airbrake and ActiveAdmin because they are a bit similar to what we want to do and we also read about generators and Bootstrap on Rails .
September 02, 2016
Team Ruby's secret (Exception Notification)  — at September 2, 2016 16:00 UTC
after 45 days of confusion , desperation and spinning around , finally we are able to solve issue#334 with the help of our coaches .
In our meeting today with our coaches we also set the outlines for the dashboard .
This is how we express our extreme happiness :The sound of zaghroota(loooooooooolyyy) : https://www.youtube.com/watch?v=qhp2ccpbHKM
September 01, 2016
Team Ruby's secret (Exception Notification)  — at September 1, 2016 23:25 UTC
Today we did the following :
1) tried to use :stmp method to preview the html mail
2) we put a plan for tomorrow's meeting with our coaches.
3) we did a PR for the contribution guide .
Team Ruby's secret (Exception Notification)  — at September 1, 2016 01:15 UTC
Today we discovered a new thing that helped us tons , we were finally able to preview the mail from our dummy app , using the 'dummy' took us some time to get used to it ,but eventually we got where we want to. Also we were able to preview the mail in the testing environment. We discovered the ":file" method in sending a mail and it helped us tons.
Plans for tomorrow :
1) using :stmp in development env to preview the .html mail
2)putting everything together and hopefully talk with our mentor
August 30, 2016
Team Ruby's secret (Exception Notification)  — at August 30, 2016 21:56 UTC
Today we did the following :
1- watching the part talking about Gem development from building Ruby gems course.
2-reading a blog about letter opener gem.
3-we tried to do post request data for a large hash.
4- we tried to get the size of a param hash.
August 29, 2016
Team Ruby's secret (Exception Notification)  — at August 29, 2016 22:19 UTC
Today we had a Visa appointment at the Embassy of Portugal, we had to wait for a very long time and in the end they asked for more documents . It's harder than we thought it could be , specially because we're still students but we want to attend the Rubyconf in Braga , so we'll have to deal with these difficulties .
Later,we were back to coding , we keep exploring new things about our gem every single time we add something new , we learn the hard way .
For us the whole project is a big chanllege ,bigger than we expected but that won't stop us , we have a goal and we're working on it
August 26, 2016
Team Ruby's secret (Exception Notification)  — at August 26, 2016 20:46 UTC
today we were trying to manually test the gem using the dummy app , we manually tested it before by installing it in an app that we had done a long time ago . We know now how to launch the dummy app , the problem is in the route that we should use , that's what we have been trying to know . We also watched a tutorial explaining the difference between POST and GET .
August 25, 2016
Team Ruby's secret (Exception Notification)  — at August 25, 2016 21:49 UTC
today we did the following :
1-manually testing the code .
2-using rails method after we had found out that we were using a ruby method that didn't work.
3-adding changes to all view files.
4-SUCCESFULLY TRUNCATING THE MAIL WOHOOOOOOOOOOOOOO
August 24, 2016
Team Ruby's secret (Exception Notification)  — at August 24, 2016 23:10 UTC
today we did the following :
-adjusting .text files
-manually testing the changes in the code
-learning more about Ruby gems .
-learning more about Post Request
August 23, 2016
Team Ruby's secret (Exception Notification)  — at August 23, 2016 20:30 UTC
today , we again focused more on learning , trying to deeply understand the thing we're dealing with , we re-watched some videos of a course talking about how to build a gem , we had abandoned this course a long time ago because back then we found it quite hard to understand but now after getting our hands somewhat dirty with exception notification gem , the course seems more clear and actually emphasizing the huge amount of information that we got to know since the beginning of the work . We also read more and more about Post Request and functional testing . At the end of the day , we tried to do some changes to the code after we had finally discovered how to run the dummy app .We feel that we're so close to the solution .
We also had our weekly call with our supervisor .
August 22, 2016
Team Ruby's secret (Exception Notification)  — at August 22, 2016 22:27 UTC
today we decided that we should read more and more about testing , so we didn't work on the code , instead we watched tutorials on functional testing and read some blogs about Post Request .Actually we have learned that we still have a lot to learn .Whenever we feel that we had finally reached the shore we discover that we are still in the middle of the ocean and that there are still more and more adventures that we shouldn't miss.
We also have got some documents that are required for our trip to the conference .
August 18, 2016
Team Ruby's secret (Exception Notification)  — at August 18, 2016 22:50 UTC
Today was one of the best days in RGSoC to us at least, we did lots of preparations and research on our trip to Braga to attend the Rubyconf 2016 , we had endless calls really but we're glad we did ,it's like suddenly the universe is sending us tons of positive energy.
Learned topics in minitest (setup , teardown) and also started learning about functional testing.
The day was full of action ,motivation and excitement for the DayOff
The clock is ticking Tik..Tok can't wait to start the next day
August 17, 2016
Team Ruby's secret (Exception Notification)  — at August 17, 2016 21:58 UTC
Today we're happy with the fact that finally we're getting some guidance , we're trying 100 random things and learning tons of stuff but still we couldn't find the answer to our problems .
1)learned about faker gem ,watched a tutorial
2)learned about post and download it on Ubuntu
3)manually tested the code
4) talked to our coach
August 16, 2016
Team Ruby's secret (Exception Notification)  — at August 16, 2016 17:36 UTC
- We continued working on the test case .
- We tried a new approach for testing because the old one didn't work .
-We watched tutorials for Mountable engines and dummy app .
- We tried to run the dummy app but it gave us an error , we googled and googled and googled but we just can't find a suitable solution .
August 15, 2016
Team Ruby's secret (Exception Notification)  — at August 15, 2016 20:29 UTC
"ERRORS" the unwanted visitor who has been coming to us every single day for the last month , finally we are able to get rid of and now we have a code that run without any errors .Now what's left for this issue is the testing , we worked on it today and we will continue working tomorrow . Although this issue had consumed so much time , it taught us a lot , so we owe it tons .
August 12, 2016
Team Ruby's secret (Exception Notification)  — at August 12, 2016 20:03 UTC
Still working on our code step by step ,after we created the helper method and tried to call it in the view , it gave lots of errors , we tried to debug the code and finally decided to create a new attribute accessor in email notifier file , and move the rendering part from the view to email notifier so by this way we can call it in the view . This way nearly worked but still needs some modifications .We need to read more about Action view : rendering .We think that if this worked , testing it would be very easy .
Team Ruby's secret (Exception Notification)  — at August 12, 2016 10:53 UTC
-decided to add the code step by step
-created a new helper method
- our tests are passing
- testing is still like a black-box to us
-"Tamam" means Ok good in Egyptian dialect
August 10, 2016
Team Ruby's secret (Exception Notification)  — at August 10, 2016 22:27 UTC
-Today we continued working on the issue .We tried to check what made the test cases failed after the PR and corrected some syntax errors , at first the tests didn't run and it always gave "rake aborted" , but after some modifications the tests ran giving more specific errors which will make us more focused , we hope . We mainly face some problems in rendering partials and testing them but we're working so hard and trying to do our best to discover the missing piece .
-We also agreed with our coaches on specific hours for our questions .
-We talked with our remote coaches , discussing the issue .Actually they motivated us so much <3 <3
-We had our weekly call with our supervisor .
August 09, 2016
Team Ruby's secret (Exception Notification)  — at August 9, 2016 20:37 UTC
1) talked with our remote coach .
2) we moved a part of the code from the view file to email notifier file after dividing this part of code into chunks , each with a new method which will make the testing much more easier .(thanks to our remote coach)
3) we did a PR but the test cases failed .
4) tried to check the code again to know why the test cases had failed .
5) worked on testing ,we want to mock a new mail object where the sections that are rendered are > 4mb , we kept searching but we can't find a suitable solution .
August 08, 2016
Team Ruby's secret (Exception Notification)  — at August 8, 2016 19:28 UTC
so today we continued fixing some of the errors , starting from Bundle and ending with Pry .
We worked on the following :
-upgrading to the ruby version 2.2.5 as our mentor advised us.
-fixing the error of bundle and installing the gems which we were unable to install before .
- running bundle exec rake to test the dummy app and it gave all 18 errors due to one single line 😑
-talked with our mentor to ask him for any alternatives for this line and we ended up removing it as our mentor told us that's not important.
-talked with our remote coaches .
- added some code to the gem but unfortunately it didn't work .
-installed Pry instead of byebug to debug our code. We watched some tutorials to know how to deal with Pry , it's pretty much like Byebug .
-We agreed with our remote coach to have a call tomorrow .
August 07, 2016
Team Ruby's secret (Exception Notification)  — at August 7, 2016 21:28 UTC
Well , it seems that all the powers of this universe are against us . Everytime we run any command ,we get a list of errors ,even Bundle we get errors with that too and it takes hours to finally be able to fix these errors ,that's why we kept working on the weekend.We tried to fix as many errors as we possibly can so that on Monday we can focus entirely on the code itself .
We don't really believe in luck but we believe that is you work hard enough you'll eventually see results
August 05, 2016
Team Ruby's secret (Exception Notification)  — at August 5, 2016 23:42 UTC
Today , we finally started working on the gem itself on Linux ,life is so much easier there, although we had some troubles installing rvm and it took us hours to finally get the job done ,we got through all of this and now we can really focus on the coding part the our work.
We're planning to work on the weekend as we don't want to waste any more time ,we're hopeful ,we can finally see the sun shines ,now we got someone who's actually helping us.
Team Ruby's secret (Exception Notification)  — at August 5, 2016 00:13 UTC
As we had lots of issue and troubles with windows , finally we moved to Linux Ubuntu , started setting up the working environment , we had lots of issues and error when installing Ubuntu but finally and with the help of the coaches ,we're now ready accelerate our pace and get the work done .
In Egypt, we have this expression "starting over on white water" which means having a new fresh start with clarity and no mystery,so that's what we've done today.
August 03, 2016
Team Ruby's secret (Exception Notification)  — at August 3, 2016 21:18 UTC
So finally we found out what had caused this irritating delay and this infinite number of errors -_- , it is that windows is not the best operating system when dealing with gems so today we did the following :
-watched a tutorial on how to Install Ubuntu Linux in Virtual Box On Windows 10
-installed virtual box and Ubunto
-made a call with our remote coach to discuss what would be best for our next steps and we decided to start working on the side gem tomorrow .
August 02, 2016
Team Ruby's secret (Exception Notification)  — at August 2, 2016 19:24 UTC
Today we did the following :
- We tried to run the local gem after the changes we've made in an application but it didn't work.
- We used the byebug gem in order to debug the local gem , after so many trials , the byebug gem finally ran but it gave errors just on the next step.
-We tried every single command written in the contribution to Exception Notification gem guide but it always gives errors.
-We talked with our mentor and told him about the errors so he told us that the Ruby version we're using have some issues.
-We downloaded another Ruby version .
-We had our weekly call with our supervisor.
August 01, 2016
Team Ruby's secret (Exception Notification)  — at August 1, 2016 22:22 UTC
Well, today was a tough ay kinda got better in the end but still we're facing a problem.the problem is we're lost,we kept thinking about ways to solve the issue and we did find one and before we finalize our work ,we've been told to redo all our work, today we were searching and trying using byebug,running tests,rendering partials..we're distracted we keep moving from one topic to another to try to find something that will help us .
Anyhow,we do believe we just need some guidance so we can focus and put our time in the right direction but as long as we're confused ,we'll be struggling
July 29, 2016
Team Ruby's secret (Exception Notification)  — at July 29, 2016 19:45 UTC
So today was about wrapping up all the stuff we had learned all over the week and actually making use of it in changing a couple of things in the code of the gem .We have learned that it is better to avoid putting too much logic in the view , so we have been working on removing some code from it , we have also researched the byebug gem in order to use it in our code and the last thing we're working on is implementing the test case .
We are a little bit late so we are working tomorrow .
note : Unfortunately , our coach is so busy so he haven't sent us the patch yet .
July 28, 2016
Team Ruby's secret (Exception Notification)  — at July 28, 2016 21:54 UTC
As easy as our issue sounds , working on it is way harder ,we go through lots of difficulties and concepts we don't understand, We are still waiting for the patch to be sent .our coaches are still busy.
We are understanding byebug more and more. We were planning to finalize all our work of the issue this week but we couldn't ,maybe we need more help.
We must say that the Helpdesk helps us a lot, one thing we are sure of is that we are not giving up we're merging this PR as fast as we can.
July 27, 2016
Team Ruby's secret (Exception Notification)  — at July 27, 2016 17:29 UTC
While waiting for our coach to send the patch we researched a couple of things that would help us later :
- we wanted to know more about the Byebug gem , what it is used for and how can we use it in Rails applications (still researching)
-we learned how we can write the statement that comes in test " statement" do (thanks to the help desk ) and how we can call a method and its test .
-we checked an interesting blog talking about top 10 mistakes that Rails programmers make.
To do :
- read about partials
July 26, 2016
Team Ruby's secret (Exception Notification)  — at July 26, 2016 18:49 UTC
Today was about organizing our priorities ,setting up the workflow we're going to use in creating our side gem ,our coaches suggested we use Linux but we're not sure if we're gonna like it so we're still using windows ,it's a bit harder but doable .
Our coach was busy ,we're waiting for the patch he's gonna send so we can apply it to our PR, the patch we worked on during our meeting.
lastly,we had our weekly call with our supervisor Linda to keep track of our progress
July 25, 2016
Team Ruby's secret (Exception Notification)  — at July 25, 2016 18:57 UTC
After a splendid weekend , we started working again with a refreshed mood .
Today we were able to :
-move some code out of the view and thus solving the problem of having too much code in it.
- extract 10 elements out of a hash.
-work on the test case ..
we waited for the patch to be sent by our coach but he was very busy today so he would send it probably tomorrow.
July 22, 2016
Team Ruby's secret (Exception Notification)  — at July 22, 2016 18:57 UTC
Today is a really different day we had a meeting with our coaches finally , they discussed the issues that were confusing us and slowly the image becomes clear .
We had the issue of having too much code in the view file which is not good ,so we were able to move to code away from the view ,this will help us a lot in doing the rest of the code .
Last week was very depressing to both of us but now we're really excited to work and do our best.
Also ,we finally took our team photo at last...
July 21, 2016
Team Ruby's secret (Exception Notification)  — at July 21, 2016 23:48 UTC
Thanks to the help desk , some issues in the testing that were confusing us began to clarify .
We began to focus on the features of the Minitest and learn the differences between them through reading blogs and watching tutorials .We are really enjoying the journey of testing although we hadn't expected that it would take all that time . We are happy because day after day we are starting to understand the source code of the gem .
July 20, 2016
Team Ruby's secret (Exception Notification)  — at July 20, 2016 20:34 UTC
The testing process is taking way longer than we excepted , but we're holding on and we're not giving up , discovering more and more how the testing process is working on our gem and we hope we can finally merge our PR as soon as possible but anyhow we're enjoying the learning process and discovering the little details that matters.
July 19, 2016
Team Ruby's secret (Exception Notification)  — at July 19, 2016 17:41 UTC
We implemented a code for the test case but it is still incomplete , there is a missing piece which we are trying to find , so we are still working on testing , trying to search for more resources to learn from , hoping that we can solve the mystery.
Although we haven't solved the mystery yet , we are really enjoying ourselves , learning new things and understanding the Exception Notification gem more and more .
July 18, 2016
Team Ruby's secret (Exception Notification)  — at July 18, 2016 21:56 UTC
WE are still working on our test case ,still testing is a very new unfamiliar topic , it's taking more time than we expected , we're using different resources to learn from trying to find guidance as much as we can.
On the other side,We're daydreaming about Rubyconf in Portugal , we really hope we can go on October,the conference sounds amazing and the city is out of this world
July 16, 2016
Team Ruby's secret (Exception Notification)  — at July 16, 2016 03:07 UTC
Actually today we focused on testing only .We read the testing guide for Rails and watched some tutorials on Railscasts .We started making some test cases.
We happily filled in the conferences survey .
July 14, 2016
Team Ruby's secret (Exception Notification)  — at July 14, 2016 23:01 UTC
-We want to deeply understand the gem we are working on so we decided to check out some of the pull requests that were merged before in the hope that this would help us fully understand the source code . We want to climb the ladder step by step .
-We talked with our coaches to give us their review about our solution for the issue .
-We did some changes to the code to improve it.
-We also continued working on testing and our mentor has asked us to add a test case to the solution we did to the issue which we will be working on tomorrow .
-We also have chosen the conferences that we would like to attend in order to fill in the survey.
July 13, 2016
Team Ruby's secret (Exception Notification)  — at July 13, 2016 15:35 UTC
Today we've mainly worked on testing focusing on mini test , read more about Action Mailer , watched more Ruby tutorials and worked on a small Ruby app .
We are waiting for our mentor to reply and give us his opinion about the issue and to tell us which is best for our next step .
setting a plan for the next days to make the best of them .
July 12, 2016
Team Ruby's secret (Exception Notification)  — at July 12, 2016 18:10 UTC
Today was a really happy day,finally ,we started seeing the results of our work
1)We did our second PR for the same issue nd adjusted the code
2)All checks of the PR passed,Yaay.
3)We did our weekly call with our supervisor Linda
4)Almost endless research on different topics of our project
July 11, 2016
Team Ruby's secret (Exception Notification)  — at July 11, 2016 15:10 UTC
With a refreshed mood and energetic spirit after celebrating our feast , we managed to do the following :
1)We published our first blog post ,finally revealing our secret, we hope you like it :)
2)We also happily did our first pull request .
3) We sent a mail to our mentor to discuss some questions related to our solution of the issue
to do :
watch more tutorials on Ruby on Rails and testing.
have a call with our supervisor tomorrow.
July 06, 2016
Team Ruby's secret (Exception Notification)  — at July 6, 2016 01:43 UTC
Day 5 was really important as we,all of the team members including our mentor, had a call with our supervisor ,Linda , we set the timing for our weekly call with her.
Then we had a call with our coaches where we discussed some of the problems and issues facing us in our learning journey
We kept researching on topics we need to learn and finding courses and good resources to study from.
July 05, 2016
Team Ruby's secret (Exception Notification)  — at July 5, 2016 01:08 UTC
On day 4 we completed our work on the issue , we're still learning about topics related to our issue such as action-mailer and testing
We were finally able to solve the mystery of the issue ,it just took from us a long time to finally understand the source code ,we still have the testing process to be able to finally submit the issue and hopefully we can finish by tomorrow.
July 03, 2016
Team Ruby's secret (Exception Notification)  — at July 3, 2016 23:37 UTC
Day 3 :
1)We researched on truncate method to be able to use it in solving the issue .
2)We read about truncating files from Ruby cookbook.
3) We re-checked Ruby on Rails guides focusing on the internals of Action Mailer especially sending multi-part emails.
4)We talked with our coaches to ask them about few things.
Actually the picture of the puzzle of solving the issue is starting to form but still missing few pieces to be completely ready .
Team Ruby's secret (Exception Notification)  — at July 3, 2016 00:05 UTC
Day 2 was all about research a few things became more clear to us in the issue we're solving like the difference between .size and .length ,at first it seemed too simple to even think about but it does make a difference if you're using Unicode.
It's like puzzle indeed , you keep putting the small puzzle pieces together and eventually you get to see the full picture.
P.S. : We created a little video as an introduction and posted on our twitter,Here's the link if you wanna check it out :D
July 01, 2016
Team Ruby's secret (Exception Notification)  — at July 1, 2016 22:06 UTC
Day 1 was even better than we expected ,we had so much fun
*Set up our working environment
*Took our very first picture and tweeted about it
*Our mentor already gave us an issue to work on before the program starts , so we started exploring it and decide if there are concepts we need to learn
*We discovered that there are a few things we need to understand better,so we started to google it
*We were so happy to use our twitter account and watch all the likes ,retweets from other teams and looking for the rest of the teams so we can follow them
We wanted to celebrate the day and have a mini party but We'll wait after our feast and have a mini celebration four our team but until then We're really enjoying every moment of it