Wotcha LV Peeps,
Hope you are doing good, doing work (if you want) and healthy.
If you are familiar with my witterings you will be aware of the terms coupling and cohesion. Because my brain is attuned to thinking in this fashion I've noticed that they apply to other things too....
One skill you get by default if you do what I do is that it makes you a pretty efficient project manager. (I get paid when I finish a project, it focusses your mind!)
I noticed something the other day when presented with a Gantt Chart .... I always work hard to remove things from the critical path. So rather than the chart below.
I much prefer this next chart, where possible.
Because I've decoupled the tasks from each other they are no longer on the critical path. If needed I could start task 4 before task 1 or even better get someone else to do it. The links are therefore coupling between tasks. How would we break those links? We could design the task to be easy to define and has limited and clear inputs and outputs.
This brings us to the point of coupling and cohesion, it was so that software could be broken into modules that could have multiple people working on them.
Another example is when organising events, one task is to organise the catering. It might be nice to provide the staff with GDevCon badged attire. This simple requirement has a lot of implications. We are coupling the organisation of the catering to the individuals in the catering staff. In essence we have become too involved in the internal workings of the catering company. It's much better to either not be involved in what the catering staff wear or to clarify in the contract that we want GDevCon badged uniform and provide clear requirements and leave it up to the catering company to organise.
So we are using cohesion to decouple ourselves from the internals of the catering company, this could be considered using a contract to hide the internal workings of the catering company.... Information Hiding!
All the best