News for hackers. Stuff that matters.
Re:Ask HN: How to blog things I've learnt in graduate school? by codingdave on Wednesday May 30, 2018 @04:52PM (#17191668)
1) Just write. You'll find your own voice. I'd worry less about whether you sound academic or not and more about whether you sound like yourself.

2) Don't write theory, write applied principles. I wouldn't share anything that was put together by one of your professors - that is their work. But if you apply their lessons to something in your own work/life, you absolutely can tell us about it, and outline the academic principles involved as you go.

Re:Ask HN: How to blog things I've learnt in graduate school? by klenwell on Wednesday May 30, 2018 @08:27PM (#17193047)
#1 brings to mind a James Gleick tweet I saw this morning that struck a chord:

> “The pen is an instrument of discovery rather than just a recording implement.” —Billy Collins

https://twitter.com/JamesGleick/status/1001835227105423360

Re:Ask HN: How to blog things I've learnt in graduate school? by keerthiko on Wednesday May 30, 2018 @09:31PM (#17193307)
Always this. Just write. Find a sample unit of your target audience, and ask them to read your posts and give you feedback (what was hard to follow, boring, interesting, too much background, too little, etc) and iterate.

As for #2, if you have a friendly prof for a relevant course or two, ask them directly! Chances are, they'll be happy to have you write about what you learned from their class, and may even be willing to read your posts and give you feedback.

Re:Ask HN: How to blog things I've learnt in graduate school? by danso on Wednesday May 30, 2018 @05:14PM (#17191864)
I second this -- actually writing is critical to finding and refining your voice. That, and actively soliciting feedback. Submit your posts to the relevant subreddits and HN, and don't shy away from constructive negative feedback.
Re:Ask HN: How to blog things I've learnt in graduate school? by brudgers on Wednesday May 30, 2018 @06:56PM (#17192622)
Or ask people you know to read drafts for tone and voice.