Originally posted 11/16/16 by Rebecca Jackson.
Figuring out client priorities is a key part of application development. It’s not an easy task. Here at Radial we’ve developed a web application to help us do this better.
Our working name for the app we developed is the “Graphing Scopeulator.” We named it that because it allows us to graphically scope our projects collaboratively with clients.
Born Out Of Client Discovery
The Graphing Scopeulator was born out of a meeting I had with Kate Catlin, founder of WomenRising, an open source project that I regularly work on. I was planning several hack nights for the project, and I needed to know how to prioritize work on features that would move the effort forward. Just like I would do with any client, I invited Kate to the office to discuss her vision for WomenRising with me and another Radial developer, Marshall Smith.
Once we had captured a list of the features she wanted, Marshall started drawing a graph on the board. He asked Kate to rank each of the listed features by value. That became the graph’s vertical Y-axis. Then, we ranked the estimated time for us as developers to complete each item. That became the horizontal X-axis.
Originally posted 11/13/17 by Sepideh Miller.
A friend asked me about the best practices for encouraging newbie contributors to open source projects. I am not a person who runs any open source projects, but I am a person who has made low-level contributions to a number of projects. I contribute data to Open Street Map. I edit Wikipedia. I helped some people with their English language skills when they were putting in Google Summer of Code proposals for Zulip, a chat application that is somewhat like Slack. I also made a contribution to IgniteSpeak, some software used for Ignite Baltimore.
Create Helpful Documentation for New Contributors
Create some documentation on what new contributors should do.
A few years ago, I woke up and took a look at my work calendar. Back-to-back meetings from 10am to 5pm. Sigh. I rolled out of bed, checked to make sure neither of my kids were awake yet, and pulled my laptop out. Starting at the file that was open in Sublime, I quickly found a few lines of unused code to delete. Within fifteen minutes, I had opened three pull-requests, each deleting anywhere from 10–50 lines of unused code. Sigh.
When I met with my manager for our weekly 1:1 later that day, I mentioned what I had done. He gave me a look, and said—critically but kindly—“is that really the best use of your time?”
Do’s & Don’ts: For video conferencing does not a remote culture make.
. . .
Trade sitting in traffic for latte’s at your local posh cafe while organizing your backlog on Trello.☕️
Swap yucky uncomfortable pants for your favorite pajama bottoms while negotiating with clients via video.💃
Reject your cube and get a tan by the pool while chatting about the next release on Slack.👙
. . .
Originally posted 7/7/17 by Lily Chen on Medium.
Lessons from “The Effective Engineer” by Edmond Lau that I apply to my job daily
One of the opening lines of The Effective Engineer is
80% of the impact comes from 20% of the work.
One of the most important skills an engineer can learn is thus identifying high leverage activities
I love me a well-run meetup: when you show up to a room-full (or huge event space-full) of friendly people chatting away and making connections, sit down for 30-60 minutes of interesting, inspiring, and (hopefully!) educational content, and head home after more chatting, ready to apply what you’ve learned.
About our blog:
This blog (like Flock) was formed to amplify the voices of underrepresented technologists and help all of us fly higher together.