Documentations are better than AI results

At some point, you’ve probably felt that AI responses are often too text-heavy and require extra mental effort to process, even for a simple question — unless we specifically tell it how long we want the answer to be.

Think about the early days of the internet, or even just ten years ago, when the web was a place for knowledgeable people to share what they knew with others who were struggling with certain problems.

People used to share solutions to help others quickly overcome their issues. Personally, I used Google Search in my early days of learning programming, and about 60% of what I know today came from searching for problems and finding their solutions on Google.

I still remember those times when we developers had to scroll through thousands of websites, blogs, articles, and documentation pages just to find one solution we’d been stuck on for two days. It was definitely frustrating back then — but it was also excellent brain training.

I learned so many things unintentionally, even when I wasn’t focusing on a specific topic. For example, while searching for how to handle Flask responses in JavaScript, I ended up learning how to cache responses, why not to use var, and how to use JSON instead of plain objects. So, documentation really helped train my brain.

This was my personal experience, but I think most developers can relate to it. If you’ve had a similar experience, don’t hesitate to share it in the comments. Thank you.