Comment by Shared404
5 years ago
But also, the blog post should be able to focus on it's own business logic so to speak.
The same arguments for and against using libraries apply here, and it's up to the author which works best for their piece.
5 years ago
But also, the blog post should be able to focus on it's own business logic so to speak.
The same arguments for and against using libraries apply here, and it's up to the author which works best for their piece.
This is what introductory paragraphs/sections/chapters are for. Someone already well acquainted with the subject matter can quickly skim through them, while others less familiar with it get a quick catch-up.
I agree. But that's not always the best solution.
Just like libraries, sometimes it is and sometimes it isn't the best approach.
For example, in a "How to do $BASIC_THING in python" article, putting an intro of "This is what a variable is" may not be a bad idea. Meanwhile, in a "Writing an operating system from scratch in an esolang I wrote" article, maybe you'd be better off linking to previous blog posts or other resources.
Obviously these are both extreme examples, but I think it's still a valid view.