Stacking things that move
A tall stack only looks right if each layer lags a little behind the one below: the bottom pelican bobs first, the rails follow, and the controller tilts last.
Notes on drafting, linkages and small tools — written somewhere along the boardwalk, usually after sunset.
Controller → bike → pelican → bike → pelicanThe drawing started as a joke prompt and turned into an exercise in load paths: every layer has to sit on something, and every wheel has to be driven by something.
Only the bottom pelican actually walks. Everything above it rides along on rails, chains and a good deal of trust.
A tall stack only looks right if each layer lags a little behind the one below: the bottom pelican bobs first, the rails follow, and the controller tilts last.
Most layout problems start in the template: unused text styles, forgotten layers and dimension styles copied from three different projects. Purge and document it once.
Automatic labels work best with a few strict rules: never overlap geometry, keep one offset, and sort by elevation before placing anything.
A fifty-line script that removes one repetitive step is often worth more than a large tool that tries to do everything.
Pelican Works is a personal notebook kept between projects: mechanisms worked out on paper, drafting habits worth keeping, and the occasional small tool.
Nothing here is for sale. There is no newsletter and no comment box, and the pelicans do not take questions.