# Introduction

### `Early transcriptions`

This is my first try on blog writing, the quality of the blog and writing style will gradually improve as soon as I unlock the super powers hidden beneath my mortal mind. \
\
Everyday, 10 tips are posted on a random topic. Writing ten ideas a day down rewires your brain. If every day you force yourself to be creative, the brain rewires itself to make creativity a priority.

> #### Yesterday is history, tomorrow is a **mystery**, and **today** is a gift–– that is why it is called the present.
>
> -Bill Keane

A bit about me. I would not like to bore you with the details.&#x20;

The name's Nivesh. CSE - Sophomore, University. India. That's it!

*`That was a quick intro! Damn!`*

Coming back to main topic, the main idea between writing the tips is to exercise my idea muscles and unleash creativity. Are the ideas good?

Not really. Hardly ever. Out of thousands of ideas, maybe 10% of them are useful in some way. Maybe a few are good enough to make money. Maybe one is GREAT. Who knows?

Too many people say, “Oh, I’m creative. When I need to be, I’ll sit down and come up with a great idea.”

It doesn’t work that way. You have to dig the ditch before the rain comes.

Writing ten ideas a day for three months and you will feel like an idea machine. And you will feel abundant. Because you know that no matter what, you can keep generating ideas.

If you have come this far. Thank you for reading. Stay tuned for "10 TIPS" daily.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://niveshpai123.gitbook.io/10-tips/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
