A programming pattern that divides components into different chemical stages to -allow reusability as much as possible. Mostly useful for frontend design.
Source: Brad Frost
At the linux kernel guideline are some good advices: The linux kernel - coding style -Google have some guidelines for some languages as well. Use positive booleans for better readability, like described here | Google Code health
Be kind! People are more receptive to feedback if you assume competence and treat them with respect.
Focus your comments on the code, not the author. Avoid statements with the word ‘you’ which can give the impression that you are judging the person and not the artifact.
Explain why you are making the comment. You may be aware of alternatives that are not obvious to the author, or they may be aware of additional constraints.
Express the tradeoffs your suggestion entails and take a pragmatic approach to working with the author to achieve the right balance.
Approach your role as a guide, not a test grader. Balance giving direct guidance with leaving some degrees of freedom for the author.
Consider marking low priority comments with severity like Nit, Optional, or FYI to help the author prioritize the important ones.
Source: Google testing blog
Some of my favourite tools and routines I using in my development environment.
Some bash file recommendations:
#!/usr/bin/env bash @@ -595,7 +503,43 @@ PKM (kn msg "- param: ${param}" msg "- arguments: ${args[*]-}"
A programming pattern that divides components into different chemical stages to +allow reusability as much as possible. Mostly useful for frontend design.
At the linux kernel guideline are some good advices: The linux kernel - coding style +Google have some guidelines for some languages as well. Use positive booleans for better readability, like described here | Google Code health
Try to develop my daily projects within the vitualServer with docker and traefik as proxy for localhost.
my daily most used commands
mvn versions:set -DnewVersion=1.1.0 && mvn versions:commit
docker run --rm -it --name pgclient jbergknoff/postgresql-client postgresql://<USERNAME>@<HOST-IP>:<PORT>/<DATABASE_NAME> +
Index Cond
Filter
CreateAt > ?1 OR (CreateAt = ?1 AND Id > ?2)
(CreateAt, Id) > (?1, ?2)
In general there are some basic topics, you have to check before start a bigger project/application. These decisions are fundamental for the smooth development of a applicaltion.
How to deal with timestamps i.e. getting from user inputs? Do we wanna be timezone compatible with clients/users in different timezones? How to get timezone from user in my backend requests?
Ingredients: <%= render recipe.ingredients %>