Displaying activities 1 - 25 of 3946 in total
August 16, 2018
Team Barcelona Duo (Exercism) — at August 16, 2018 15:16 UTC
During our daily stand up we reviewed what we learned about testing so far, and identified concepts that we need to understand in order to write good tests. Amalia realized that she still lacks a good understanding of classes, and the four pillars of object-oriented programming: abstraction, encapsulation, polymorphism, and inheritance. A fundamental understanding of classes and inheritance is necessary to understand how to properly model and write tests. She spent the day reviewing classes and getting a better understanding of OOP.
Lori spent the day yesterday working through a practice problem that our coach Javi created for us so that we can learn about classes, object-oriented modeling, and testing. She continued to work on this problem set, along with some ruby Koans. She also had a session with Javi to review her solution. Overall, the past two days have been filled with learning a lot of new concepts.
In terms of output, the last two days have been slow, but in terms of learning, they have been important milestones. A week ago we did not understand what object-oriented design was. The concept is still not 100% clear, but we know that it's very important in order to properly model our programs, created classes, and write sound tests for our code. The other really important thing is that we are learning how to identify good sources for learning. While we won't be able to cover everything during the summer, we are creating a list of concepts we will need to understand, and we are understanding why we need to learn these concepts and how they fit in the development process. This will give us a great base to continue our learning.
August 15, 2018
Team Akaringular (EBWiki) — at August 15, 2018 20:52 UTC
- Updated paper trail gem to the latest version
- Added specs for the admin
- Made some requested changes to pending pr ( moving modified changes on bootstrap-mod.scss to cases.scss )
- Later in the day we hung out with Andreas Finger, senior developer. We didn't want him to leave Kenya without us learning something new from him. Asked some general questions but this interested us more, Where do one start on realizing that there is a bug in the system? for him its doing a regression test, and many more, for sure we learnt a lot.
Team $we init (Probot: build your own GitHub app(s)) — at August 15, 2018 18:00 UTC
What we did?
- Discussed idea of our second bot with coaches.
- Worked on obtaining string version of issue template and issue body.
- sent pr for the basic setup.
- Work on comparing the above two formats.
Team 101 Days of Summer (Servo) — at August 15, 2018 17:15 UTC
Happy Independence Day from India 🇮🇳
- The PR which were solving yesterday got reviewed.
- We updated the PR and it got merged too. Yay :D
- We were able to compile our code on Janitor today, finally! There were problems related to outdated containers which had some missing libraries.
- Got some hack with the help of community to finally figure this out. Happy moment :)
- Will start again with solving the timing tests problem!
Team Popcorn (Nextcloud) — at August 15, 2018 16:26 UTC
- Arati worked on refractoring her code on the Add Addressbook using the comments the App maintainer gave on the Github commits
- Jessica also did some refractoring based on the App Maintainers comments and started on the Popover menu
- We had a meeting with our coach Markus and the App mainainer to talk about intergrating BEVM in our SCSS and also had a mini code along session with Markus to show us in more detail how to get started.
It was a good session with the App maintainer today discussing our naming conventions and folder structuring as well as learning more about BEVM. We have also been enjoying refactoring our code and learning new tips as we go!
Team GirlsCode MK (Bahmni) — at August 15, 2018 15:02 UTC
- working remotely today, but had a long team meeting to share progress, what we are working on at the moment
- Georgina: working on branches, forks and creating new learning repositories. The need to practice in a safe place and with simpler or out of project scope was necessary so she has created a new learning app to test out some code. Looked at preparation of next blog, so whilst sorting out github, forked RGSoC, installed Jekyll, had an issue with changing ruby version and updating the .ruby-version file to 2.3.7 and got all setup so we can add stuff as we go for the blog. Time is going so fast we are nearly half way!
- Eva: working on a reactjs Udemy course and getting a better understanding of how reactjs works (even slightly more advanced concepts): things I've learned today are higher order components (HOC), pure components, Radium and CSS modules, npm eject for editing project config, better project structure, proptypes, Aux wrappers for adjacent components.
- Eva: Ploughing through the tutorial until I get to the modals and ajax requests - which are the two things needed for our current story.
- Eva: reading on web design and usability and getting better at implementing basic design principles
- potentially re-structure our app into smaller components (our FormContainer component is quite large and could be broken down - the fetch request with its conditional logic should probably go into its own component)
- coming up with conditional logic for displaying either the spinner, the error popup or the success popup
Team potatoCode (stretchly - break time reminder app) — at August 15, 2018 12:54 UTC
Wrapping up (we think)
our almost done issues. Today we decided we would be close to finish them up.
We had our team call yesterday with Ana Sofia. We're happy with the way this Summer of Code is challenging us in exploring the unknown and contributing to Stretchly in particular. We told Ana Sofia that we would be finishing up the 4 issues that are open now and continue.
This morning we had a phone call with our mentor, project owner Jan. He's so supportive and we agreed that we would try and finish the issues in this week. Also he looked ahead of what would be a good opportunity to do after these features have been build. There's a lot of options and Jan asked us if we wanted to learn anything in particular he would look at the backlog of issues and match them with our 'goal'. Awesome mentor!
Wrapping up the issues today still is a bit to challenging, we keep encountering this problems with the update tray menu. It makes the app buggy and that's what you don't want.
Jack really helped us out today and gave feedback on our code. It's great we can reach out to our coaches for questions :-)
That's it for now from team potatoCode
Team Brazilian housewives coding (Public Lab) — at August 15, 2018 05:15 UTC
Today the PR (#3134) for the people_locations endpoint improvement that we have been working for the last 2 weeks was merged!
So with the new code merged from yesterday, we started working on calling the new profiles endpoint for the autocomplete feature passing an optional field for searching the users by username only. We also studied a little more about unit tests.
August 14, 2018
Team Akaringular (EBWiki) — at August 14, 2018 21:10 UTC
-Helped one of our member solve merge conflicts.
- Had a hangout where we discussed RSpec testing
- Made some progress on writing tests for one of the features though two tests are still failing.
- Tested email validations.
- Had a look at how gem devise work in sessions
Team Sectumsempra (Chapel Parallel Programming Language) — at August 14, 2018 19:10 UTC
We had our monthly call with our supervisors, coaches and mentors. Apart from that, our mentor listed the next steps for us.
Here's what we did:
- Avneet: My PR on radix sort has been approved. Yay! :D My work today involved figuring out ways to make the radix sort parallel, and reading about Chapel's parallelism.
- Rupal: Finally, after she was able to create her very first PR. Her work involved testing the LSB version. Great going! :D
Cant believe 1.5 months are almost over. This journey is going quickly. Can't wait to see what we are able to achieve next :D
So far so good,
Team Sectumsempra (Chapel Parallel Programming Language) — at August 14, 2018 18:59 UTC
We have made progress with our respective tasks, and are hoping we would be able to get on with the parallelized version of the sort soon. Apart from that we had our weekly call with our supervisor, and it was a nice refresher talking to her.
Here's what we did individually:
Avneet: Worked on changes suggested for the MSB radix sort, and finally after adding the performance and correctness test it is now complete. Also researched about API design and how to make the MSB version parallel.
Rupal: Worked on testing the LSB version of radix sort.
Team GirlsCode MK (Bahmni) — at August 14, 2018 16:19 UTC
Had our monthly meeting with local coaches and supervisor - Team Photo!
Introductions, Fun Fact, Expectations
Discussed communication and how to get better coaching and how to be a better coach.
Discussed consistency with meetups.
It was agreed that if we need more help that we need to be more specific in the help we need and more direct questions on slack. It is a balance between helping and struggling. So we will keep our weekly catch up meetings at 8pm on Mondays. This is a 10min what is happening meeting. We will also continue to give summaries of these meetings for people that can't make them.
RGSoC slack channel discussion about Agile. This was good to revisit especially as it wasn't long ago at girls code that we had our Agile workshop. Tools: https://youtu.be/Z9QbYZh1YXY, https://funretro.io/, Sprint-Retro-Repeat, stand up meetings, kanban, trello, and stories. We are using Jira for our workflow and stories.
Asked coaches direct questions today. Asked their learning journey of react and looked up roadmaps to help facilitate this. Trying to get a clearer picture of what coaches have done with React to help advise us. GTH expressed the problem with trying to find good quality learning resources that did not involve installing libraries, or redux. It is hard to gauge whether it is a lack of React knowledge or whether libraries are really needed.
Continued with Udemy course. Eva said it is beginning to make more sense the 2nd and 3rd time round!
Eva using pomodoro for videos. GTH has been changing between videos, creating test branches, playing with app and error codes. Changing activities is also as good as a rest. Whilst becoming fixed on Fetch API error handling and modals, GTH had a thought about our date issue from our previous story. A little progress and then back to the current story!
Meetup with mentor about current story
Fetch API error handling status
Team Barcelona Duo (Exercism) — at August 14, 2018 15:14 UTC
During our standup this morning, we shared with our coach Maikha what we did to finally understand our Git workflow. She suggested that it would be great to give a short lightning talk on how to contribute to an open source project so that other people at Thoughtworks can learn about Exercism, and from what we are doing this summer. We also discussed unit testing and TDD with Maikha. The rest of the day was spent learning about different types of expectation statements and practicing writing unit tests.
Testing and TDD are quite large topics, but we are slowly understanding more fragments and different parts are starting to make sense. It's empowering to realize that through practice and patience we can learn anything, including testing and TDD. It's not something that is impossible to master. Getting comfortable with not understanding something on the first day has been an incredible lesson. Each day we have the opportunity to add nuance and layers to our understanding. Eventually, after several attempts and many failures, things click and make sense. Trusting that things will one day make sense with enough practice and patience is a lesson that we will carry with us for the rest of our careers.
Team 101 Days of Summer (Servo) — at August 14, 2018 15:06 UTC
Today, we were working to update one of the PRs which got blocked due to external reasons some time back.
- But we had a hard time dealing with merge conflicts.
- I (Nupur) decided to start using Janitor which will help in running code remotely, because my laptop has become too slow and takes more than an hour for every build which is ideally a 5-10 min task!
- Janitor is giving more trouble. It was repeatedly showing the low disk space error. We deleted the earlier builds and tried rebuilding, but it is stuck on another weird error now. Next task is to talk to the Janitor community and ask more questions :P
- We are hoping we can solve this task soon and get back to the debugging work....
Team Popcorn (Nextcloud) — at August 14, 2018 14:51 UTC
- Jessica worked on refactoring and cleaning up the code she was working on and looked at styling for the share addressbook section
- Arati was back in today and caught back up with messages
- We had our coach Lora in today for our second knowledge share sessions. She was giving us tips on working with Dev tools
Tomorrow we have our weekly meeting with the App maintainer to discuss structuring our CSS and next steps so it has been good to get some solid coding done to be able to present to him.
Team Brazilian housewives coding (Public Lab) — at August 14, 2018 04:22 UTC
We started our week with an approved PR (#3134)! We are also almost finishing #3217. After these two PRs are merged we will call them on the feed RSS methods, so we decrease the amount of duplicated code around the codebase.
Today we started to study unit tests. And as soon as we have the necessary knowledge we will write new tests for the Search API.
Team $we init (Probot: build your own GitHub app(s)) — at August 14, 2018 01:57 UTC
What we did?
- Discussed idea of our second bot.
- Created basic bot setup of the second bot.
- Coding for second bot.
- send pr for the basic setup.
August 13, 2018
Team Akaringular (EBWiki) — at August 13, 2018 20:24 UTC
About the weekend
Th e Rails Girls meet up was awesome. We had a fun time together. Our guide is Michael Hartl's Rails 5 book. All the attendees were able to deploy their applications on heroku.
- We updated the changes requested on our first blog.
- Figured out how to implement sending emails after user is successfully registered on gem devise, using a microservice.
- Today we able to open and complete three pull requests and also finished on one that was pending.
- Caught up with our mentor on our progress so far.
Team DelSquared — at August 13, 2018 18:48 UTC
Today we ran code on accelerometer to check its functioning with Tessel 2. Then we dived into issue #18 (https://github.com/tessel/reach-wg/issues/18) on tessel/reach-wg. We made the circuit and we are trying to figure out how to make the accelerometer send data to ESP32 via I2C protocol.
Till we meet again,
Team Rubies (if me - mental health communication app) — at August 13, 2018 18:22 UTC
Tasks completed today
- Started working on tests for Rails (Rspec)
- Continued working on mailer.
Things we learnt
Team Barcelona Duo (Exercism) — at August 13, 2018 17:20 UTC
We started our day with our daily standup. We used this time to review what we learned about testing and to discuss what we wanted to accomplish during the day. We realized that while we understood the process to create a PR, we still did not understand how to sync our fork and local copy with the Exercism upstream. We decided to spend some time trying to figure this out so that moving forward we have a clear idea of our git workflow.
One thing that was helpful was to draw out the pieces of the problem that we do understand. We saw our coach Maikha do this last week, and found that it is a very useful way to break a problem down into smaller pieces so that you can see the gaps. We did some research on stack overflow and once we had a better understanding of the problem we were having with our git workflow, we reviewed our thought process with our mentor Jeremy. The session with Jeremy was super helpful. He walked us through two ways of syncing the local repo and our fork with the upstream and explained when you would use each scenario.
After the session with Jeremy we were able to put what we learned into practice and finished up the remaining tasks that were pending on issue # 3966.
We also spent some time installing some libraries we need in order to analyze the mentor comments. Our goal for this week is to start cleaning up the data so that we can begin the analysis.
The highlight of the day happened at the end of the day when Lori and I explained to each other what we learned about the git process. By explaining the process to one another, we realized that we understood each piece of our git workflow. It is so rewarding to see how the fragments of what we learn are finally clicking and making sense.