This article covers highlights from a podcast conversation about recent advancements in AI models, particularly Google's new vision-capable LLMs. It discusses technical features like parameter efficiency and multi-modal capabilities, as well as ongoing challenges in running local models effectively.

• Google released Gemma 4 reasoning models (2B–31B params), with the E2B/E4B variants using Per-Layer Embeddings to boost on-device efficiency without growing total parameter count, and all versions handle text, images, and audio.
• Willison's hands-on testing found the smaller Gemma models worked well but the largest 31B model repeatedly errored out.
• A supply chain attack hit the Axios HTTP client via a malicious npm dependency, underscoring open-source package security risks.
• Willison argues efficient code will dominate AI deployment due to economic incentives, based on his experience running these models locally versus via Google's AI Studio API.

The article explores the definition of an engineer and what engineering truly entails, especially in the context of advancing AI technology. It emphasizes that engineering is about taking the right actions in the right sequence to achieve various intentions, highlighting the importance of clarity in project goals and the art of sequencing tasks.

• An engineer is defined as someone who takes the right actions in the right sequence to achieve a set of intentions, not someone who builds physical things—making software engineers legitimately engineers.
• Engineering projects have multiple simultaneous intentions (resources, stakeholders, users), and failing to articulate them causes teams to build the wrong product or misalign with goals.
• Sequencing matters as much as choosing the right actions—order of operations determines success, and sequences nest recursively within larger sequences (illustrated via the hand-washing example).