In early October 2026 I wrote a LinkedIn post about emerging software‑engineering philosophies. I noted that the field already embraces three well‑known approaches—test‑driven development, pair programming, and “move fast & break things”—and that we are now entering a new era with two additional, as‑yet‑unnamed philosophies.
- traditional_philosophies.count = 3
I plan to explore and define these two new philosophies in future posts, comparing them to the established ones and looking for real‑world case studies.
- Open questions:
- What are the two new software‑engineering philosophies?
- How do they integrate with test‑driven development, pair programming, and “move fast & break things”?
- What evidence supports adopting them?
- Will formal definitions or principles be published?
- new_philosophies.count = 2