Thanks for putting this together. I had read about a handful of these things when GitHub announced them, but this is such a great refresher. The part about including a TLDR in all pull requests is something we could work on.
Also, I want to get better at writing documentation for projects. It seems like it's always one of the first things we neglect and if not, it's the last thing on the list. Making it part of the process seems like a win-win. You document things properly and it pays off down the road, much when you least expect it. Having the documentation ready when someone new joins the team means much less time wasted trying to remember what's what.
We never prioritize documentation and especially the last talk shows how relevant is keeping a good documentation in the project. It is something that we need to practice :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for putting this together. I had read about a handful of these things when GitHub announced them, but this is such a great refresher. The part about including a TLDR in all pull requests is something we could work on.
Also, I want to get better at writing documentation for projects. It seems like it's always one of the first things we neglect and if not, it's the last thing on the list. Making it part of the process seems like a win-win. You document things properly and it pays off down the road, much when you least expect it. Having the documentation ready when someone new joins the team means much less time wasted trying to remember what's what.
We never prioritize documentation and especially the last talk shows how relevant is keeping a good documentation in the project. It is something that we need to practice :)