Hi Everyone,

Hope you are doing well. in health and wealth.

anyway, just wanted to get some idea on the Initialization setup for Psuedocode.

If there are a couple of input requirements, should it be stated in the initialization section based on the sequence?

eg;

a program to calculate game platform, game price, payment method and maybe game type (physical/digital)

so should there be a sequence on which should be first in the initialization? will it be based on the flowchart process? if there is a gap between the requirement of input. does it mean that we need to split the initilization between process?

eg: select item ---> select item color ----> calculate price ----> apply discount ----> select location ----> calculate total cost. ---> select payment method ---End

so in the example above; the initialization is

Input Item

Input item color

Input location

Input payment method.

but since input location and payment method is not required in the earlier process (anything before calculating the prices process), should the initialization be split into 2 segments?

some like this.

Begin

Initialization
SET item_price = INPUT “Enter the item ”

SET color_tag = INPUT “Enter the item color tag (Blue, Red, Green,): ”

Calculate Price. ----> Apply discount

Initialization

Set location = INPUT "Location for delivery"

Set payment method = INPUT "payment method"

Or we can just prepare everything in the first initialization section without any issues?

Appreciate the help on this.

Thanks!!!

ChatGPT Grok DeepSeek Claude Gemini Qwen semua tu kan ada

owh, cannot get human touch anymore?

Depends, is the location and payment info sharable by other process?
If it is, yes u can have it on initialization, and keep it as singleton, so the later action will always grab if from the same cache.
But if it's vary by user input or data, then it's better to only load it when necessary, which is later stage.

For example, let say if the location and payment took 2 seconds to load.
In singleton case, only the first load (maybe during system startup) u spend 2 seconds for the initialization, thn once and for all, all the transaction later will save the 2 seconds loading time.
But if it have to be load later due to design, thn only load it when necessary, u don't want the 2 seconds kick in everytime user access the page, user might not even enter into the later stage, generally in programming it's best to avoid loading what's not needed yet for better user experience

This post has been edited by ragk: Feb 18 2025, 07:11 PM

Genius answer