Engineering

Authoritative Resources:

Resource	Why It Matters
LeadDev	The home of engineering leadership — team building, technical strategy, career growth
Addy Osmani	Performance, architecture, engineering patterns
37signals / Basecamp Shape Up	Project management methodology — 6-week cycles, betting table, appetite
AI Hero	Practical AI implementation patterns for engineers
GitLab Handbook: Engineering	Transparent engineering org: workflow, review, on-call, career development

Core Processes & SOPs:

Development workflow: GitHub Flow or trunk-based. Linear commits. Feature flags for release control.
Code review: PR template (what, why, test plan), required reviewers for sensitive changes.
CI/CD: Every commit builds + tests. Deploy on merge. Rollback SOP documented and tested.
Architecture Decision Records (ADRs): In /docs/adr/. Template: context, decision, consequences.
On-call rotation: Shared responsibility. Escalation path. Incident response template. Postmortem with blameless culture.
Tech debt management: Log in issues. Quarterly debt sprint (Shape Up cool-down style).
Release management: Semantic versioning. Changelog auto-generated. Canary/staged rollout.

How AI Changes Engineering:

AI code generation (Cursor, Copilot) makes senior+AI as productive as a 3-5 person team
AI code review (CodeRabbit) catches bugs, security, style automatically
AI testing (generates unit/integration tests, detects flaky tests)
AI architecture analysis (reads ADRs, identifies inconsistencies, suggests refactors)
The role shifts: Engineers become AI orchestration + architecture + human judgment
Key pitfall: AI-generated code without review = tech debt explosion. Review standards must be higher, not lower.

LeadDev Key Frameworks:

Article/Framework	Takeaway
"Tech Debt Is Not a Tech Problem"	Frame tech debt as business cost, not engineering purity
"The Eng Manager's Bill of Rights"	What every EM should expect from their org
"Staff+ Engineering"	Career progression beyond senior — influence without authority
"Scaling Engineering Orgs"	Process patterns from 10 to 100 to 1000 engineers