WW<CODE> Maker Bytes

#development #apps #features #design #ui/ux

written by

Issue 55

We are working to build great features for the Women Who Code community and we want to highlight that work with our stakeholders, you! THANK YOU to our contributors for dedicating their free time to help us build tech a place where women can excel.

You can follow all of our work on github. Below are a few snippets of our awesome features.


This week we've been working on a number of initiatives to make our products even better. With the job board we've developed the ability to associate a post with a customer ID giving posts ownership, we improved the way the system interacts with Stripe to make it even more secure, we improved communications by implementing a task to notify customers when they have to schedule a post, and they fixed a minor error in the invoicing system.

On the rest of the site the team made some information changes to the About page, changed some of the actions that can be performed by Admins on the back end, and created a tell us how you found us page that pops up whenever a new user logs in and which will help us to track usage and community data better. We also set up a rake task to check the site and update Network statistics such as number of members, leaders, and past events on a regular basis.

Now we have a CONTRIBUTING to more accurately communicate our guidelines and workflow.

pulse 2-6-17

Our Website

Our repo is private, yet running under an open source license. Instead of pointing to issues and PRs, we are including a screenshot of what our weekly pulse looks like.

Existing website contributors, please check out our pulse!

Potential website contributors, please email core-team@womenwhocode.com with your github username to get started. It's built in Ruby on Rails + React + Postgresql.

In The Works

Continuing to improve the stability and function of our platform so that we can do amazing things throughout the year.

Technical Pro Tip

By Sarah Masud of WWCode Delhi

While setting up a multi cluster Hadoop network (on 2 or more distinct systems), all system should have a Hadoop user with same user name, and the Hadoop folder in /usr/local for each user should also have the same name. This is because while connecting with nodes in the cluster, the master first matches the user name, and then the file permission. If the naming conventions are not followed, then Hadoop return a File Access Permission Exception.

sarah masud

Talk to us

Any ideas about existing features, new features, getting involved as a contributor, please share it in this FORM and/or watch our repos on Github.

To submit feedback, comments or questions email core-team@womenwhocode.com, we would love to hear from you.

My first #DockerCon

I was beyond excited when I...


How recruiters can help close the gender gap within the tech arena

As the wave of digital transformation...


WW<CODE> Maker Bytes

Issue 147We are building features for the...


Welcome to Women Who Code