Older schedulers like myself used logic to limit the number of resources required because the scheduling software was too primitive to do this.
We called this type of logic “crew restraints” and I still use this technique today.
But if the longest path of activities are themselves quite aggressive then we are only setting ourselves up for failure.
My strategy of primarily using Finish-to-Start relationships is a direct result of the early years of CPM scheduling, when Activity-on-Arrow (AOA) was the dominant scheduling technique.
In those days, the arrows represented tasks, whereas the nodes (circles in most cases) were the activity identifiers.
This technique was also referred to as the Arrow Diagramming Method (ADM).
The Activity-on-Node (AON) method became very popular in the early 1990s and was certainly spurred along by Primavera Systems’ decision to drop Activity-on-Arrow altogether when the first Windows-based version of Primavera Project Planner (P3) was released in 1994.
My attitude often comes down to this: prove to me you can get ahead of my schedule and I will modify the logic accordingly.