Open Contemptio opened 6 years ago
This is a wonderful ide! I imagine a md document with a few sections and hyperlinks so you can quickly look for related tools. Important distinction to make right away this document is for tools only and not tutorials.
What are the different sections/labels we sort things under? I start by posting some tools here and what I think they should be sorted as.
pkg manager yarn - https://yarnpkg.com/en/
code quality prettier - https://prettier.io/ eslint - https://eslint.org/
version control git - https://git-scm.com/
security retire.js - https://github.com/RetireJS/retire.js snyk - https://snyk.io/
development ngrok - https://ngrok.com/ teamviewer - https://www.teamviewer.com/en/ serverless-offline - https://github.com/dherault/serverless-offline
Editors Atom - https://atom.io/ Nuclide - https://nuclide.io/ vscode - https://code.visualstudio.com/
build tools webpack - https://webpack.js.org/ rollup - https://github.com/rollup/rollup
Glad you like it! And yes, a list of tools and links was what I intended.
As for categories, I think we will just make them up as we add things. It can be hard to come up with them on the spot (albeit you have done a fair job already) and we might want to merge or split categories later on. Not very important though; the most important thing is that this list exists somewhere. Extremely useful for eventual additions to the team as well.
A couple of things 1) with the start of this list i think there should be a "ban" on posting tools in slack. If it's useful enough to be posted there it is useful enough to be a issue, so the tools can be evaluated.
2) The list is for tools and not npm packages that are useful. Distinction
3) The list should be curated. So a tool is only put on the list if it's deemed worthy, and could be replaced/removed if the right criteria is met.
Great points! I'll add them to the description.
Should this be it's own project? The reason behind that would be so you could have it as the README.md and get the list up right away. No need to navigate to it through a file structure.
I agree.
Error reporting/Exception tracking tools Airbrake - https://airbrake.io/ Sentry - https://sentry.io/welcome/ Rollbar - https://rollbar.com/
Learning Exercism - http://exercism.io/ Project Euler - https://projecteuler.net/
Validation sync/async
https://www.papapi.se - postnummer async
Flow-type cheat sheet. https://www.saltycrane.com/flow-type-cheat-sheet/latest/
DynamoDB reserved keywords: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ReservedWords.html
Mostly concerns tools which have been or are going to be listed in Slack's #education. In order not to lose track of all these qualities of life, a list should be kept that lists these along with a short description of each. This issue involves deciding on the location and format of such a document, and also any discussion or meetings required to resolve this. A couple of things to note: