Displaying activities 201 - 225 of 4301 in total
September 05, 2018
Team Barcelona Duo (Exercism)  — at September 5, 2018 13:31 UTC
We started our day with our daily stand-up followed by a call with Sophia, our supervisor. One bit of feedback from both Sophia and one of our coaches was that we needed to keep a keep them informed of the work we are doing. One of the things that we have learned this summer is that there is a need to maintain consistent communication with the different members of our team. It was clear that we needed to update our process, so we updated our trello board to include the steps we are taking to learn more Rails and Ruby. This will allow them to know at a glance what we are doing at any time.
Later we had a session with our coach Jorge who helped us parse areas in the codebase that were still unclear. It is still hard to identify the helper functions on our own so the session was very useful. We did a lot of experimenting by generating code through the rails console enabling us to map different routes. We had some success manipulating the path. We are just about ready to move forward on issue#3881. Tomorrow we will write some tests and see if we can get them to pass. We are trying to complete this issue, with complete being defined as submitting a PR. Our goal is to start working our feature next week.
As a side effect taking extra time to solve what should be a simple issue of changing a link, we have managed to really understand how Rails works . This new knowledge will come in handy as we move forward.
Team potatoCode (stretchly - break time reminder app)  — at September 5, 2018 10:29 UTC
Success to celebrate:
Issues that we've been working on have been merged in an updated Stretchly Master in Github, whenever a new release of Stretchly comes, these functionalities will be in it. The PR add pause until morning and the new feature to not show breaks when the user is in do not disturb mode are now live!! 🎉🎊🎂🎏🎈
We're progressing on a new feature for Stretchly: including statistics of breaks. This and the custom wallpaper during breaks is what we're working on. For the stats we now have code to run the database first time. Next steps here include making the database update whenever an event occurs, we're for the stats interested in the duration of breaks, naturalbreaks. Then we also need to decide upon the structure, or what will be in the database. Like: do we need ID's for every event? We will expand from here probably next time.
Since our next blogpost is due pretty soon, we started making a draft for this.
That's it for now 👋🏿
Team Brazilian housewives coding (Public Lab)  — at September 5, 2018 04:42 UTC
Yesterday was a holiday here in Vancouver. It was a very good day to do nothing! XD
But today, after a well-deserved rest, we get back to work! We are waiting for the PR #3282 to be reviewed. Meanwhile, we are working on applying UX concepts to the search in the navbar (#3595) and we started to write our second blog post.
Team Sectumsempra (Chapel Parallel Programming Language)  — at September 5, 2018 02:18 UTC
We had our weekly call with our mentors and coaches who laid down the next steps. Also worked on comparing performance of MSB and the new flag sort implementation trying to figure out what are the key parameters for optimisations.
September 04, 2018
Team Barcelona Duo (Exercism)  — at September 4, 2018 21:49 UTC
After an early morning coaching session on Ruby syntax, I created a new Rails blog , trying to recreate the process from memory. I started writing some tests and realized that I still do not know the correct syntax. Assessment: I can piece together the parts of the app, so I understand the general relationships, but I had an unacceptably high number of syntax errors.
In the afternoon I mapped what I had learned to the exercism codebase. Tomorrow I have a session with a coach to go over the parts I do not understand.
I had my first feed back session with Maikha, one of our coaches. I was nervous, but she quickly put me at ease. The hardest part for me was coming up with things she could improve on. She was more forthcoming. After listing my strengths she gave me feedback on things I should do more of: believe in myself more, seek out individual coaching sessions, and pair-programming with ThoughtWorkers. Tomorrow I will start.
After several weeks stuck in customs, our package from our mentor Katrina Owen arrived today. We are so in-love with our new gear we will probably spend the rest of the summer wearing it. Every. Single. Day. She also sent us stickers! What is it about stickers that make grown developers get in-touch with the kid within?
After two intense days at Full Stack Fest Amalia will be in tomorrow taking advantage of the conference day off to come to the office.
Team GirlsCode MK (Bahmni)  — at September 4, 2018 21:13 UTC
- met with coach Ivo (who is sick, but still met with us, took notes and researched our next story! <3 Ivo <3)
- I (Eva) have been excitedly refactoring code for the past couple of days, so it was very good to receive some feedback from coach Ivo on what is useful (and what is not)
- implemented the changes suggested by coach Ivo
- I hosted GirlsCode in the evening which was again a good mix of welcoming new students, recommending resources, motivating the veteran students and solving some coding issues (and installing some Ubuntu, of course)
GTH - it has been a long interesting day that has got me excited about our project with our new story and me studying well into early hours. Does anybody else program all hours when they are in flow?
Our mentor Ivo has given us less detail for this story as it is similar to a past story and it is just enough to make us struggle so that we again learn more. The story is to use a get api in a search form. As this is a separate form we will need to plan out reusable components, look into the rest api end point so it only returns persons that we have added from our input form and not all users, providers etc.
I have also been reading up on react router. Do we really need this whole library for a low resource app with only two pages? Playing with browser, switch and link. A good question for discussion with coaches on our slack channel.
Lots of meetings today that were reflective on what I have done so far, always good to stop and reflect . RGSoC meetup today talking about imposter syndrome and mindsets. Also one to one with supervisor Ramón.
- researching our current story including GET requests, React routing, adding more components
- using the SVGs provided by the team designer, Konrad
- watching (and rewatching) the Mosh tutorial on React
create a search form for our app
- meeting with coach Neil tomorrow
- meeting with coach Ivo on Thursday
I would really like to celebrate RGSoC as I think it is such a great experience and more people need to know. As I feel I have learnt so much and I have met so many lovely people. Would any body else like to celebrate with us? Maybe we can arrange a joint party - suggestions welcome
Team Akaringular (EBWiki)  — at September 4, 2018 19:54 UTC
Based on the review given to us by our mentor we were able update the following pull requests:
- Create a null object class for Cases that handles blank cases or cases that are not versioned. We had issues with
uninitialized constant NullObjects::Casewhich came to realize that it is because directories in the app folder are considered root directories and therefore cannot be used for name spacing as explained here
- Added migration for slug on State. We then used it to find States which is more friendly to a user instead of using id to find a state.
- Put versions controller in Case module.
- We have also opened three pull requests setting instance variables, we are waiting on our mentor to review them
- We also finished our pending pr that needed some additional information on adding content on how to create and update agency in ebwiki contribution guidelines
Team 101 Days of Summer (Servo)  — at September 4, 2018 19:22 UTC
We spent the day figuring out the reason of failure for the tests involving current pixel density. Finally we found out by talking to Emilio(on IRC, he is really helpful when Josh is not around :D ) that pixel density is not being taken into consideration currently. We were confused about in which file should all this be happening, but now we know.
So we will be implementing that part of the code today, to fix the failing tests in current-pixel-density.
Team $we init (Probot: build your own GitHub app(s))  — at September 4, 2018 18:22 UTC
- Made final commits to first-timers-only bot <3
- Discussed with coach Divjot on issues in PR on second bot
- The first bot is ready for a first release! Yay!
Team Rubies (if me - mental health communication app)  — at September 4, 2018 18:13 UTC
Tasks completed today
- Worked on 'Blocking from Admin dashboard'.
- Continued writing Tests. Faced many problems as we had changed the admin dashboard model.
Things we learnt
- Fix the problems in tests.
- Continue Blocking Feature.
It was nice talking to Anna and other RGSoC participants in the Meetup! :D
Team Popcorn (Nextcloud)  — at September 4, 2018 15:04 UTC
Today Arati was out of the office to compensate for time spent at the Nextcloud conference.
* I worked on my PR #618 for fixing issue #614 the popover menu. Close to a nice working solution 💪
* I also joined the remote call with the other members of RGSoC 📞
It was really nice to see and talk with Anna and some of the other RGSoC participants and share our experiences. I also got quite a bit of coding done today and managed to untangle in my mind how to work with the WebDav (still not completely but I understand it much better!) 🎉
Link(s) to work:
Team 101 Days of Summer (Servo)  — at September 4, 2018 10:50 UTC
Today we updated the previous PR. A large number of failing tests are passing now, it seems to be some progress. But still some of the tests are failing, and we need to look into those. We couldn't have our weekly call with Rakhi yesterday, so we'll have it today. We also need to add all the relevant mutations in the current PR to ensure all the tests are passing.
September 03, 2018
Team Barcelona Duo (Exercism)  — at September 3, 2018 21:36 UTC
Reflections on Learning
Amalia is at the Full Stack Fest this week. I am working on learning Ruby and the Rails framework.
Before this summer I had never coded in Ruby or used the Rails framework. Over the past few weeks I have spent a few hours on and off playing around with Ruby, but if progress can be measured by what I can do with Ruby or Rails, I have made little.
So over the weekend, I decided to take everything I have learned in the past decade of teaching and design a study plan that would take me to where I want to be. In particular, I wrote a series of mock lesson plans on Ruby and Rails. While I am far from a Ruby rock star, I finally have a clear idea of what are my particular weaknesses and how I can improve going forward.
Mapping teaching to learning
There are four basic steps that guide lesson planning and I will share them here in case they might be of use to others who are learning something new. This is how it works.
First, there is the sorting the material into the key points that you want to cover and divide them in a series of coherent lessons. A few of the key points of my lessons are routes, models, views, controllers, classes, instance variables and relevant gems and their helper functions are critical to understand how Rails structures its apps.
Second, each lesson is designed around a "heart". That is, for each lesson there should be one thing that you want the learners to be able to do after they complete the lesson. An outcome of a lesson on routes could be something as small as being able to decipher the output of ´bin/rails routes´.
Third, after deciding on the focus of each lesson, you identify what does a student need to know in order to understand your lesson and identifying what you need to 'pre-teach'. In teaching a grammar lesson, for example, you want to make sure the students know the vocabulary you are using, so they are not distracted from the lesson's key objective. Analogous, Rails apps are full of
<%= %>. While not fundamental to using Rails, encountering such syntax without understanding what it means increased my cognitive load and made it difficult to decipher the basics of routes and controllers.
Finally, each lesson is placed in a logical order (scaffolding, in teacher-speak), from simple to more difficult, where each parts builds on the previous one.
For my study plan, after every mini-lesson, I should know something and be able to do something new, whether it is identify the helper functions when reading the codebase or actually being able to write the code behind each one. As for what I needed to know before I could fully get the most out of a tutorial, I needed to know more Ruby and have some familiarity with the embedded Ruby syntax.
To remedy this I dedicated a part of the day learning Ruby syntax by mapping it onto Python, a language I am more comfortable with. For example, when I saw
for. It turns out, knowing
<%=is embedded Ruby syntax makes it easier to understand a Rails application.
The long term objective of learning Rails is to be able to fix bugs or create features for the Exercism platform. It has been just a few days of this new approach to studying, and yet I feel that I have made more progress towards that goal in this time than the previous two months of studying without a plan.
Team GirlsCode MK (Bahmni)  — at September 3, 2018 20:39 UTC
Met with supervisor Ramón online - he is also a good coach checking we are both ok and happy with our project. Eva explained the last two stories she has done with spinner and refactoring. We had a great conversation about testing and discipline. It was interesting to hear about other technologies and their community. For example Python is seen as having lots of documentation and Ruby has a great community of testers and feedback.
We then did a meeting about the overview for the next 30 days. It covered things that we had planned, obstacles, ideas of what we think is coming up for the application and what would we need to learn. We also set about a strategy for the upcoming blog post due on Sept 17th.
Eva filled me in as to what changes she had made on the app.
Georgina shared resources from conference in June Women of Silicon Roundabout. Lots of soft skill talks for women to help move into technical leadership roles.
More learning on what is clean code, consistent code, best practices and ways to refactor code to make it easier to understand and read by others.
We are both doing the codewithmosh course and we are working through this and applying what we are learning to our app. We actually felt that having a project to apply this to was so good in learning and helping to understand that is shows how much we have learnt in these two months with RGSoC.
ByteConf online videos
Continued to share resources with girls code MK community and our social media followers.
Write a template for the blog post that we can start to work on - some ideas to make it fun to read
Meet with mentor Ivo about the two stories that are currently showing on Jira but are not ready for development and are still being analysed.
We have set a date of 2nd November to do a presentation of our app to ThoughtWorks staff in London and will be streamed to Berlin. This is a lunch time session which we hope to;
* thank Ivo for his unfaltering patience, very clear and precise instructions
* encourage and inspire others to mentor with RGSoC for future teams as we have benefitted so much
* share specific details of the Bahmni project
Continue to use react router in a separate branch on github.
Team Akaringular (EBWiki)  — at September 3, 2018 20:32 UTC
About the Weekend
Coaching at Girls Get Geeky was great. We helped newbies build their first Rails app and did a scaffold on ideas. We also took them through the MVC architecture and how it works.
- Fixed a review requested on making factories dynamic
- Worked on making cases controller with modules, by having versions controller as one of its sub module. We also set the same on the routes to ensure that proper each route is matched to the correct controller and action.
- Looked at rules governing a rescue clause and how it works, rescuing exceptions. The pr on that was also merged today.
- Looked in deep how to do a 301 redirect if an old id was used to find a record, the code is great but the test are still not working, yet to find the reason behind that.
What we learnt
- Today we read on the law of the demeter which in short would be summarized as.."only use one dot". Very many chains in method calls are discouraged
Team Popcorn (Nextcloud)  — at September 3, 2018 19:44 UTC
- Jessica worked on the rename function in the popover menu for issue #600 and added a fix for issue #615 as per review.
- Agile Meeting without coaches.
- Arati worked on form validation with regex for issue 605 and design fixes.
Team Rubies (if me - mental health communication app)  — at September 3, 2018 18:22 UTC
Tasks completed today
- UI for Admin Dashboard done.
- Worked on implementing Notification badge for Admin Dashboard.
- Added mailto links for Reports.
- Continue working on Blocking Feature.
Team Sectumsempra (Chapel Parallel Programming Language)  — at September 3, 2018 17:24 UTC
Our work today:
Avneet: Tried out various ways to optimize the MSB performance. And read about different implementations from different blogs (https://probablydance.com/2016/12/27/i-wrote-a-faster-sorting-algorithm/).
Rupal: Worked on feedback and fixing installation issues.
Team $we init (Probot: build your own GitHub app(s))  — at September 3, 2018 17:11 UTC
It was Janamashtmi today! It's one of the biggest festivals in India on the birth of Lord Krishna. We enjoyed a lot and so could do little work. :/
We faced a few issues refactoring the code further away and are working on it. We have also started working on blogs for our bots starting with the first one. Our target for this week would be to get the PR merged for the second bot and finish the blog for the first one!
Team 101 Days of Summer (Servo)  — at September 3, 2018 12:34 UTC
One of our PR got merged, hooray! After so long finally.
We are now again working on the reacting to environment changes PR. After our current changes, some more unexpected tests have started failing due to the borrow errors and we need to correct them. Also our tests which were earlier passing are now failing and timing out due to some changes. We are again working on correcting those failing tests.
We'll also have our weekly call with Rakhi today. This is going to be an exciting week.
September 02, 2018
DV Team (LivingStyleGuide)  — at September 2, 2018 19:39 UTC
- Finsihed working on #16 & #45 -> waiting for review and merge
- Had a meeting with Nico, Tobi, Bogdan (new coach!)
- Sent welcome message to Bogdan with info about what we are doing
- Discussed what we are going to be working on next week
Team Rubies (if me - mental health communication app)  — at September 2, 2018 18:17 UTC
Tasks completed today
- Reimplementation of admin panel done!
- Discussed the workflow for Blocking feature.
- Improve UI for Admin Dashboard
- Continue working on Blocking Feature.
Team Sectumsempra (Chapel Parallel Programming Language)  — at September 2, 2018 15:02 UTC
Here's what we did.
Avneet: Finally was able to figure out the American flag sort and wrote an implementation for the same. Now the further step would be to compare it with the MSB version, while Rupal is trying to setup chapel as it stopped working on her laptop. She is using the guidance of coaches for the same.