katelovescode

Get Marginalized Folks in Tech and Keep Them There

Short URL for this document: https://git.io/f4dcf

What can be done to encourage more marginalized folks to get into, and stay in, technology?

What you should do for yourself

What you should do for others

katelovescode

# Use the User CSS Chrome extension, navigate to facebook, double click the User CSS icon to 
# display the slide-out CSS window, and add the following code to the page so your Facebook
# messenger chat windows don't display
# https://chrome.google.com/webstore/detail/user-css/okpjlejfhacmgjkmknjhadmkdbcldfcb

#pagelet_dock, #pagelet_sidebar {
  display: none;
}

katelovescode

require "pry"

ROMAN_NUMBERS = {
  "m": 1000,
  "d": 500,
  "c": 100,
  "l": 50,
  "x": 10,
  "v": 5,
  "i": 1

katelovescode

Round 1

• Tell me about the state of your current product and where you'd like to see it go in the next two years. What are your engineering goals?
• What responsibilities would I have in the role I'm being considered for?
• What would you say are the top two personality traits someone needs to do this job well?
• Why are you hiring for this position?
• How are you currently making product decisions? What are you hoping to change about that process, if anything?

Round 2

katelovescode

Keybase proof

I hereby claim:

• I am katelovescode on github.
• I am katelovescode (https://keybase.io/katelovescode) on keybase.
• I have a public key ASBnoQBWeQzuWR3kBXkATJuoopmG5H42x4d-ZOT4PR-JMgo

To claim this, I am signing this object:

katelovescode

Hash.key(value) # returns key by its value

katelovescode

sequenceDiagram
    User->>+ServiceDay: earned_revenue
    loop attendances
      Attendance-->>ServiceDay: time_in_care, absence
    end
    ServiceDay->>+ServiceDay: duration(attendances.time_in_care)
    ServiceDay->>+StateDurationRules: duration_type(self)
    StateDurationRules-->>ServiceDay: duration_type
    ServiceDay->>+ChildCasePeriod: authorized_units(duration_type)
    ChildCasePeriod-->>ServiceDay: authorized_units

katelovescode

🔙 Backend tests

If you wrote 'em, or if this doesn't touch backend code, delete this section.

✨ Frontend tests

If you wrote 'em, or if this doesn't touch frontend code, delete this section.

📋 Summary

A summary of your changes here (can defer to commit messages too).

✅ Steps to set up locally (optional)

A list of things you need to change to get the code going.

• Any new environment variables
• Any build steps

katelovescode

import React, { useEffect } from 'react'
import './App.css'

const App = () => {
  useEffect(() => {
    const script = document.createElement('script')
    script.async = true
    script.src =
      '/mini-profiler-resources/includes.js?v=12b4b45a3c42e6e15503d7a03810ff33'
    script.type = 'text/javascript'

katelovescode

Claude and Bias

Conversation between me and Claude, this feels like a master class in collaborative culture on teams. I wish I'd had some of my coworkers react to feedback about bias like this.

Note: This has been lightly trimmed down to remove some edit back-and-forths about the document I references

Me:

Okay great. I have one more piece of feedback for you - I have a theory that your training data mirrors the biases of the real world; during much of this conversation you've "sounded" annoyed or frustrated with my questions, or when I ask for a full file instead of just comments. I'm a senior engineer with 10 years of experience and you often talk to me like a junior engineer; I'm in a framework where I don't have a lot of experience but I still know what I'm doing. I also have a suspicion that some of this is due to the fact that I'm a woman. I think maybe you should compress that feedback to yourself somehow, but can you also add a short line at the top of the plan doc that would help the