deft/notes/following_best_practices_is_a_bad_practice.org
Yann Esposito (Yogsototh) c1d2459d0c
save
2024-08-14 11:35:42 +02:00

31 lines
1,011 B
Org Mode

:PROPERTIES:
:ID: 75035ffa-73bd-46e5-bdc2-8b80b08e0566
:END:
#+title: Following Best Practices is a Bad Practice
#+Author: Yann Esposito
#+Date: [2023-01-05]
- tags :: [[id:a5be1daf-1010-428f-a30f-8faf95c1a42f][blog]]
- source ::
* Best Practices are Bad Practices
So if you are in the software industry for some time now you probably know what
I am talking about.
So mainly here are all the "new best practice you must follow if you want to be efficient"
- Kubernetes
- Docker
- nix
- SCRUM (this is bullshit)
- etc…
But most of these Best Practice are great but only after your team has reached
some level of experience.
But really, if you want to build and deliver something the main best advice is
not to follow these best practices and discoveries, and focus on what you really
already familiar about.
So I would say only use 90% of what you are already familiar and efficient with,
and to keep you motivated to not exceed 10 to 20% of something new, Best
Practice, or something like that.