Sort of. It's actually backwards because BE work should be demand based driven by the needs of the FE. This allows 3 things: a BE API as a promise AND division

Sort of. It's actually backwards because BE work should be demand based driven by the needs of the FE. This allows 3 things: a BE API as a promise AND division of labor (when possible and/or necessary) AND building what's essential on-demand by thinking about the FE's planning and needs first. The problem with building a BE first is that leads to unnecessary work. I'm a bit biased because I prefer standardized/CoC, monolithic development that doesn't have too much disconnection between the FE and BE stacks.