Refactor Maker Entries for Full-Stack Applicability
Closed this issue · 3 comments
Many titles within the Maker ladder include language that has the potential of being biased towards backend engineers (see: Write scalable, performant code that leverages asynchrony, caching, database indexes, prefetching & sideloading, etc. in Engineer II entry, for example).
Given the authorship of these entries so far, we have some unintentional bias here and we want to make sure that any engineer can review any entry, coming away with value and feeling empowered.
I would like to see a PR here that aims to:
-
remove technical language within the main bullet points (NOTE: Example can include are a reasonable place to get detailed, however, for all parts of the stack! 🎉 )
-
refactor stack-biased language in the main bullet points to get at the heart of the cross-stack applicability, ex.
Write code that leverages language-specific optimizations, or framework best-practicecould be one way to refactor the problematic example above) -
provide new entries in the
Example Behaviorssection so that all engineers have an opportunity to relate to real-world examples
I would ask for the assistance of the team in helping to engage with this ask, relying on our collective experience to ensure this repo continues to evolve to better reflect our own diversity of technical backgrounds/domains.
An empty branch has been created (update-maker-entries-for-more-cross-stack-representation), as well as a PR to be filled out on completion here: #16
Aiming to get the 🏀 rollin' and get the 🧠 juices flowin', the list below is not a comprehensive list and anyone feeling like they'd like to tag somebody to get involved please don't hesitate to do so!
Should someone like to own coordinating - I'll offer this as an example of a process which is working reasonably well: #11
On a related note - perhaps a similar exercise from our Mobile colleagues might be warranted: