i just released the 8th part of my "essence of architectural work" blog series, embedding various software development approaches into the uncertainty continuum (which influences the *when* and *how much* of architectural work).
i released a new blog post about the omnipresent striving after error-free, "software-like" AI solutions, the limits and dangers of this approach, and what we can learn from resilient software design about robustness as a better alternative. enjoy ... ;)