Find attached my project. (I am not familiar yet with github and the like; for the time being I hope this is a suitable way to share.)
If you want to run my project, please be aware of this line of code (in the first code block): opened_file = open('inputdata/hacker_news.csv')
So do ensure that the input file is in that folder (or that you update the code).
No particular issues or topics that I request feedback for - any feedback is welcome and appreciated!
Thanks for sharing your project, Jasper. The way you did it is just fine, I think the team has it set up to automatically create a view link so that we can see it fine. You don’t have to worry about anyone having to run the cells if they download and view it locally – it shows up just as it was when you last ran the cells.
I think you did a great job! The code is commented well and you used the Markdown cells to note your observations and steps. I really like how you went back and mirrored the intro and conclusions to summarize everything for the reader.
Good job! You make it seem so easy. I’m constantly having trouble with my markdown notes and I have a constant feeling that it is some how wrong or not up to par with other people’s notes. It just seems really messy and that I’m not using the correct terminology. Is there some tip you can provide so I can do a better job on my markdown notes?
I like to use the verbiage straight from the reading of the mission. Changing up dataquest words to your own really helps you to put the context of the project in your own understanding. Its up to you to make it readable to your audience.
Thank you for the encouraging comments! And @louisalau716 sorry for my late response. It’s hard to come up with general tips, but let me try nevertheless. While it may sound abstract, one thing that you may want to keep in mind, is that in my view we should be “telling a story, supported by code” rather than “providing code, supported by some text”. So really think of the story as you want to tell it, put that in words that come naturally for you and that the audience that you have in mind would understand. Then use that as the framework, and put in your code “in between”. Another thing: review and revise. The text as you found it in my guided project I certainly did not write in one go. I regularly read through what I had written before and then improved it. And did so for the entire thing once more before publishing it. Yes, that costs time, but I personally really need some iterations to get to a text that I feel happy about. And feel that that is time well-spent, as ‘the story’ is as important as ‘the code’ to get something across.
