Software engineering is getting a second material

At a New York fireside chat, Gergely Orosz and Michael Grinich discussed how AI is changing software engineering by introducing probabilistic model output as a second “material” alongside deterministic code, requiring engineers to balance reliability, cost, latency, and architectural choices. They argued that AI tools have raised overall productivity enough to reduce the advantage of individual early adopters, but have also enabled teams to pursue larger migrations and more ambitious projects while human coordination and customer-change constraints remain. The conversation described a weakening of traditional specialization boundaries among individual contributors, with product and platform engineering emerging as broader roles, while increased engineering throughput may create greater demand for technically capable product managers. Grinich said companies may need to build temporary internal agent tools to understand frontier capabilities, and both speakers emphasized that AI reliability depends on preexisting practices in testing, review, ownership, and observability rather than on adding agents alone. They also examined agent-first products, including machine-readable registration, temporary anonymous accounts, and constrained access models, arguing that businesses should serve agents as a new consumer class without abandoning human interfaces. Orosz concluded that engineers should seek demanding environments that build durable experience, support internships and entry-level opportunities, and recognize that AI is likely to shift engineering work rather than eliminate it, as organizations continue to build and rebuild systems using both deterministic and probabilistic components.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.