Short micro blog pieces that might lead to something bigger...
Are strong, deterministic, highly specified guardrails (e.g. context, tests) really required to keep AI on track? If so, then aren't AI engineers applying software engineering to guardrails?
It seems that AI engineering is basically software engineering applied to building AI guardrails.
See the pattern?
Software engineering fundamentals + specific knowledge in a sub-field.
Fundamentals don't disappear. Rather, specialisations are added to them.

Why startups fail – the 8 patterns of failure (according to Eisenmann).
From the book: Why Startups Fail • Tom EISENMANN.
Installing Obsidian, adding my pre-existing notes folder and everything just working is a great #ux! An examplar for software interoperability.
Brilliant talk! The “debt” metaphor in “tech debt” is problematic. Code quality is best seen as a continuous process, which needs to be supported by frequent delivery, appropriate timeframes, continuous learning, transparency and advocacy.
Thought: CSS inheritance seems to cause similar maintainability issues to OO inheritance.
Good systems tend to have a lot of redundancy (“fall-backs”), and thus, have some inefficiency. Designers often seem to understand this better than engineers.