awesome-cto/README.md

Awesome CTO

— Hi, my name is Dima and I'm CTO

— (chorus) Hello, Dima

A curated and opinionated list of resources for Chief Technology Officers, with the emphasis on startups

Contents

• General
• Hiring
• Development process
• Architecture
• Technologies
• Startups
• Related stuff
• Marketing
• More links

General

• The Different CTO Roles - Werner Vogels (Amazon CTO)
• Is it required to be a developer to become a CTO? (Quora)
• Three Golden Rules to Finding a CTO
• Becoming a CTO
• VP Engineering vs CTO - Fred Wilson (Union Square Ventures)
• What makes for a successful CEO and CTO relationship in a startup? (Quora)
• #define CTO - Greg Brockman (Stripe CTO)

Hiring

• The Guerrilla Guide to Interviewing - Joel Spolsky (StackOverflow co-founder)
• The Joel Test: 12 Steps to Better Code - Joel Spolsky
• Why Can't Programmers.. Program? - Jeff Atwood (StackOverflow co-founder)
• We Hire the Best, Just Like Everyone Else - Jeff Atwood
• Engineering interview process at Stripe (Quora)
• Improving Our Engineering Interview Process (Foursquare)
• Hitting the High Notes - Joel Spolsky
• The mythical 10x programmer - Salvatore Sanfilippo (author of Redis)

Development process

• Scrum / Agile
  • Introduction to Scrum for Managers and Executives
  • Writing User Stories, Examples and Templates In Agile Methodologies
• CI / CD
  • What are the fundamental principles of continuous integration?
  • The Product Managers’ Guide to Continuous Delivery and DevOps
• Git
  • Comparing Git workflows
  • A successful Git branching model
• Planning
  • Evidence Based Scheduling - Joel Spolsky (StackOverflow co-founder)
  • [Book] The Mythical Man-Month
• Crisis
  • How to Write a Postmortem
  • List of Post-mortems (GitHub)
  • Startup Lessons Learned - Five Whys (Eric Ries, creator of the Lean Startup)

Architecture

• Twelve-Factor App
• Reactive Manifesto
• Microservices – Please, don’t (also: HackerNews discussion)
• NoSQL Databases: a Survey and Decision Guidance
• Best Practices for Designing a Pragmatic RESTful API
• 10 Modern Software Over-Engineering Mistakes
• How I Write Tests
• Lambda Architecture
• Evolutionary Database Design (Martin Fowler)

Technologies

• Algorithms
  • Big-O explained in plain English
• Javascript
  • SuperheroJS collection
  • JS: The Right Way
  • Frontend developer handbook 2017
• Machine Learning
  • Awesome Machine Learning (GitHub)
• Big scale
  • What is CAP Theorem? (Quora)
  • CAP Theorem: Revisited
• Security
  • SaaS CTO Security Checklist
• Cloud
  • Open Guide to Amazon Web Services
  • Amazon AWS in Plain English
  • Microsoft Azure in Plain English
  • Google Cloud Services for the AWS expert

Startups

• What are the things startups have to get right? (Quora)
• 85 Things I learned being a CEO
• What’s the Second Job of a Startup CEO?
• Things I will tell my kids if they become entrepreneurs
• What do VCs really look for when making investments? (Quora)
• What would a CTO equity be for a small startup? (Quora)
• As an employee of a startup, how do you know when to quit? (Quora)

Related stuff

• Knowledge-Sharing Architects As An Alternative to Coding Architects
• Ten Rules for Negotiating a Job Offer (also: HackerNews discussion)
• GitLab Team Handbook
• What are best practices of experienced programmers? (Quora)
• Falsehoods Programmers Believe About Names
• 2016 European Software Development Salary Survey (O'Reilly)
• Software Engineering at Google
• The Atlassian Team Playbook
• DevOps: Bringing development and operations together (Atlassian)

Marketing

• Developer Marketing Guide
• Top Resources for Startup Marketing and PR
• SaaS Email Marketing Handbook

More links

• Awesome Falsehood
• Engineering blogs
• Awesome Awesomeness (GitHub)
• Awesome.re (GitHub)
• Chief Technology Officer vs Coder Thinker Organizer (GitHub)
• Socal CTO

License