Please enable JavaScript.
Coggle requires JavaScript to display documents.
Developer guideline (:smiley:Mindset (:smiley:Continuous Improvement
…
Developer guideline
:smiley:Mindset
:smiley:Continuous Improvement
Always leave work in better shape than when you found it (even if by a little).
-
-
:smiley:Limit work in progress
Stop starting, start finishing.
-
-
-
-
:smiley:Build security in security
Security is not an afterthought. As with butter in a cake you can't add it post mortem.
-
:smiley:Plan
Having to be planned, prioritized, and tracked
:smiley:Planning and effort estimation
- No realistic plan can be made if the targeted work does not have a reasonable effort estimation.
:smiley:Work breakdown.
- Having a common understanding of the scope of the work.
- Shed light upon your tasks and challenge scope and verify expectations.
-
:smiley:Task Completion.
- Code builds without warnings.
- Code tested with automated tests.
- Code has been reviewed and follows the application design.
- Documentation updated(clarifications of requirements, assumptions, decisions).
- Deployment and verification on integration server was successful.
=> Unfinished work generates no value.
-
:smiley:Build.
:smiley:Code Maintainability.
- Maintainability benefits most from adhering to simple guidelines.
- Maintainability is not an afterthought, and should be addressed from the very beginning of a development project. Every individual contribution counts.
- Some violations are worse than others. The more a software system compiles with guidelines, the more maintainable it is.
:smiley: Coding conventions.
- Follow the general formatting principle.
- Using the provided default style of IDE provided by company.
- As being consistent is often better than being correct we stick to established convention of your project at hand.
=> Consistently pay attention to code maintainability and clean code.
:smiley:Technical debt.
- An important lesson to learn is Later Equals Never.
- When you have to do something, stop waiting for the "right moment", just do it now.
=> Leave no code smells behind.
- Proper communication of our work adds tremendous value.
- FIXME: thing that MUST be fixed before going into produtcion(missing or bug code).
- TODO: Things that SHOULD be fixed in order to have clean, maintainable code(technical depth).
:smiley: Source code repository.
- Source code and configuration is stored in centrally managed source_code repositories.
:smiley:Build system.
- Builds must always be automated, headless, reproducible and stable.
:smiley: Binary Repositories.
- Use our central managed binary repository as build dependencies source.
-
-
-
:smiley:Provision.
- Don't touch the servers directly, every change should be done with script.
- Deployment scripts and their configuration must be committed to the source-code repository.
- Every change should be idempotent, so reapplying scripts does not change the result beyond the initial application of the change.