-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add DEI in Tech portfolio page with header and references
- Loading branch information
1 parent
65c2790
commit b74953e
Showing
1 changed file
with
129 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,129 @@ | ||
| <!DOCTYPE html> | ||
| <html lang="en"> | ||
| <head> | ||
| <meta charset="UTF-8"> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
| <title>DEI in Tech: Real Challenges and Solutions</title> | ||
| <style> | ||
| body { | ||
| font-family: Arial, sans-serif; | ||
| line-height: 1.6; | ||
| margin: 0; | ||
| padding: 0; | ||
| background-color: #f9f9f9; | ||
| } | ||
|
|
||
| header { | ||
| background: url('header-image.jpg') no-repeat center center/cover; | ||
| color: #fff; | ||
| height: 300px; | ||
| display: flex; | ||
| justify-content: center; | ||
| align-items: center; | ||
| text-align: center; | ||
| } | ||
|
|
||
| header h1 { | ||
| font-size: 2.5rem; | ||
| margin: 0; | ||
| } | ||
|
|
||
| main { | ||
| padding: 20px; | ||
| } | ||
|
|
||
| section { | ||
| margin-bottom: 40px; | ||
| background: #fff; | ||
| padding: 20px; | ||
| border-radius: 8px; | ||
| box-shadow: 0 2px 4px rgba(0, 0, 0, 0.1); | ||
| } | ||
|
|
||
| h2 { | ||
| color: #333; | ||
| font-size: 1.8rem; | ||
| } | ||
|
|
||
| p { | ||
| color: #555; | ||
| } | ||
|
|
||
| ul { | ||
| margin-left: 20px; | ||
| } | ||
|
|
||
| .references { | ||
| font-size: 0.9rem; | ||
| color: #333; | ||
| } | ||
|
|
||
| .references a { | ||
| color: #007acc; | ||
| text-decoration: none; | ||
| } | ||
|
|
||
| .references a:hover { | ||
| text-decoration: underline; | ||
| } | ||
| </style> | ||
| </head> | ||
| <body> | ||
| <header> | ||
| <h1>DEI in Tech: Real Challenges and Solutions</h1> | ||
| </header> | ||
| <main> | ||
| <section> | ||
| <h2>The Technical Side: Where Imposter Syndrome Meets Code</h2> | ||
| <p>Think about your first day at a tech job. Now imagine facing that with documentation that might as well be written in ancient Greek, while a voice in your head keeps whispering, "Everyone else probably gets this." This is what many women and LGBTQ+ folks deal with in tech – not just technical barriers, but the crushing weight of imposter syndrome that makes those barriers feel ten times higher.</p> | ||
| <p>Research has shown that software developers constantly seek information to further their work, but when that information resides in someone else's head (such as why certain decisions were made), it becomes slow or impossible to retrieve (Ko et al., 2007).</p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h2>The Culture Problem: Why People Leave</h2> | ||
| <p>Here's the hard truth: tech has a culture problem. Modern work environments are still dominated by men, who may speak loudly, out of turn, and disrespectfully, sometimes even engaging in sexual harassment (Wang, 2016). As Ko (2023) points out, "Computer science as a discipline, and the software industry that it shapes, has only just begun to consider the urgent need for cultural competence."</p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h2>Bridging the Gap: What Actually Works</h2> | ||
| <p>Effective communication requires empathy and teamwork. When communication is poor, teams become disconnected and produce software defects (Bettenburg & Hassan, 2013). The solution involves creating inclusive environments where cross-disciplinary collaborations can thrive, requiring open-mindedness about others' input and seeing the broader picture of how different perspectives fit together (Li et al., 2017).</p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h2>The Power of Codes of Conduct</h2> | ||
| <p>Enforced codes of conduct matter significantly. The Contributor Covenant has become the de facto standard for open source communities, but as it states: "Simply adopting [the] Contributor Covenant will not prevent conflict or toxicity in your community." Enforcement is key (Riggins, 2021).</p> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h2>Practical Solutions That Make a Difference</h2> | ||
| <ul> | ||
| <li><strong>Structured mentoring programs</strong> matching newcomers with experienced professionals.</li> | ||
| <li><strong>Documentation that avoids assuming prior knowledge</strong> and supports diverse learning styles.</li> | ||
| <li><strong>Regular check-ins and support networks</strong> to ensure that employees feel heard and valued.</li> | ||
| <li><strong>Anonymous feedback channels</strong> to address concerns without fear of retaliation.</li> | ||
| <li><strong>Enforced codes of conduct</strong> with real consequences for violations.</li> | ||
| <li><strong>DEI training</strong> that goes beyond awareness to foster actionable change.</li> | ||
| <li><strong>Active sponsorship programs</strong> to promote underrepresented groups into leadership roles.</li> | ||
| </ul> | ||
| </section> | ||
|
|
||
| <section> | ||
| <h2>Conclusion</h2> | ||
| <p>The tech industry has serious work to do on DEI. We face structural issues, technical barriers exacerbated by imposter syndrome, and cultural obstacles driving people away. But increasing inclusivity in tech isn't just the right thing to do—it's the smart thing to do. As research shows, diverse teams lead to better innovation (Riggins, 2021), and isn't that what technology is supposed to be about?</p> | ||
| </section> | ||
|
|
||
| <section class="references"> | ||
| <h2>References</h2> | ||
| <ul> | ||
| <li>Bettenburg, N., & Hassan, A. E. (2013). Studying the impact of social interactions on software quality. <em>Empirical Software Engineering, 18</em>(2), 375-431.</li> | ||
| <li>Ko, A. J. (2023). Chapter 3: Communication. In <em>Software Engineering: The Expert's Way</em>.</li> | ||
| <li>Ko, A. J., DeLine, R., & Venolia, G. (2007). Information needs in collocated software development teams. <em>ACM/IEEE International Conference on Software Engineering</em>, 344-353.</li> | ||
| <li>Li, P. L., Ko, A. J., & Begel, A. (2017). Cross-disciplinary perspectives on collaborations with software engineers. <em>International Workshop on Cooperative and Human Aspects of Software Engineering</em>, 2-8.</li> | ||
| <li>Riggins, J. (2021, November 30). WTF is Wrong with Open Source Communities? <em>Container Solutions Blog.</em> <a href="https://container-solutions.com/wtf-is-wrong-with-open-source-communities/">https://container-solutions.com/wtf-is-wrong-with-open-source-communities/</a></li> | ||
| <li>Wang, J. (2016). Female pursuit of Computer Science with Jennifer Wang. <em>Software Engineering Daily Podcast</em>.</li> | ||
| <li>Washington, A. N. (2020). When twice as good isn't enough: the case for cultural competence in computing. <em>ACM Technical Symposium on Computer Science Education</em>, 213-219.</li> | ||
| </ul> | ||
| </section> | ||
| </main> | ||
| </body> | ||
| </html> |