Thank you for the questions Subha. When it comes to blogs/articles, the actual research process involves:
- Reading the official specification and the MDN documentation and making notes as I go along.
- Use the feature (as a developer) and write down all the points I struggled with.
- The tutorial then identifies those pain points, and how to work around them. The paint points I experienced is probably what folks reading the tutorial will experience/have experienced also.
Resume: I'm big on projects! Having built stuff is such a helpful tactic as a candidate. I don't mind if it's a hello world app, as long it pushed the candidate in a creative sort of way.
Also no matter how complex or how simple the project is, there's still lots for us to talk about e.g. what made you chose that language, how did you find it, what were your pain points, how does it compare to that other language, what did you think of the syntax etc.
One thing that would stand out for me, if the candidate worked on a project which attempted to solve a problem they had, or someone else had, that's a big plus in my mind. Nothing wrong with implementing some binary search algorithm just because, but I think it's cool when the project genuinely helps someone.