awesome-cto
A curated and opinionated list of resources for Chief Technology Officers, with the emphasis on startups
Top Related Projects
A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools and more.
😎 Awesome lists about all kinds of interesting topics
Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.
Interactive roadmaps, guides and other educational content to help developers grow in their careers.
🗂 The perfect Front-End Checklist for modern websites and meticulous developers
:books: Freely available programming books
Quick Overview
The "awesome-cto" repository is a curated list of resources for Chief Technology Officers (CTOs) and technical leaders. It provides a comprehensive collection of articles, tools, and best practices covering various aspects of technology leadership, including management, architecture, and strategic planning.
Pros
- Extensive collection of high-quality resources for CTOs and tech leaders
- Well-organized structure with clear categories for easy navigation
- Regularly updated with new and relevant content
- Community-driven project with contributions from experienced professionals
Cons
- May be overwhelming for new CTOs due to the large amount of information
- Some resources might become outdated over time
- Lacks a rating system or reviews for individual resources
- Limited focus on specific industries or company sizes
Note: As this is not a code library, the code example and quick start sections have been omitted.
Competitor Comparisons
A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools and more.
Pros of the-book-of-secret-knowledge
- Broader scope, covering various IT topics beyond CTOs' responsibilities
- More detailed technical information and tools for hands-on professionals
- Regularly updated with community contributions
Cons of the-book-of-secret-knowledge
- Less focused on leadership and management aspects
- May be overwhelming for those seeking specific CTO-related information
- Lacks structured categorization for easy navigation
Code comparison
While both repositories primarily consist of curated lists and don't contain significant code samples, here's a comparison of their README structures:
the-book-of-secret-knowledge:
<p align="center">
<img src="https://github.com/trimstray/the-book-of-secret-knowledge/blob/master/static/img/the-book-of-secret-knowledge-preview.png">
</p>
<h4 align="center">A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools and more.</h4>
awesome-cto:
# Awesome CTO [](https://awesome.re)
A curated and opinionated list of resources for Chief Technology Officers, with the emphasis on startups
## Contents
- [1. General](#1-general)
The-book-of-secret-knowledge uses more visual elements and HTML formatting, while awesome-cto follows a simpler Markdown structure with clear categorization.
😎 Awesome lists about all kinds of interesting topics
Pros of awesome
- Much broader scope, covering a wide range of topics and technologies
- Significantly larger community with more contributors and stars
- More frequently updated with new content and resources
Cons of awesome
- Less focused, making it harder to find specific information for CTOs
- May include outdated or less relevant links due to its vast size
- Requires more time to navigate and find relevant resources
Code comparison
Not applicable for these repositories as they are curated lists of resources without significant code content.
Key differences
awesome-cto:
- Specifically tailored for Chief Technology Officers
- Organized around key CTO responsibilities and challenges
- Includes resources on leadership, management, and technical strategy
awesome:
- Covers a vast array of topics beyond just technology leadership
- Includes sub-lists for specific programming languages, tools, and platforms
- Serves as a starting point for discovering resources on almost any tech-related topic
Use cases
awesome-cto:
- Ideal for aspiring or current CTOs looking for targeted resources
- Useful for technical leaders seeking guidance on specific aspects of their role
- Provides a curated list of high-quality resources specific to technology leadership
awesome:
- Excellent for developers and technologists exploring new areas of interest
- Useful for finding resources on a wide range of programming languages and tools
- Serves as a comprehensive directory of curated lists for various tech topics
Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.
Pros of system-design-primer
- Provides in-depth explanations and visual aids for system design concepts
- Includes practical examples and case studies of real-world systems
- Offers a structured learning path for system design interviews
Cons of system-design-primer
- Focuses primarily on technical aspects, lacking broader business context
- May not cover the full range of skills required for a CTO role
- Less frequently updated compared to awesome-cto
Code comparison
While both repositories are primarily resource collections, system-design-primer includes some code examples:
# system-design-primer example: URL shortener
def encode(num):
chars = '0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz'
base = len(chars)
encoding = ''
while num > 0:
encoding = chars[num % base] + encoding
num //= base
return encoding
awesome-cto doesn't typically include code snippets, as it's a curated list of resources.
Summary
system-design-primer is an excellent resource for technical system design knowledge, particularly useful for engineers preparing for interviews or looking to improve their system architecture skills. awesome-cto, on the other hand, provides a broader range of resources covering various aspects of the CTO role, including leadership, management, and business strategy. The choice between the two depends on the specific needs and goals of the user.
Interactive roadmaps, guides and other educational content to help developers grow in their careers.
Pros of developer-roadmap
- Provides visual roadmaps for various tech roles, making it easier for developers to plan their learning journey
- Regularly updated with new technologies and industry trends
- Offers interactive versions of roadmaps on the project's website
Cons of developer-roadmap
- Focuses primarily on technical skills and career paths, lacking management and leadership aspects
- May overwhelm beginners with the sheer amount of information presented
- Less emphasis on soft skills and business aspects of technology roles
Code comparison
Not applicable for these repositories, as they primarily contain curated lists and resources rather than code samples.
Additional notes
developer-roadmap is more suited for individual developers looking to advance their technical skills and career paths. It provides comprehensive visual guides for various tech roles and technologies.
awesome-cto, on the other hand, is tailored for those in or aspiring to leadership positions in technology. It offers resources on management, leadership, and business aspects of being a CTO.
Both repositories serve different purposes and target audiences, making them complementary rather than directly comparable. developers-roadmap is ideal for technical skill development, while awesome-cto is better for those seeking to enhance their leadership and management capabilities in the tech industry.
🗂 The perfect Front-End Checklist for modern websites and meticulous developers
Pros of Front-End-Checklist
- Highly focused on front-end development best practices
- Provides a comprehensive checklist for web projects
- Includes practical tips and resources for each checklist item
Cons of Front-End-Checklist
- Limited scope compared to the broader CTO-focused content
- May not cover higher-level management and strategic aspects
- Less emphasis on team leadership and organizational structure
Code Comparison
While both repositories primarily contain curated lists and resources rather than code, Front-End-Checklist does include some HTML examples for best practices:
Front-End-Checklist:
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta charset="utf-8">
Awesome-cto doesn't typically include code snippets, focusing instead on high-level concepts and resources for CTOs.
Summary
Front-End-Checklist is a specialized resource for front-end developers, offering detailed guidelines for web projects. Awesome-cto, on the other hand, provides a broader range of resources for technical leaders, covering topics like management, hiring, and strategy. While Front-End-Checklist excels in its specific domain, it may not be as comprehensive for those in leadership roles seeking guidance on a wider range of responsibilities.
:books: Freely available programming books
Pros of free-programming-books
- Extensive collection of free programming resources across various languages and topics
- Regularly updated with community contributions
- Well-organized structure, making it easy to find specific resources
Cons of free-programming-books
- Focuses solely on educational materials, lacking practical guidance for CTOs
- May overwhelm beginners with the sheer volume of resources
- Limited curation, potentially including outdated or lower-quality materials
Code comparison
Not applicable, as both repositories are primarily curated lists without significant code content.
Summary
free-programming-books is an extensive collection of free programming resources, ideal for developers at all levels seeking learning materials. It covers a wide range of topics and languages but lacks the specific focus on CTO-related skills and responsibilities found in awesome-cto.
awesome-cto, on the other hand, provides a curated list of resources specifically tailored for CTOs and technical leaders. It offers practical guidance on leadership, management, and technical decision-making, which is not the focus of free-programming-books.
While free-programming-books is an excellent resource for individual learning and skill development, awesome-cto is more suitable for those in or aspiring to technical leadership roles, offering targeted information on the challenges and responsibilities unique to CTOs.
Convert
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
Awesome CTO
— Hello, my name is Dima and I'm a CTO
— (chorus) Welcome, Dima
A curated and opinionated list of resources for Chief Technology Officers and VP R&D, with the emphasis on startups and hyper-growth companies.
Contents
- CTO Position
- Hiring
- People management
- Career growth
- Project management
- Handbooks
- Development process
- Architecture
- Technologies
- Data
- Startups
- Due Diligence
- Money / Finance
- Related stuff
- Product
- Marketing
- Books
- More links
CTO Position
- 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)
- 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
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
- Getting the Interview Phone Screen Right - Jeff Atwood
- Engineering interview process at Stripe (Quora)
- Improving Our Engineering Interview Process (Foursquare)
- Hitting the High Notes - Joel Spolsky
- Top 10 System Design Interview Questions - (HackerNoon)
- How To Hire World-Class Engineers (angel.co)
- Trouble hiring senior engineers? It's probably you
- The Real 11 Reasons I Don't Hire You - Charity Majors
- How to Interview at Amazon
- Lessons from Keith Rabois: How to Interview an Executive
- Lessons from Keith Rabois: How to Become a Magnet for Talent
- GitLab Talent Acquisition Framework
- Visualizing Tech Company Layoffs in 2022
People Management
- The mythical 10x programmer - Salvatore Sanfilippo (author of Redis)
- The Engineer/Manager Pendulum - Charity Majors
- Maker's Schedule, Manager's Schedule - Paul Graham (Y Combinator)
- Software Engineering at Google
- Google re:Work
- 44 Engineering Management Lessons (correct link to non-violent communication for lesson 34)
- The Secret To Discussing Pay With Employees
- Awesome Leading and Managing (Github)
- Progressing from tech to leadership
- A Review Process - Cap Watkins
- 12 manager readmes from top tech companies
- Predictable Delivery
- How people rise up to EVP level in big organizations (Quora)
- Should I Become a Manager? - Cap Watkins
- How to fail as a new engineering manager
- Design Patterns for Managing Up
- A Tactical Guide to Managing Up
- Engineering Management (Github)
- On-boarding Software Engineers
- Hold Your Team Accountable
- The Manager FAQ
- The Power of Performance Reviews
- Performance reviews are coming up - Gergely Orosz
- Principles of Engineering Management
- Compensation Best Practices
- Draw The Owl and Other Company Values You Didnât Know You Should Have
- A MANAGERâS BILL OF RESPONSIBILITIES (AND RIGHTS)
- After Being A Manager, Can I Be Happy As A Cog?
- Increment: Teams
- Hacking team communications
- How to build a startup engineering team
- Hug your manager
- Lessons from Keith Rabois: How to be an Effective Executive
- How Context Switching Sabotages Your Productivity
- 10,000 Hours with Reid Hoffman: What I Learned
- 7 Ways to Set Up a New Hire for Success
- How to get promoted
- Individuals matter
- Mandate Levels
- 10 ideas for building great culture in a distributed (remote) team
- Adapting to Endure / Crisis management - Sequoia
- Mochary Method Curriculum - Matt Mochary
- Meetings for an effective eng organization - Will Larson
- The One Key to Dealing with Senior Executives: Answer the Question!
- Step by step guide to building high performing teams
- Cycle times - Andrew Bosworth
Career growth
- Career Growth Frameworks in Software Engineering: A Review
- Software Engineers Growth framework
- Software Engineering Ladders (GitHub)
- Awesome Engineering Ladders (GitHub)
- Reverse Interview
Project management
- Evidence Based Scheduling - Joel Spolsky (StackOverflow co-founder)
- How Big Tech Runs Tech Projects and the Curious Absence of Scrum - Gergely Orosz
- The Secret to a Great Planning Process â Lessons from Airbnb and Eventbrite
- What TPMs Do and What Software Engineers Can Learn From Them - Gergely Orosz
- How to Scope a New Feature
- Measuring an engineering organization - Will Larson
Handbooks
- The Atlassian Team Playbook
- Valve Employee Handbook
- Basecamp Employee Handbook
- GitLab Team Handbook
- How HashiCorp Works
Development process
- Scrum / Agile
- CI / CD
- Git
- Comparing Git workflows
- A successful Git branching model
- Alternative: Trunk Based Development (focused on DevOps and CI/CD)
- Tech debt
- Crisis
- How to Write a Postmortem
- List of Post-mortems (GitHub)
- 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
- Error handling
Architecture
- Twelve-Factor App
- Reactive Manifesto
- An introduction to distributed systems - Kyle Kingsbury (aphyr, author of Jepsen)
- Microservices â Please, donât (also: HackerNews discussion)
- GitHub CTO â Biggest architectural mistake was going full microservice (also: HackerNews discussion)
- The Death of Microservice Madness in 2018
- Shrinking microservices to functions
- Design patterns for microservices
- Serverless architecture (Quora)
- Best Practices for Designing a Pragmatic RESTful API
- 10 Modern Software Over-Engineering Mistakes
- How I Write Tests
- Lambda Architecture
- Awesome Scalability (GitHub)
- The Single Most Important Internal Email in the History of Amazon
- Build Your Own X (GitHub)
- Accentuate the negative: making the non-perfect decision. Technical decision making
Technologies
- General
- Developer Roadmaps (GitHub)
- Coding Interview University (GitHub)
- Big-O explained in plain English
- Javascript
- Big scale
- Security
- Search
- Open Guide to Search Engineering (GitHub)
- Cloud
- Pricing
- Awesome Billing (GitHub)
- Awesome PriceOps (GitHub)
Data
- NoSQL Databases: a Survey and Decision Guidance
- Evolutionary Database Design (Martin Fowler)
- 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
- Data Science
- Machine Learning
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)
- As an employee of a startup, how do you know when to quit? (Quora)
- Pitch deck collection from VC funded startups
- YCâs Series A Diligence Checklist
- Startup Playbook - Sam Altman
- Y Combinator Startup Class
- Lean Canvas + Miro template
- Open Source Pitch Deck Templates for Figma
- List of startups that had successful pivots (GitHub)
Due Diligence
- Technology Due Diligence Checklist
- Technical Due Diligence Questions (GitHub)
- IT Department Tech Due Diligence Checklist
- A Guide to Surviving Tech Due Diligence
Money / Finance
- Startups
- IPOs and Beyond: A Guide to Exit Options for Companies
- What would a CTO equity be for a small startup? (Quora)
- Options vs Cash
- How To Invest In Startups - Sam Altman
- A Guide to Seed Fundraising
- Startup Economics equity calculator
- Option grants at seed
- Joining the new startup, with a handsome stock option allocation - Gergely Orosz
- Equity 101 for Software Engineers at Big Tech and Startups - Gergely Orosz
- Big companies
Related stuff
- Knowledge-Sharing Architects As An Alternative to Coding Architects
- Ten Rules for Negotiating a Job Offer (also: HackerNews discussion)
- Salary Negotiation: Make More Money, Be More Valued
- What are best practices of experienced programmers? (Quora)
- Falsehoods Programmers Believe About Names
- 2016 European Software Development Salary Survey (O'Reilly)
- DevOps: Bringing development and operations together (Atlassian)
- How to Prepare a Talk
- Undervalued Software Engineering Skills: Writing Well - Gergely Orosz
- The Pyramid Principle
- Senior Engineerâs Checklist
- How to Use OpenAPI and Swagger for Documentation
Product
- What Makes a Great Product Manager
- If You Donât Think You Need a VP of Product...
- Red Oceans: How to Find Profitable Startup Ideas
- Product North Star Metric
- What distinguishes the Top 1% of product managers from the Top 10%? - (Quora)
- How to Hire a Product Manager
- The Secrets Of Creative Thinking
- StellarPeers - Product Management Interviews
- Product vs. Feature Teams
- Most Startups Should Be Deer Hunters
- Shape Up: Stop Running in Circles and Ship Work that Matters
- How to Write Your First Strategic Roadmap
- Execution at Facebook
- 8 Product Hurdles Every Founder Must Clear
- The Top 10 Deliverables of Product Managers
- Product Manager Career Ladders - Lenny Rachitsky
- Awesome Product Management (GitHub)
- Awesome Product Manager (GitHub)
Marketing
- Developer Marketing Guide
- Top Resources for Startup Marketing and PR
- SaaS Email Marketing Handbook
- How today's fastest growing B2B businesses found their first ten customers
Books
More links
- Awesome Falsehood (GitHub)
- Engineering blogs (GitHub)
- Awesome Awesomeness (GitHub)
- Awesome.re (GitHub)
- Chief Technology Officer vs Coder Thinker Organizer (GitHub)
- Senior Software Engineer
- Socal CTO
- Curated list of CTO resources (GitHub)
- Awesome CTO Resources (GitHub)
- Free Tools for Developers
- NfX - The Founder Library
- foundr - Advices from founders
- The Leadership Library for Engineers
- Rands Leadership Slack
- Engineering Managers Slack
Other
- Awesome CEO (GitHub)
- Awesome TPM (GitHub)
License
Top Related Projects
A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools and more.
😎 Awesome lists about all kinds of interesting topics
Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.
Interactive roadmaps, guides and other educational content to help developers grow in their careers.
🗂 The perfect Front-End Checklist for modern websites and meticulous developers
:books: Freely available programming books
Convert
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot