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!