Skip to content

Giving Thanks to Diversity in Tech: Faiza Yousuf

Giving Thanks for Diversity in Tech - 15 Part Series

Faiza

Despite already organizing her own massive tech community, Faiza is also the Pakistani chapter leader of CryptoChicks, through which she has hosted numerous hackathons. Faiza also regularly speaks at engagements both locally and internationally, having most recently delivered talks on Empathy in Business, and served on panels discussing the challenges that women face in the workplace.

“My team and I have been working tirelessly to create a better tech ecosystem locally and so far we have seen that the first step is to make people aware of their biases and to learn to distinctly see stereotypes and not let them cloud their judgement. Understanding our biases is the first step towards learning to value and appreciate all people.”

When asked about her perspective on inclusion in the tech industry, Faiza added that, “The next step is to have more role models for women, for people of color, for differently-abled people, for people from underprivileged or disadvantaged backgrounds.”

Even with her busy schedule, Faiza is an avid reader, and commits herself to reading one book every week! She encourages people, who would like to attend one of her local conferences, or international talks, to keep an eye on her Twitter page: @FaizaYousuf, where she will update you in the coming year!

This Dot Labs is a development consultancy that is trusted by top industry companies, including Stripe, Xero, Wikimedia, Docusign, and Twilio. This Dot takes a hands-on approach by providing tailored development strategies to help you approach your most pressing challenges with clarity and confidence. Whether it's bridging the gap between business and technology or modernizing legacy systems, you’ll find a breadth of experience and knowledge you need. Check out how This Dot Labs can empower your tech journey.

You might also like

The Open Source for All Initiative: Investing in Underrepresented Minorities in Tech -  How 2 Companies are Kicking Off 2020 with $20,000 cover image

The Open Source for All Initiative: Investing in Underrepresented Minorities in Tech - How 2 Companies are Kicking Off 2020 with $20,000

Here at This Dot Labs we are a development consultancy that is known for its work in providing opportunities to underrepresented minorities in tech. We are very excited to be partnering with StackBlitz, a company that is an online IDE used by millions of developers every month & adopted by open source projects such as Angular (Google), RxJS (Microsoft), and many others. We have teamed up this January to announce the Open Source for All Initiative to provide $20,000 of opportunities to those who need their first foot in the door. With only 50% of boot camp students able to find employment within 3 months of graduation (Dice), we both feel passionate about trying to help bridge the divide between graduating boot camp and someone's first development job. The $20,000 investment from StackBlitz and the supply of mentors (senior software engineers) from us will give paid apprenticeship opportunities for boot camp graduates to contribute to prominent open source projects. We have over 20 bootcamp partners including Fullstack Academy, Coding Dojo, Prime Academy, Vets Who Code and The Last Mile. “It’s tough to go from a bootcamp to an entry level developer role,” says Co-founder and CEO Tracy Lee, “and that challenge is compounded if you are a minority. Our apprentice program makes it easier for folks to transition to a full time job smoothly.” StackBlitz is already used by open source projects such as Angular (Google) and RxJS (Microsoft) in their documentation. "We have been very happy to work with the StackBlitz team and hosting the Angular documentation code samples on StackBlitz has been great for developers." said core team member Stephen Fluin. “StackBlitz has been a great partner at helping provide code samples in our documentation, and I admire Tracy's work with under-represented groups in tech,” says Ben Lesh of the RxJS core team, “The pairing for this initiative is great and I expect good things to come out of it.” Those interested in participating in the program as apprentices can apply here. If you’re an open source project who wishes to provide opportunities to underrepresented minorities and have great code examples in your documentation enhanced for free, sign up here. We can’t wait to work with everyone and make a difference in the tech world!...

Giving Thanks for Diversity in Tech: Angie Jones cover image

Giving Thanks for Diversity in Tech: Angie Jones

Angie Jones is a San Francisco-based Senior Developer Advocate at Applitools, as well as the Director of Test Automation University, a free, community-driven educational program that provides training to test automation teams. A Master Inventor, Angie currently holds 26 patents across both the United States as well as China, and has garnered a reputation as a leading innovator in the tech community through not only her work, but also her regular international speaking engagements. Angie has delivered talks on topics ranging from visual testing, to clean code, and even testing AI-enabled applications, having recently spoken on large international stages, including Selenium Conference in Chicago, STAREAST Testing Conference in Orlando, and Agile Testing Days in Potsdam, Germany, just to name a few. Not only a prolific speaker and creator, Angie also finds time to volunteer with Black Girls Code, an organization through which she hosts workshops for young women interested in getting into web development. Angie has a very busy 2020 on the horizon, with upcoming talks at JSConf Hawaii, Devnexus, TSQA, SauceCon, STPCon, RenderATL, and Agile Testing Days. We can’t wait to see what else she will accomplish in the new year! Want to keep up with everything Angie is doing in 2020? You can follow her at @techgirl1908!...

Announcing October JavaScript Marathon - Free, online training! cover image

Announcing October JavaScript Marathon - Free, online training!

Join us October 28th, 2020 for our next JavaScript Marathon!__ JavaScript Marathon is a full day of free, online courses on React, TypeScript, GraphQL, and more. Come learn about some of the leading web development technologies, and concepts! Stay for one training, or stick around for the whole day! No two sessions will be the same! --- React Hooks 201__ Featuring Kyle Hill @ 11:00am - 12:00pm EDT* It might have taken a little while, but: have you mastered the use of useState, and maybe even (mostly) understand what useEffect is doing at this point? Cool. Let’s level up our React Hooks skills further by diving into some of the other tools in our box. We’ll leverage useContext and useReducer to create an easy to implement interaction and data flow that scales along with your application and your team. --- Getting Started with Eleventy__ Featuring Kyle Mitofsky @ 12:30pm - 1:30pm EDT* Eleventy is a JavaScript based Static Site Generator (SSG) that's designed around performance, accessibility, and simplicity. Take your first steps to build out front end designs, websites, and content with this walk through that'll get you set up on your first eleventy site. Learn some of the basics with some patterns and best practices as well. --- TypeScript for Beginners__ Featuring Dacey Nolan @ 2:00pm - 3:00pm EDT* During this introduction to TypeScript, we will cover what TypeScript is, what benefits it provides, and how you can use it in your projects. Code with me or just follow along as we dive into each of the types and learn how to use them. --- Automating GraphQL Client Code Generation__ Featuring Kevin Wolf @ 3:30pm - 4:30pm EDT* In this talk, we will learn how to streamline Front End Development by generating type-safe GraphQL Operations for Apollo Client. --- Building GraphQL Resolvers__ Featuring Josh Oppenheim @ 5:00pm - 6:00pm EDT* Have you ever wanted to know how graphql resolvers work or why we use them? In this training we will talk about the philosophy behind resolvers and how they fit in the greater GraphQL flow. We will take a look at how the graphql-js library implements them and we will write some of our own. We will discuss some possible requests from consumers and write resolvers to accommodate the needs presented. --- Need private trainings for your company? If you would like to learn more about how you can leverage This Dot’s expertise to upskill your team, and reinvigorate your developers with new knowledge about the web’s leading development technologies, visit the trainings page....

I Broke My Hand So You Don't Have To (First-Hand Accessibility Insights) cover image

I Broke My Hand So You Don't Have To (First-Hand Accessibility Insights)

We take accessibility quite seriously here at This Dot because we know it's important. Still, throughout my career, I've seen many projects where accessibility was brushed aside for reasons like "our users don't really use keyboard shortcuts" or "we need to ship fast; we can add accessibility later." The truth is, that "later" often means "never." And it turns out, anyone could break their hand, like I did. I broke my dominant hand and spent four weeks in a cast, effectively rendering it useless and forcing me to work left-handed. I must thus apologize for the misleading title; this post should more accurately be dubbed "second-hand" accessibility insights. The Perspective of a Developer Firstly, it's not the end of the world. I adapted quickly to my temporary disability, which was, for the most part, a minor inconvenience. I had to type with one hand, obviously slower than my usual pace, but isn't a significant part of a software engineer's work focused on thinking? Here's what I did and learned: - I moved my mouse to the left and started using it with my left hand. I adapted quickly, but the experience wasn't as smooth as using my right hand. I could perform most tasks, but I needed to be more careful and precise. - Many actions require holding a key while pressing a mouse button (e.g., visiting links from the IDE), which is hard to do with one hand. - This led me to explore trackpad options. Apart from the Apple Magic Trackpad, choices were limited. As a Windows user (I know, sorry), that wasn't an option for me. I settled for a cheap trackpad from Amazon. A lot of tasks became easier; however, the trackpad eventually malfunctioned, sending me back to the mouse. - I don't know a lot of IDE shortcuts. I realized how much I've been relying on a mouse for my work, subconsciously refusing to learn new keyboard shortcuts (I'll be returning my senior engineer license shortly). So I learned a few new ones, which is good, I guess. - Some keyboard shortcuts are hard to press with one hand. If you find yourself in a similar situation, you may need to remap some of them. - Copilot became my best friend, saving me from a lot of slow typing, although I did have to correct and rewrite many of its suggestions. The Perspective of a User As a developer, I was able to get by and figure things out to be able to work effectively. As a user, however, I got to experience the other side of the coin and really feel the accessibility (or lack thereof) on the web. Here are a few insights I gained: - A lot of websites apparently tried_ to implement keyboard navigation, but failed miserably. For example, a big e-commerce website I tried to use to shop for the aforementioned trackpad seemed to work fine with keyboard navigation at first, but once I focused on the search field, I found myself unable to tab out from it. When you make the effort to implement keyboard navigation, please make sure it works properly and it doesn't get broken with new changes. I wholeheartedly recommend having e2e tests (e.g. with Playwright) that verify the keyboard navigation works as expected. - A few websites and web apps I tried to use were completely unusable with the keyboard and were designed to be used with a mouse only. - Some sites had elaborate keyboard navigation, with custom keyboard shortcuts for different functionality. That took some time to figure out, and I reckon it's not as intuitive as the designers thought it would be. Once a user learns the shortcuts, however, it could make their life easier, I suppose. - A lot of interactive elements are much smaller than they should be, making it hard to accurately click on them with your weaker hand. Designers, I beg you, please make your buttons bigger. I once worked on an application that had a "gloves mode" for environments where the operators would be using gloves, and I feel like maybe the size we went with for the "gloves mode" should be the standard everywhere, especially as screens get bigger and bigger. - Misclicking is easy, especially using your weaker hand. Be it a mouse click or just hitting an Enter key on accident. Kudos to all the developers who thought about this and implemented a confirmation dialog or other safety measures to prevent users from accidentally deleting or posting something. I've however encountered a few apps that didn't have any of these, and those made me a bit anxious, to be honest. If this is something you haven't thought about when developing an app, please start doing so, you might save someone a lot of trouble. Some Second-Hand Insights I was only a little bit impaired by being temporarily one-handed and it was honestly a big pain. In this post, I've focused on my anecdotal experience as a developer and a user, covering mostly keyboard navigation and mouse usage. I can only imagine how frustrating it must be for visually impaired users, or users with other disabilities, to use the web. I must confess I haven't always been treating accessibility as a priority, but I've certainly learned my lesson. I will try to make sure all the apps I work on are accessible and inclusive, and I will try to test not only the keyboard navigation, ARIA attributes, and other accessibility features, but also the overall experience of using the app with a screen reader. I hope this post will at least plant a little seed in your head that makes you think about what it feels like to be disabled and what would the experience of a disabled person be like using the app you're working on. Conclusion: The Humbling Realities of Accessibility The past few weeks have been an eye-opening journey for me into the world of accessibility, exposing its importance not just in theory but in palpable, daily experiences. My short-term impairment allowed me to peek into a life where simple tasks aren't so simple, and convenient shortcuts are a maze of complications. It has been a humbling experience, but also an illuminating one. As developers and designers, we often get caught in the rush to innovate and to ship, leaving behind essential elements that make technology inclusive and humane. While my temporary disability was an inconvenience, it's permanent for many others. A broken hand made me realize how broken our approach towards accessibility often is. The key takeaway here isn't just a list of accessibility tips; it's an earnest appeal to empathize with your end-users. "Designing for all" is not a checkbox to tick off before a product launch; it's an ongoing commitment to the understanding that everyone interacts with technology differently. When being empathetic and sincerely thinking about accessibility, you never know whose life you could be making easier. After all, disability isn't a special condition; it's a part of the human condition. And if you still think "Our users don't really use keyboard shortcuts" or "We can add accessibility later," remember that you're not just failing a compliance checklist, you're failing real people....