Software Development: Difference between revisions
Jump to navigation
Jump to search
(→CICD) |
|||
| (16 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[Software Engineering]] | * [[Software Engineering]] | ||
=Overview= | =Overview= | ||
| Line 9: | Line 7: | ||
With any of the delivery modes below, the provider controls and manages some portion of the technology stack. The customer manages the portion of the technology stack that is not managed by the provider. The benefit is that the customer controls the design of its portion of the stack. | With any of the delivery modes below, the provider controls and manages some portion of the technology stack. The customer manages the portion of the technology stack that is not managed by the provider. The benefit is that the customer controls the design of its portion of the stack. | ||
Software development makes [[Software_Architecture#Overview|software architecture]] to materialize, and the set of rules and practices that go into software development belong under the larger umbrella of [[Software_Engineering#Software_Development|software engineering]]. | |||
=A/B Deployments= | =A/B Deployments= | ||
| Line 76: | Line 39: | ||
{{Internal|Code Review|Code Review}} | {{Internal|Code Review|Code Review}} | ||
=Simplicity= | =Simplicity= | ||
| Line 96: | Line 55: | ||
=Consistency= | =Consistency= | ||
* https://medium.com/@jgefroh/why-consistency-is-one-of-the-top-indicators-of-good-code-352ba5d62020 | * https://medium.com/@jgefroh/why-consistency-is-one-of-the-top-indicators-of-good-code-352ba5d62020 | ||
=Software Development Practices= | |||
* [[Continuous Delivery#Overview|Continuous Delivery]] | |||
=To Process= | =To Process= | ||
* Grady Booch - Building the Enchanted Land https://www.infoq.com/presentations/ai-best-practices. Health of the system: "do you have a regular process of release?" "do you have a sense of architecture?" | * Grady Booch - Building the Enchanted Land https://www.infoq.com/presentations/ai-best-practices. Health of the system: "do you have a regular process of release?" "do you have a sense of architecture?" | ||
* [[Feature Toggle]] | |||
Latest revision as of 23:14, 2 July 2023
Internal
Overview
With any of the delivery modes below, the provider controls and manages some portion of the technology stack. The customer manages the portion of the technology stack that is not managed by the provider. The benefit is that the customer controls the design of its portion of the stack.
Software development makes software architecture to materialize, and the set of rules and practices that go into software development belong under the larger umbrella of software engineering.
A/B Deployments
Twelve-Factor Application
Semantic Versioning
Good Reads
Developing Applications for the Cloud
Microservices
Infrastructure as Code (IaC)
Infrastructure as Code is an approach to IT systems infrastructure management, where various elements of the underlying hardware infrastructure are represented as programming constructs rather than physical hardware. This approach can be used in combination with automation tools to provide the ability to provision infrastructure in a repeatable and reliable manner.
Code Review
Simplicity
- https://thinkingsideways.net/code/2019/03/24/simplicity-over-flexibility.html
- https://www.infoq.com/articles/simplicity-manifesto-development
Scrum
Domain-Driven Design
Software Security
Consistency
Software Development Practices
To Process
- Grady Booch - Building the Enchanted Land https://www.infoq.com/presentations/ai-best-practices. Health of the system: "do you have a regular process of release?" "do you have a sense of architecture?"
- Feature Toggle