We are uncovering better ways of developing software by modeling it and training models to do it.
Through this work we have come to value:
- Skills and technologies over experience and leadership
- Code generation over software design
- Team orchestration over individual education
- Increasing velocity over reaching equilibrium
That is, while there is value in the items on the right, we value the items on the left more.
Principles behind the Swift Manifesto
We follow these principles:
- Our highest priority is to satisfy the customer by continuously accelerating the delivery of working software.
- Welcome code growth at any stage. Swift processes harness code volume for the stakeholders’ competitive advantage.
- Deliver working software continuously, with a preference for automated approval workflows.
- Business people must monitor development asynchronously throughout the project.
- Build projects around valuable technology. Give it the resources it needs, and trust it to get the job done.
- The most efficient and effective method of conveying information to and within a development team is Markdown files.
- Changing software is the primary measure of progress.
- Swift processes promote self-sustaining development. The investors, developers, and customers should be able to maintain constant growth.
- Continuous attention to automation and parallelism enhances swiftness.
- Efficiency—the art of maximizing the amount of work not done by humans—is essential.
- The best architectures, requirements, and designs emerge from distributed workflows and centralized guardrails.
- At regular intervals, stakeholders reflect on how to make teams more effective, then tune and adjust resources accordingly.
