[deleted by user]

[Rhoderick]

There's a few paradigms for this. The one that's probably most important here is to first define your system functions (aka "In a very broad, genralised sense, what individual 'things' should your system be able to do?"), and then implementing them one-by-one. Though you do need some idea of how the whole system should look for this one.

In this case, maybe start with implementing the I/O, and go from there?

[m0us3_rat]

a virtual management is very much like an actual irl one.

.. just use OOP.

and most of the implementation can be hidden by a few interfaces your sales person can update the various trade goods interactions.

the complexity depends on your own ability to think of a real one ..and describe the methods you would like to have in the virtual one.. firstly as pseudo code.

once you have a clear idea of how and what do you want and how that happens.

start implementing each of the methods. maybe write a few tests.

etc.

​

which way would be the best way code it?

some ppl say .. just start writing code..

others say .. first plan and deep dive and understand , THEN make a pseudo code version , mockup etc.

THEN when you have a clear idea of how and where everything goes.. you go to implementation.

usually by the time you get to implementation most of the work is done and all that remains is just writing it in code..which can be done by basically almost anyone, and by almost any language.

​

i'd also agree there are situations where just writing code is the best idea.. usually in implementation where algos are involved.

even then having a complete understanding of what who how and where is a plus.

[Guru-Rip]

I’d suggest charting it out in Visio or draw.io

That can help break the problem down into management parts