awesome-cto
A curated and opinionated list of resources for Chief Technology Officers, with the emphasis on startups
https://github.com/kuchin/awesome-cto
Last synced: 16 days ago
JSON representation
-
Architecture
- Microservices – Please, don’t
- GitHub CTO – Biggest architectural mistake was going full microservice
- The Death of Microservice Madness in 2018
- Shrinking microservices to functions
- Design patterns for microservices
- Serverless architecture
- Best Practices for Designing a Pragmatic RESTful API
- 10 Modern Software Over-Engineering Mistakes
- How I Write Tests
- Lambda Architecture
- The Single Most Important Internal Email in the History of Amazon
- Accentuate the negative: making the non-perfect decision. Technical decision making
- The Single Most Important Internal Email in the History of Amazon
- The Single Most Important Internal Email in the History of Amazon
- An introduction to distributed systems - Kyle Kingsbury *(aphyr, author of Jepsen)*
- Awesome Scalability
- Build Your Own X
- The Death of Microservice Madness in 2018
- Shrinking microservices to functions
- Serverless framework
- The Single Most Important Internal Email in the History of Amazon
- Accentuate the negative: making the non-perfect decision. Technical decision making
-
Books
-
Career growth
- Career Growth Frameworks in Software Engineering: A Review
- Software Engineers Growth framework
- The Reverse Interview: How To Choose Your Next Company
- Reverse Interviewing — How to interview a company as well as they interview you
- Software Engineering Ladders
- Awesome Engineering Ladders
- Reverse Interview Questions
-
CTO Position
- The Different CTO Roles - Werner Vogels *(Amazon CTO)*
- Is it required to be a developer to become a CTO?
- 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?
- #define CTO - Greg Brockman *(Stripe CTO)*
- How my role as CTO has changed as we've grown to 100 engineers
- Your first 90 days as CTO or VP Engineering - Will Larson
- How to spend your first 30 days in a new senior-level role
- The difference between a CTO and a VP Engineering
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- Evolution of my role as a founder CTO - year-4), [Year 5 Update](https://miguelcarranza.es/cto-year-5) - Miguel Carranza
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- Three Golden Rules to Finding a CTO
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
- How my role as CTO has changed as we've grown to 100 engineers
-
Data
- NoSQL Databases: a Survey and Decision Guidance
- Evolutionary Database Design
- Database Migrations Done Right
- A reference guide for fintech & small-data engineering
- Building a data team at a mid-stage startup: a short story
- DataOps
- Databases in 2022: A Year in Review
- Building a data science team
- Managing Data Science Teams
- How to Structure a Data Science Team
- Awesome Machine Learning
- Best resources of everyday ML learning
- Weapons of Math Destruction
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- NoSQL Databases: a Survey and Decision Guidance
- Awesome Production Machine Learning
- NoSQL Databases: a Survey and Decision Guidance
- Databases in 2022: A Year in Review
- Managing Data Science Teams
- How to Structure a Data Science Team
-
Development process
- Introduction to Scrum for Managers and Executives
- Writing User Stories, Examples and Templates In Agile Methodologies
- What are the fundamental principles of continuous integration?
- The Product Managers’ Guide to Continuous Delivery and DevOps
- Comparing Git workflows
- A successful Git branching model
- Trunk Based Development - tech-trunk-based-development))
- Why You Should Learn to Stop Worrying and Love Technical Debt
- It’s Time to Rethink Technical Debt Management
- How to Write a Postmortem
- Startup Lessons Learned - Five Whys - Eric Ries *(creator of the Lean Startup)*
- On Call Rotations: How Best to Wake Devs Up in the Middle of the Night
- Testing in Production, the safe way
Categories
Sub Categories
Keywords
awesome-list
13
awesome
11
programming
3
resources
3
lists
3
management
2
list
2
pricing
2
computer-science
2
interview
2
machine-learning
2
product-management
2
billing
2
internationalization
1
myths
1
network
1
design-patterns
1
phone-number
1
phone-numbers
1
postal-addresses
1
big-data
1
time
1
typography
1
backend
1
unicorns
1
architecture
1
algorithm
1
algorithms
1
coding-interview
1
coding-interviews
1
post-mortem
1
data-structures
1
interview-prep
1
interview-preparation
1
programming-interviews
1
software-engineering
1
study-plan
1
debugging
1
pm
1
product
1
security
1
accounting
1
business-intelligence
1
cloud
1
cost-forecast
1
cost-management
1
credit-card
1
data-engineering
1
finance
1
fraud
1