> "architect-less" [vs] "architecture" has run fully amok and any corporate project winds up wading through cloud architects, devops architects, The fact that

> "architect-less" [vs] "architecture" has run fully amok and any corporate project winds up wading through cloud architects, devops architects, The fact that these two statements actually both accurately describe reality is the crux of the problem, IMHO.