I guess my point more was the section seems to conflate the idea of pools
with non full node workers.

Pooling happens regardless for full node miners, unless you have giant hash
rate on your own.

It's used to reduce variance, at least primarily. Of course somehow people
end up spending thousands on asic and are too cheap to run a full node now.
On Apr 15, 2014 6:09 PM, "David A. Harding" <notifications@github.com>
wrote:

> In en/developer-guide.md:
>
> > @@ -3185,6 +3185,94 @@ Bitcoin Core.
> >
> >  ### Alerts
> >
> > +## Mining
> > +{% autocrossref %}
> > +
> > +Mining adds new blocks to the block chain, making transaction history
> > +hard to modify.  Mining today takes on two common forms:
> > +
> > +* Solo mining, where the miner is also a full peer on the network.
> > +
> > +* Pooled mining, where the mining pool is a full peer and the miner just
>
> @instagibbs <https://github.com/instagibbs> I think the design of p2pool
> is really awesome, but yeah, almost nobody uses it, so I left it out for
> brevity. However, I just pushed 1ba5a8b<https://github.com/saivann/bitcoin.org/commit/1ba5a8b>,
> which adds a SOMEDAY comment to describe p2pool at some point.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/saivann/bitcoin.org/pull/66/files#r11660702>
> .
>