The document summarizes what the author learned in their first year as a full-time programmer. Some of the key lessons included that programmers are not necessarily the most important people on a tech team, and that qualities like collaboration, quality work, and avoiding "rockstar" behaviors are more important for success than being a highly skilled coder. The author advocates learning where one's strengths lie to best contribute, such as through documentation, code reviews, or testing. Asking for help from others and tracking one's own growth through blogging or public speaking are also recommended. Diversity, inclusion, and avoiding tokenism are important both for the team and for building products for diverse users.
5. They’re bad for business.
✖ Overconfident
✖ More likely to break
rules
✖ More productive, but
lower quality work
✖ Negative behavior is
infectious
Forget rockstar-ninja-10x coders1
What actually brings success?
★ Don’t go rogue
★ Slow and steady
★ Collaborative, not
competitive
@hilarysk
6. “... converting [a superstar worker] to an
average worker enhances performance to a
much greater extent than replacing an
average worker with a superstar worker.1
”
@hilarysk
9. Learn where you are
★ Who writes the clearest documentation?
★ Who leaves the best feedback on PRs?
★ Who finds the most bugs during testing?
@hilarysk
10.
11. Ways to contribute
★ Add to documentation
★ Pair on code reviews
★ Aid in researching potential frameworks or gems
★ Help with testing
@hilarysk
28. How to clear your head
★ Reframe your feelings5
★ Go for a walk7
★ Switch to paper8
★ Clean (or rearrange) your desk
★ Help someone else6
@hilarysk
29.
30. How to ask for help4
1. What are you trying to do?
2. What have you already tried?
3. What else might work that you haven’t tried?
4. How, exactly, can the other person help you?
@hilarysk
https://tinyurl.com/railsconf-ask-help
32. Track (and celebrate!) your growth
★ Keep a journal
★ Document successes on company or personal blog
★ Tutor or mentor
★ Speak at a local meetup
@hilarysk
40. Anything you think could be better with ...
★ Office culture or environment?
★ Development process?
★ Documentation?
★ Bonding activities?
★ Workspace arrangement?
★ Company swag?
@hilarysk
43. Don’t put up with bullshit.
★ 80,000 unfilled tech jobs through 2022 (U.S.)9
★ Work remotely
★ Every company is a tech company
★ Avoid tokenism, but use your advantages
@hilarysk
47. Citations
1. “Toxic Workers” (Harvard Business School)
2. “It’s Not You, It’s It: Voice Recognition Doesn’t Recognize Women” (Time)
3. “Amazon’s Face Recognition Disproportionately Matched Congressional Members
of Color With Mugshots” (The Root)
4. “A guide for junior devs: How to ask for help in 5 steps” (Ten Forward Consulting)
5. “How to Strategically Manage Frustration at Work” (Glassdoor)
6. “7 Science-Backed Methods To Get You Out Of Your Head” (Forbes)
7. “Give Your Ideas Some Legs: The Positive Effect of Walking on Creative Thinking”
(American Psychological Association)
8. “A Learning Secret: Don't Take Notes with a Laptop” (Scientific American)
9. “Study: U.S. Demand for Skilled Tech Workers Rises While Optimism for Finding
Talent Shrinks” (Consumer Technology Association)
@hilarysk