Multiple git workflow exists. Choosing the right git workflow depends on the type of project, the team size, the deployment frequency and the deployment environement.
- Centralized workflow
- Feature branch workflow
- Forking workflow
Maher Mhiri visiover
A simple, pragmatic versioning convention.
In a sense, this is a subset of SemVer, but with slightly different semantics.
An API has two series of releases: feature-complete, and feature-incomplete.
visiover
/ bitbucketpipelines.md
Last active
December 23, 2021 12:59
Pipeline configuration (https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html) Php and pipelines (https://confluence.atlassian.com/bitbucket/php-with-bitbucket-pipelines-873907835.html)
Bitbucket Pipelines is an integrated Continuous integration (CI)* and Continuous delivery (CD)* service, built into Bitbucket. It allows you to automatically build, test and even deploy your code, based on a configuration file in your repository.
Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer or navigator,[1] reviews each line of code as it is typed in. The two programmers switch roles frequently.
While reviewing, the observer also considers the "strategic" direction of the work, coming up with ideas for improvements and likely future problems to address. This frees the driver to focus all of their attention on the "tactical" aspects of completing the current task, using the observer as a safety net and guide.
TOOLS : https://openapi.tools/
Generate from annotations : https://github.com/zircote/swagger-php / http://zircote.com/swagger-php/#links
====
Link : https://www.youtube.com/watch?v=VuBVAgwMfLE&list=PLGJDCzBP5j3xGaW0AGlaVHK2TMEr2XkP9&index=3
General repeatable solution to a commonly occurring problem in software design.
Design patterns can speed up the development process by providing tested, proven development paradigms.
- Learn by doing - Woodworking analogy.
- tuto : https://scrimba.com/g/glearnreact
- Speed - use of virtual Dom.
TDD is the process of writing automated tests to ensure that code works before writing the implementation. You write a test, watch it fail (red), write the implementation, watch the test pass (green), and refactor if needed. Repeat the cycle as you build out the system.
The process has been studied in depth, and has proven itself to be very useful to increase the quality of software. But did you know that it also saves organizations a lot of time and money?
One of the primary reasons managers cite for waiting so long to implement TDD is the cost. It’s common for initial project build-outs to take up to 30% longer with TDD.
What those managers need to know is that TDD reduces production bug density 40% — 80%, and that makes all the difference. More bugs in production leads to a dramatic rise in maintenance costs.
OlderNewer