I agree with @sandeep and @chilimatic. I think what will make Hashnode Originals special and unique is that a great amount of time and effort will be put into the articles and text. This will make them thought provoking and insightful. I think Hashnode Originals will have a certain degree of quality that is high. Hashnode Originals like their name implies should be unique to Hashnode.

1. Stories I would love to read would include:

• Stories about similar problems that a specific software developing community faces as a whole. Examples could be similar problems game developers face in their craft. How the web development community is solving the problems of safety and security.

• Articles about technologies, projects, and people that are truly changing the world. I mean projects that are groundbreaking. Projects that changes peoples lives and help their communities

• Advice and experience articles from acclaimed developers in their industry. These articles would give background of the person as well as give others insight into their great minds

2. Stories I think should be avoided include:

• How-to's, simple tutorials, quick tips, or simple guides should be avoided.

• Articles that compare technologies. No "React.js vs Vue.js". No "Functional vs OOP". No "<insert favorite framework> vs jquery".

• Boring articles. Articles that make me leave with nothing. Articles that don't offer me a new insight or new ideas about something. (This one is probably a little general.)

Thanks @sandeep for asking for input for what content the Hashnode community wants to see. Hashnodes always impresses me when they cater to their users and community! 👍 👍 👌 👌

I don't know if you remember the Teach Yourself [Language] in 21 days type of books, I'd like to see something like that for Kotlin or something teaching you to transition from Java to Kotlin, maybe even write it myself - writing helps me learn as well as it forces me to read and experiment.

The 21 topics could be spread across several months, every 11 days another post continuing the series.

I love opinionated articles about tools, processes, and methods. I like to read "This is my favorite because..." and "I hate this because..." instead of "Here's an objective explanation...". I find these the most interesting to read and also the most helpful in forming my own opinions.

I'd also love to read about other developers' journeys—how they got to where they are and how they're getting to wherever they're going. What were their pivotal moments? What are they working toward?

I would love to read about:

• Technical findings with real data instead of just opinions. Benchmarks, researchs, polls, etc.
• Personal opinions based on real problems that people are facing in their everyday programming sessions.

You should probably avoid:

• Personal opinions based on nothing but the author's mood.

I agree with @fibric that every story counts / afford to invest into the community counts. If someone invests time into searching the right desk light and elaborates on it, It can be as interesting as reading about CPUs, GPUs, State-Machines, Distributed Systems ... the only thing I want is that people really invest time into it.

Maybe we could add a volunteering review process for such stories ? We all think and express ourselves differently so helping to structure and check really can be a big help.

I guess everyone of us has an idea what he/she/_* finds interesting, this is something i leave to all of the community to decide and vote and set priorities :) as long as I'm allowed to post my stories.

Hi Sandeep :)

I think, stories containing the following bullets might be interesting (at least for me):

• How the author struggles to learn a new language/framework/pattern, with simple examples of stuff they tried. I do not mean tutorials themselves, but just a meta text about the experience. It might help others who are following actual tutorials take a look at the steps of the author and try to retrace them when stuck. At least this kind of article would be very helpful for me at the moment, learning Rust, so I guess it might be for others, too ;)
• The thoughts the author put into building a program or library (maybe even while writing said library). It is always difficult to look into the head of another programmer, especially when just looking at the source code, so a little more detail would be nice. The only other way I know of to get deeper insight into how another developer works is by doing pair programming; but that's not really possible because of time/location.
• Hypothesis about how to construct complex software projects and why it makes sense to do certain things while it might be stupid to do other things. Just like how to glue things together
• Bugs which kept the author glued to the PC for several days, what they tried, how they debugged, which tools they used and how they finally fixed the error
• In general something with more emotion, which might not even be about a technology I want to learn, but just to have a nice little read about someone elses thoughts and experiences
• Comparisons of available tech which people might not even think about that much with deep insights about protocols, history, benchmarks, simple examples which show the difference in implementation and usage, etc.
• Implications of software (and certain algorithms) on hardware. The author can use such a case to show certain problems with security and hardware failure and show how to improve the situation even a little. For example why it makes sense to use a CoW FS and how to emulate it when not available (for example on Arduino + memory shield)
• Articles which take a deep look at available software and discuss how it might be improved or in what way a user (for example developer using the library) can get more out of the library.
• Theories about new patterns, why they make sense, in which kind of situations and what downsides they might have
• Articles about the most current tech which might drive the world in a few years, like Block-Chains, what it is, what they can do and how to apply them to other areas, with links to existing projects
• Articles about differences in culture: How do different people work together? What methods do they use, what practices, what events do they attend and how is working climate in general?
• How certain hardware works and what implications that has on software. For example how rendering to different monitors with different subpixel layout works, what implications it has on anti-aliasing techniques, what would happen if the monitor was curved, how can we apply these things to AR/VR, etc.
• A look behind the scenes: What kind of ideas and prototypes does the author come up with, but then has to discard, and why

On the other hand, things I rather do not want to see in such an amazing collection:

• Tutorials (things like "how to set up your own NGINX server") as there are so many out there already and no one will read something like that except they are in need for the technology is about
• Articles with topics (or similar topics) which have been covered elsewhere
• Monotonous topic selections, meaning there are a lot of original articles, but they all cover a similar theme (for example everything is only about front-end web development). To be blunt, I would love to see Hashnode expand a little bit, as we have loads of Web Dev topics already :)

Wow, it is really a lot easier to come up with things I would love to read... Most probably time will tell which kind of topics are less interesting, so you really should experiment a bit!

A fantastic idea!

I love to read about in-depth stories. Stories such as how GPU's and CPU's function or protocols such as MQTT work. Stories about how great minds set up a healthy and productive environment including the hardware; which chair, what keyboard/headphones, desk light and all the stuff that gets overlooked way too often. Every story counts and has a value to somebody; that's why I don't tell what stories I won't like to see on Hashnode.