Probabaly the reason why heated debates emerge is because no one pat rule ever seems to work across the board (ha ha, what a pun).
I agree with the comment that a ground plane amounts to a large area single-point ground.
Thing is, whether on a single card, or in a large system of components, I guess the one basic goal is to minimize ground currents. And the knee-jerk reaction of isolating grounds doesn't always work, to this end, because then your risk frying components when their zero volt references drift too far apart.
One good solution is fiber optics.
Much depends on the power output level of the switcher. The simplified drawing in the article shows the typical single phase SMPS chip with on-chip gate driver. With literally dozens of chips to choose from this approach reaches its practical limit around 150W. For these middle-to-lower wattage supplies a single ground consisting of a compact star ("single point") topology is adequate, but a ground plane is preferred for best EMI performance. Much above the 150W (or so) level a separate gate driver device will greatly help decouple switching transients from the SMPS chip - this is where a two-mesh power and signal ground approach is necessary. In these designs the signal ground will host the SMPS chip and associated bias and feedback scaling/filtering circuits. These larger designs also tend to be poly-phase so a separate power ground is especially important to keep the multiple high current paths away from the control circuitry. The power ground is common to the gate driver, current sense, input capacitor(s) and OVP. Of course in isolated designs like flybacks there's almost always a third isolated "ground" on the output.
both are a single point star ground, one is just more distributed than the other :-)
and then you have , vias and components on both sides of the board,
all good fun.
My mark one eye ball rule of thumb is like yours.
Look at the currents, keep di/dt low.
and break every other rule at some point or other
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.