Advertisement
Guest User

Untitled

a guest
May 25th, 2016
59
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.93 KB | None | 0 0
  1. * Understands that people > software.
  2. * Able to take on any piece of the software stack and know where to begin.
  3. * Can self-manage and prioritize on projects without oversight and guidance.
  4. * Mastery of at least a few technologies, and at least familiar with the other options out there.
  5. * Is aware of what they don't know, and is honest with themselves and others about their knowledge.
  6. * Knows how to look for solutions on their own, and sticks with it when things get touch, but also knows when to ask for help.
  7. * Can be given hard (unknown-unknown) tasks to figure out on their own.
  8. * Doesn't stop when something "just works", keeps pushing until they comprehend the solution.
  9. * Actively seeks feedback and the opinions of others.
  10. * Able to speak with public officials & partners confidently about our topic areas.
  11. * Comfortable with leadership on projects and engagement with the community. Speaks up with ideas during discussions.
  12. * Is able to work with teams outside of the company - contributing to open source projects, committees, etc.
  13. * Actively helps more junior developers.
  14. * Understands how to delegate.
  15. * Shows a mastery of software development in all of its lifecycle: architecture, planning, testing, development, deployment, security, refactoring.
  16. * Understand the needs of the business as well as the technical needs - balancing deadlines, budgets, resources. Comfortable pushing back on unreasonable requirements.
  17. * Constantly seeking to expand their skillset and learn new things. Stays current on technology without prompting.
  18. * However, is *not* simply a trend follower. Conservative in technology choices. Stable, maintained solutions over trendy tech.
  19. * Knows how to pick the best off-the-shelf solution, and when it makes sense to write their own.
  20. * Is not beholden to tools, instead looks to methodology.
  21. * Approaches any problem from the 10,000 foot view, but able to see specific details clearly and plan for them.
  22. * Ships code regularly.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement