This is the entry point into a whole thought process around how to build software, software teams, software businesses, etc. I intend on making this into some kind of guide with a catchy name at some point. ## Core Concepts - [[Engineering Must Have All The Inputs]] - [[Elon Musk's 5 Steps for Engineering]] - [[Elon Musk's 6 Rules for Tesla]] - ROI calculations require engineers - Only work on the most important things - You should be allergic to release gates - Requirements should be as vague as desired outcomes allow ([[Abstract Strategic Value]]) - Phase Zero is the new MVP ## Name Ideas Provided by ChatGPT (lol) - SyncDev: Synchronized Development - AlignFlow: Alignment-Focused Workflow - BridgeBuild: Bridging Business and Engineering - LeadTogether: Collaborative Leadership in Software - TeamSync: Team Synergy in Software Development - DevBizHarmony: Development and Business Harmony - UnitedCode: Uniting Engineering and Business - VisionForge: Forging Unified Visions in Software Development - GoalLink: Linking Goals for Business and Engineering Success - SynergizeIT: Synergizing Information Technology and Business Goals