Note that that is only the start of the journey where I explore the right way to work in sync with latest tech but still be unique and add value. Will keep you posted with progress.

Recently, I generated a blog post via GPT. The problem is, should you don’t guide it well, it is going to just write general stuff and won’t have any personal touch.

In the long run I will provide you with the prompt and the resulting blog post, so you may judge if it has any value or is just random rambling of the facts.

But first let me state my position on the subject of using generators:

For me it’s okay to make use of generators, so long as you define the outline and the sort of writing, that’s what you might be contributing. The more details you define, the more value you added, and fewer value is a few general generated stuff.

The primary blog post I attempted to jot down with the assistance of GPT generator is one in all these (attempt to guess which):

Guessed which?

The chance management one was generated, the opposite one was hand written. Which one is best btw?

The propmpt I used to generate and guide GPT within the direction I would like is that this one.

Be happy to comment and discuss the right way to improve this!

For every of the next points write a paragraph:
- what's risk management
- the right way to numerically quantify risk
- the right way to model real world as numerical quantities
- why it's important to make use of numerical quantities when assessing risk
- what's the target of risk management
- what questions risk management process tries to reply
- wherein cases it is just not possible to empirically get data for risk management procedure
- how can simulations might help risk management?
- what are monte carlo simulations on this context?
- what are the same old outputs of monte carlo simulations?
- an example of monte carlo simulation getting used in risk management
- an example of actions proposed based on probabilities of certain risk events
Additional requirements:
- Each paragraph MUST NOT contain greater than 60 words
- Text MUST use easy language
- Text MUST avoid expert terminology each time possible
- Text MUST BE engaging
- Text MUST BE easy for casual readers to know
- Text MUST BE in a sort of a blog post
- Text SHOULD OCCASIONALLY make jokes
- Text SHOULD OCCASIONALLY be witty