3 little answer to learn and understand from you!

[Kd-Here]

Hey Rémi, thanks for giving time to read this.
I appreciate your work on opensource so have bunch of questions

Blogging

1. I saw many expert developers do blogging about journey. Whom do you follow any advice for beginner dev in it.

Coding

2. If you are starting your coding journey from zero what will your roadmap of learning, language from start to end ML developer

Career

3. Any advice to ML learner to try to get job at under graduate? How to stand out from others.

[rlouf]

1. I saw many expert developers do blogging about journey. Whom do you follow any advice for beginner dev in it.

That's a very good question! I don't have anyone in mind, but a good start would be to look at the top contributors and currently most active contributors to libraries you like and look them up. Reading experts' blogs and making up your own mind about how to get there is probably the best advice there is; advice for beginners is often written by slightly-less-beginners who still have a lot to figure out.

2. If you are starting your coding journey from zero what will your roadmap of learning, language from start to end ML developer

Can't escape Python these days. I'd start with learning that language very well. For ML I heavily recommend Patrick Murphy's "Probabilistic Machine Learning", by far my favorite entry-level and intermediate book out there. It will give you a high-level overview and you can explore from there.

3. Any advice to ML learner to try to get job at under graduate? How to stand out from others.

Give people proof that you can code, get your name out there and the best way to do this is to contribute to open source, blog, and show the result of your work. People will notice eventually, and enough code out there will allow you to skip the leetcode interview in reasonable places.

When I evaluate someone's open source contributions I look at 3 things:

1. Of course, the code (but not so important)
2. The way the author communicated in issues and PRs; clear communication in writing is essential when collaborating on software. Sometimes writing issues or PR descriptions takes me longer than the code itself. For instance, an issue is very helpful when it contains self-contained examples that show the bug.
3. Rigor. That usually shows in the commit names, PR titles, the way the code is formatted, naming, documentation.

Those are 3 skills you can learn, but beginners often make the mistake of believing (1) is enough. It's not.

[Kd-Here]

Thankyou @rlouf I really appreciate your efforts!
I know this will helpful for new developers.