Communication, simplicity, feedback, respect

[rami18]

Hello....................


Communication, simplicity, feedback, respect

Those are essentials steps also, you have to know how to communicate
your your ideas and how to simplifying them correctly, and efficient
communication is also efficient abstration, so you have to know how to
decompose and how to abstract the essentials to be able to communicate
efficiently, and this better realiability and correctness, feedback is
also important, i mean like the testing phase, you have to improve your
ideas layer by layer and incrementally using the patience of science ,
because as i have said your perception takes time to be correct
perception , so you have to know how to be patience science waiting
for your perception to be set correctly, this is in accordance with
efficient morality and in accordance with Liberty.

And how to improve also quality and timeliness of software ?

I was asking myself this question and i will present my thoughts:

You have to abstract also the graph that offer a deeper insights into
the nature of objects and the system.

And this has to be done smartly..

The abstract graph of the system must reveal the following:

1- It has to reveal the hierarchy of roles and the
breadths of those roles

2- It has to offer a deeper insights into the nature of the objects, the
abstract graph must reveal easily the triads why-what-how.

3- the abstract graph must be clear and it has to clearly and
efficiently and plainly communicates what the roles do.

4- It has to have a high unity, a role has high unity if all actions
described in the role have one purpose.

5- You have to have a good coupling between objects and methods. This is
the visibility and degree to which two objects or methods communicate
with each other. This is the degree of interdependence between software
modules, a measure of how closely connected two routines or modules are,
it must be low coupling. A low coupling is a sign of well-structured
software system

Also i am an experienced programmer in parallel programming and
synchronization algorithms, and here is some of my inventions:

You have to appreciate my inventions of my C++ synchronization objects
library..

Here is why:

Here is the problem of optimistic Transactional memory:

If there is more conflicts between reads and writes you have to rollback
and to serialize also etc. and this will be less energy efficient and it
will be less faster than pessimistic locking mechanisms

So i think that my C++ Synchronization objects library and my Delphi
synchronization objects are still really useful..

You can download it from:

https://sites.google.com/site/aminer68/c-synchronization-objects-library


Thank you,
Amine Moulay Ramdane.