Nobody pays for code: customers pay for outcomes
Software engineering’s version of the 3Blue1Brown three-column board
What engineers do
Writing code
like proving theorems
Framing problems
like asking questions
Designing systems
like theory building
Shipping and operating
like applying theory
Why software is valuable
Products and automation
work people use every day
Reliability and trust
correct and secure at scale
Systems-thinking muscles
decompose, abstract, debug
Joy of building
craft and elegance
Where the money comes from
Customers
paying for outcomes
Enterprise budgets
cutting cost and risk
Investors
betting on future revenue
Public and research
grants, defense, academia