Journeys: What makes a developer, really?
summary
Research from the Origins interview series claims there is no single path to being a developer and that CSS already functions as development. Concrete examples include a responsive design in four lines, a modular framework with JavaScript and Ruby dependencies, and CSS that can be tested and used to build games—these work and change hiring and pay. Recommended actions are to document and publish role hierarchies, make evaluation criteria explicit, and place minority voices in decision making.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:50the development identity crisis
- 6:45presentation
- 8:45titles matter
- 11:01different journeys different perspectives
- 11:25"legitimate" paths and "developer" archetypes
- 13:14why create hierarchies?
- 14:06identification matters
- 18:13consequences power dynamios & development legitimacy
- 19:20consequences salary variation
- 21:30acknowledgement
- 22:36honesty hyper-awareness and accountability: write down those hierarchies!
- 23:18managers: lead from the top transparency and openness is driven by those in charge
- 24:04challenge hierarchies hire CSS-focused developers, and put minorities in decision-making roles
- 24:47what shouldn't make a developer? why?
related talks
33mWhat it takes to become a great developer!
01h 03mFrontend Developers — They Are Everywhere
16mThe job of my dreams
46mThe Developer Journey
48mWho are you, JS developer?
21mWhat it’s like to be a Developer (and) Advocate?
13mGrowing Developers: Helping Junior Developers Improve & Succeed
27mThe myth of the “Real JavaScript Developer”