ActivitiesAtom Feed

Displaying activities 51 - 75 of 3946 in total

August 09, 2018

  • Day 29: Sweaty Cornflower Ice-Cream Popcorn

    Team Popcorn (Nextcloud) — at August 9, 2018 17:13 UTC

    Today's Progress:

    • Jessica was working on the first version of share contacts version using axios.
    • Arati was working on setting up the functionality for importContacts--in particular working with FileReader and parsing of VCF files.

    Thoughts:

    A great day of intense coding with no meetings (nothing against meetings but getting a solid chunk of coding time feels like such a luxury).

  • Day 30

    Team 101 Days of Summer (Servo) — at August 9, 2018 17:06 UTC

    Another debug day
    We got to know the reason for the timeout of our tests but still there is some unexpected behaviour in some part of the code. Which otherwise should not have happened.
    We are now trying to replicate the unexpected behaviour in the form of a smaller test.
    Debugging is a tough thing :P

  • Day ?

    Team Barcelona Duo (Exercism) — at August 9, 2018 14:30 UTC

    Another retro

    Yesterday we finished our first Sprint, so this morning we had a retrospective followed by a team meeting to plan our next one. We were joined by our coaches Klaus and David. We all agreed that certain things are going really well. For one, we've mastered communication, conflict can lead to growth as long as a safe space has been created where everyone feels they can speak honestly and openly about their feelings. Second, while we didn't achieve as much as we expected in terms of closing issues, we learned much more than we expected. Third, to accomplish more we need to better size each issue and better to prepare for our kickoff.

    We ended our retro with some action items. First, we will spend more time preparing for our kickoff. That is, we want to explore each issue we have been assigned, identify any questions or confusion about it which will better enable us to better understand the scope and depth of each issue and schedule any training sessions with our coaches. We will also be able to review our proposed solution with our mentors before we began our sprint. Also, to improve our pair programming we will shadow our coaches and see how they pair program to get a better view of how different teams function. Finally, we decided that we need to better access how many issues we can reasonably take on during a sprint. For our first sprint we chose three issues to work on and we were not able to complete them. For our next sprint, since it is over a shorter week (we have a mid-week holiday in Spain) we will be more pragmatic.

    Highlights

    • Listening to a podcast about Exercism featuring our mentor Katrina Owens.
    • A training session on object-oriented modelling with our coach Javi and guest coach Emma.

  • Day 29 - Validating inputs

    Team GirlsCode MK (Bahmni) — at August 9, 2018 12:48 UTC

    Done

    • went over the refactored code (including destructuring, ES6 arrow functions)
    • added max date to our date input
    • reviewed how momentjs handles/formats dates
    • solved merging issues and conflicts on github - reversing a pull, re-opening a PR
    • reviewed setState with prevState in reactjs
    • held a GirlsCode MK daytime session - helped other students with JS issues (solving algorithms)

    Doing

    • validating fields (the required inputs should have a red border if they are empty)
    • learning about instant validation in reactjs forms
    • learning pseudoselectors :invalid :focus :touched
    • onBlur?

    To Do

    • meeting coach Ivo to discuss the new story
    • is more refactoring needed for the current story?
    • adding popus and spinners

  • Day 36 & 37 (August 8 - 9)

    DV Team (LivingStyleGuide) — at August 9, 2018 08:36 UTC

    Violeta

    • We had a remote session with Tetiana and Bright to install Living Style Guide
    • Inspected the website example on the LSG repo and figured out how it works and how to implement it
    • Doing Ruby tutorial to know more about what we are porting to JS
    • Reviewed the new issues and researching on documentation

August 08, 2018

  • Day 27

    Team Barcelona Duo (Exercism) — at August 8, 2018 21:43 UTC

    Refactoring code and processes

    Today we read a lot of code. Since our sprint was ending today we spent a part of the morning preparing for our next issue. It is an exciting one since it will allow us to get our heads around writing tests. To prepare we had a coaching session on writing tests and TDD philosophy with our coach Nacho. We also managed to go through parts of the codebase with him. Our questions are becoming more precise and direct as we can now identify what we don't understand.

    Mid-morning we got a kind message from Jeremy telling us that our PR had failed some integration tests so we spent some time reviewing our work and following the trail to find our errors. It was a great day's work, not measure in tasks accomplished but in the growth of our understanding. Tomorrow will be even more exciting as our delay in updating the PR has led to a merge conflict. It's hard to believe that this is inspiring us. While we know it will be a challenge, we will learn so much in the process.

    Emily introduced us to a set of online exercises for practicing Ruby. We've decided on a three-prong approach: pair programming, working alone as homework and code review of each other's work the next day. We are going to experiment with this format over the next two weeks and assess it's effectiveness.

    We learned some important lessons today. One, the way we have set up our workflow is not the best way to do it. Back then, we didn't understand enough about Git and GitHub for teams so we forked then cloned then pushed our changes to our GitHub accounts and then made a pull requests. In other words, we had created a very convoluted workflow which created more work for us and a more than a bit of confusion as we were always commits ahead and behind the upstream. While cherry-picking is fixes the problem (and adds a bit of git playtime), there are better ways.

    Finally, we took a long walk at the end of the day to check-in with each other. We realized that each of us assimilates information in different manners and this was producing a bit of confusion for both of us when we had our coaching sessions. After identifying that we have different learning styles we created a plan that will enable both of us to benefit fully from our sessions.

    Highlights of the day

    • git checkout -b experiments Enough said.
    • Elena (a ThoughtWorker not affiliated with our project) agreeing to moderate our Retrospective
    • Being comfortable asking for help from other members of the Exercism team
    • Realizing that everyday we feel more and more like we are a part of the Exercism team

  • Day 28 - holes in knowledge being plugged

    Team GirlsCode MK (Bahmni) — at August 8, 2018 20:31 UTC

    DONE

    RGSoC meetup yesterday. Running theme of this week is how to learn and then to take healthy breaks. Walks, natural breaks, pomodoro clock, and regular patterns.

    Studying and going back over basic concepts of react at a different level to try and understand gaps in knowledge. Using a udemy course, book (full stack react), looking at examples (React Rocks website), Git hub, Stack Overflow. This is sometimes a good blend. When you have had enough of reading, a video demonstration is good and welcome change. Is it possible to have too many resources? 🤯

    Communication on design of app with regards to visually showing errors.

    GTH struggling with solving date problem which Eva has already solved. Frustration of ability to learn and apply to project but good to know that coaches are reassuring that it is normal.

    DOING

    Repeated error on form with NAN error. When an invalid date is entered into DOB input. So now we need to trap error and give visual warning.

    Studying on refactoring code, moment.js, set state, prev state.

    TO DO

    Meetup with Bahmni mentor

    Tests

    CSS error handling - red border, red label and red text on invalid input

    Set maximum birthdate to todays date.

  • Day 27: RSpec book challenge continues

    Team Akaringular (EBWiki) — at August 8, 2018 19:41 UTC

    • We discussed Chapter two on Rspec testing book
    • Tried setting up Postgresql on the machine of one of Rails Girls members who is interested in contributing to the project, but we had issues installing it(Ubuntu 17). Planning to try another version of Ubuntu.
    • Resolved issues on the open prs that were failing.
    • Improved UI on Cases page

  • Day Twenty Six

    Team Sectumsempra (Chapel Parallel Programming Language) — at August 8, 2018 19:25 UTC

    We worked on the respective tasks provided by our mentors.
    Avneet: She worked on creating performance test for the MSB version of radix sort and also converted the code into a module.
    Rupal: She worked on creating tests for LSB version of radix sort.

    Next Steps

    • Working on feedback provided by the mentor.
    • Proposing a mock up for the API design for the radix sort module.
    • Thinking of ways to parallelize the code.

    Team Sectumsempra

  • Day Twenty Five (7th August 2018)

    Team Sectumsempra (Chapel Parallel Programming Language) — at August 8, 2018 19:20 UTC

    We had our weekly call with our mentor and coaches and discussed about the next tasks namely:
    - Creating a separate module for radix sort
    - Doing a performance test
    - API design
    - Parallelizing the code

    Apart from this Avneet worked on feedback provided by the coaches and accordingly modified the code and Rupal worked on her task of creating a test for LSB.

    Team Sectumsempra

  • Day 29

    Team 101 Days of Summer (Servo) — at August 8, 2018 17:33 UTC

    Tough day for us...!
    - We continued with debugging our code.
    - We discussed the issue with our mentor, and got clarity about what each of the tests are trying to do.
    - We backtracked through our code and went about inserting a large number of print statements.
    We think we are almost there and understand the reason of timeout. But we are still figuring out how to correct it !

  • Day 28: Brain-Melting Royal Slushi Popcorn

    Team Popcorn (Nextcloud) — at August 8, 2018 16:32 UTC

    Today's Progress:

    • It's a big day. We are merging our forked branch with the main vue branch in the nextcloud contacts repo! Moving forward we will be working directly in that repo (with smaller branches).
    • For this purpose, Jessica was adding comments to the sections that she was working on and she also made the PR.
    • The borders for the import section are looking sharp thanks to our mentor's suggestions! Related to this section, Arati replaced some selectors in the section to hopefully make the CSS neater.
    • We had our weekly meeting with supervisor Neta.

    Thoughts:

    We are just one week away from the half-way mark but also only a week away from the one month mark--time has a strange way of bending during RGSOC.

  • Day #30

    Team Brazilian housewives coding (Public Lab) — at August 8, 2018 03:40 UTC

    Yesterday was a holiday here in Vancouver, so we got back to work today! We also attended the Public Lab Open Hour yesterday, it was a meeting for everyone from summer of code projects (google and rails girls).

    We updated the schema.example.rb with our migration version and now we are only waiting for a final review. The endpoint now returns better and faster profiles. It was definitely a hard thing to work and we are really grateful for the help from our team.

    After we did that, we opened a new PR from the work we did on Saturday, waiting for a code review too.

    Stefanni

August 07, 2018

  • Day 26

    Team Barcelona Duo (Exercism) — at August 7, 2018 22:11 UTC

    It takes a village to make a developer

    Reflections on our first month

    We used to think that if you hadn't written your first line of code before puberty you could never become a developer. Now we know that through hard work, curiosity, a strong desire to learn and the right support team, anyone can learn the skills needed to become a developer.

    We have been very fortunate on our coding journey to have a wonderful support team. There are our local coaches (David, Emily, Javi, Jorge, Klaus, Miakha, and Nacho); there are our mentors (Katrina and Jeremy) and the other members of the Exercism team (Carlos and Nicole); our host company ThoughtWorks and all of the ThoughtWorkers who stop by our workstation each day with advice, jokes and words of encouragement. Each have been an integral part in our development and growth over the past month. None of this would have been possible without our village of coaches, mentors and the amazing people that make up the ThoughWorks community. Words seem insufficient to express our gratitude and joy at having each one of you on this journey with us.

    Highlights

    • Waking up to an awesome message from our mentor Katrina ❤️
    • Slack lessons from our mentor Jeremy (a rock star teacher ❤️)
    • Learning how to add commits to an existing PR
    • cat .git/config
    • Learning the difference between running tests in :headless_chrome and :chrome and later integrating it into our bug fixing
    • Flying a drone at the Lunch and Learn

  • Day 26: Refactoring

    Team Akaringular (EBWiki) — at August 7, 2018 20:16 UTC

    • Today we finished setting up stella's machine atleast all is set.
    • We also did a little bit refactoring and opened two prs on the same.
    • We are happy to say that the people we introduced to Open source are not letting us down. Seeing them open new pr, consultation after consultation. Wow, that is great!!
    • Not forgetting our book challenge, having done with chapter 1 now on chapter 2. From wring Specs to Running them.
    • We also booked our monthly call for all of us mentors, coaches, supervisor and we Team Akaringular.

  • Day 28

    Team $we init (Probot: build your own GitHub app(s)) — at August 7, 2018 20:15 UTC

    What we did?

    • Addressed the comments on the bot
    • Had it reviewed by our mentor, Gregor who successfully tested it on his own repository
    • Gathered suggestions on making the bot intelligent at recognizing a diversity of comments and not just the hard coded strings that it responds to currently
    • We've settled on using regular expressions. NLP is something we will eventually aim for

    Plans ahead

    • Getting the bot to detect the comments that claim an issue using regular expressions
    • Scoping out the extent to which NLP can be applied here, if we take it up now.
    • Documenting all the work we did in a blog!

  • Day 26

    Team DelSquared — at August 7, 2018 19:33 UTC

    Hi All!

    Today we talked to our coaches about the RFID issue and the Fritzing issue, but we felt that more clarity was required on them. Tomorrow we have a meeting with our mentor Kelsey, so we will be able to ask our doubts there. Our work on the modules and Fritzing issues continues.

    Till we meet again,
    Cheers!

  • Day 27 - Progress has been made!

    Team GirlsCode MK (Bahmni) — at August 7, 2018 16:43 UTC

    Done

    • met with Bahmni mentor Ivo who is the most patient coach on the planet!
    • discussed the date functionality again and this finally led to some breakthrough
    • we were also talking to our local coaches and asking them about best practices - sometimes there are many possible solutions and it's hard to see what's right (e.g. question: in Reactjs is it better to bind functions or keep them as anonymous functions that are fired up onChange? answer: no definite preference. Just be consistent.)
    • refactored our existing code, removed unnecessary items from react state, which makes our app clearer and more concise
    • read a lot of momentjs documentation: we are now much clearer on formatting issues and calculating the difference between two dates

    Doing

    • reading up on ReactJS, watching tutorials on states vs props, react setState API
    • studying ES6 Javascript - destructuring and spread/rest operator
    • going through our code, removing what's unnecessary (both in terms of react code and css)

    To Do

    • GirlsCode MK meetup tonight which will give us an opportunity to talk about our project and less experienced coders
    • perform a npm build of our app and run it through Lighthouse audit (how are we doing in terms of accessibility and speed?)
    • talk to coach Ivo (story 3 should be coming up!)

  • Day 27: Disgusting Light Blue Watermelon Popcorn

    Team Popcorn (Nextcloud) — at August 7, 2018 16:32 UTC

    Today's Progress:

    • Jessica was working on the search input and has to start all over again as a result of our meeting today with the main maintainer of the Contacts app .
    • Arati started applying feedback that the main maintainer of the Contacts app had left on comments about the styling of the importContacts component (in particular regarding the borders of the two buttons).
    • We had a long meeting with the main maintainer of the Contacts app and discussed everything from how to structure our CSS to using actions vs mutations and more specific topics about issues we are working on.
    • We are still both feeling pretty sleep deprived from weekend busyness...

    Thoughts:

    Our coaches and mentors are so helpful to talk to, and not just about code!

  • DAY26: First major setback 😢

    Team Sunshine (Babel) — at August 7, 2018 14:29 UTC

    Sujin is working on adding Repl option to toggle Time Travel View :)
    Gyujin is sad and ashamed cause she found out that she's been working on intergrating Sandpack based on the wrong PR(outdated) 😭However she learned a lot about code sandbox codebase 😂
    We joined the RGSoC Remote meet up and talked about how to learn new things as engineers!