Guides, tips, and tricks from the team at Fly
#alternative #app #cdn #close #clusters #competitor #deploy #docker #docs #documentation #elixir #fly #fly.io #heroku #hosting #networking #postgresql #servers #to #users

Comment contribuer à un projet open source

• Identifier et fixer des bugs
• Proposer des améliorations (éventuellement en fonction de votre profil)
• Comprendre comment fonctionne le projet (policies, code of conduct, about page, documentation, README, wikis, ...)
• S'il y a encore des points d'interrogation -> Communauté (Slack, IRC, etc.).

Cheatsheets everywhere ! :-D

Générer un site statique à partir de plusieurs dépôts git (branches, version, ...).

On peut jeter confluence :-)

Fast, offline, and free documentation browser for developers. Search 100+ docs in one web app including HTML, CSS, JavaScript, PHP, Ruby, Python, Go, C, C++, and many more.

'sais plus si je l'avais déjà partagé ou pas...

You will be using your code in 6 months

Code that you wrote 6 months ago is often indistinguishable from code that someone else has written. You will look upon a file with a fond sense of remembrance. Then a sneaking feeling of foreboding, knowing that someone less experienced, less wise, had written it.

As you go through this selfless act of untangling things that were obvious or clever months ago, you will start to empathize with your users. If only I had written down why I had done this. Life would be so much simpler. Documentation allows you to transfer the why behind code. Much in the same way code comments explain the why, and not the how, documentation serves the same purpose.