Do

build_assets_job()

and

define_assets_job()

have same responsibilities ? Bringing it up because I have been using

define_assets_job

to add to Definitions until today, but I also discovered

build_assets_job

and many more new

build_*

functions that appear more intuitive by following the Builder design pattern.

build_assets_job

is an internal utility that isn't designed for public consumption, so I'd say use it at your own risk

Does this apply for all

build_*

functions?