Some ideas for improvement + Do you need a collaborator?

[dorukhansergin]

Hi Team,

I've been thinking about doing something like this and you guys already have a great head start. I'd love to be a collaborator or at least a regular contributor to this project.

Speaking of which, here are some ideas on how the guide can be improved.

• IDEs: While I use PyCharm myself and I love it, I know people also use Sublime Text + SFTP plugin or VSCode + Rsync plugin. Those could be added.
• Exploration of High-level APIs starting from ignite. These have implications for how to structure to code and usage of callbacks.
• Logging and experiment management, a review of which libraries work well with Python for this. I currently started a repo dedicated to Mlflow with certain use cases. This has implications on how to set up the CLI for the main and subsequent procedures.
• Project template. There is this one I really like.
• How to set up different entry points for people to interact with your research in the repo? I am usually influenced by this repo

And many others I forgot about.

[IgorSusmelj]

Hi,

thanks for your interest in contributing. I like your ideas and inputs (Especially the first 3 points). I would like to keep this style guide as simple and lean as possible. I don't want to push people into certain patterns or making them use templates.
Feel free to make a pull request to add missing pieces. I haven't used Sublime or VSCode with plugins to work on remote machines. I'm pretty sure there are lots of people who would love to get an idea of how this can be done :)