# Culture & Methods Published articles for Culture & Methods. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building an Internal Developer Platform with Artificial Intelligence DevFeed: [Building an Internal Developer Platform with Artificial Intelligence]() Original publisher: [Read original article]() Author: Ben Linders Published: 2026-09-17T11:11:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [internal developer platform](), [AI Development](), [AI search](), [agent observability](), [OpenTelemetry](), [telemetry]() Tags: [agent](), [agents](), [artificial-intelligence](), [culture-methods](), [developer-experience](), [developer-platform](), [distributed-tracing](), [guardrails](), [internal-developer-platform](), [logging](), [logs](), [metrics](), [news](), [opentelemetry](), [platform-artificial-intelligence](), [platform-engineering](), [prometheus](), [traces]() ### AI overview This news article covers a KubeCon presentation about using AI agents as an internal developer platform. It discusses semantic search across sources such as Git, Slack, Jira, repositories, pull requests, and wiki pages; guardrails for controlling actions; and logs, metrics, and traces for understanding agent behavior. The speakers also describe OpenTelemetry conventions for GenAI and related observability tools. ### Source excerpt Agents are becoming the new developer platform, using semantic search with data from tools like Git, Slack, and Jira for context. Things to consider are setting guardrails to block or allow things, and using logs, metrics, and traces to understand agent behavior. By Ben Linders ## Presentation: Teaching Engineers, Trusting AI: How Education Enabled Autonomous Code Review DevFeed: [Presentation: Teaching Engineers, Trusting AI: How Education Enabled Autonomous Code Review]() Original publisher: [Read original article]() Author: Sarah Deitke Published: 2026-09-16T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [Artificial Intelligence](), [Code review](), [Pull Request](), [Tooling](), [engineering-culture](), [observability]() Tags: [adoption](), [agile](), [ai](), [ai-ml-data-engineering](), [architecture-design](), [artificial-intelligence](), [automated](), [automation](), [autonomous](), [case-study](), [code-review](), [code-reviews](), [culture](), [culture-methods](), [developer](), [developer-experience](), [development](), [duolingo-ai-literacy-code-review](), [infoq](), [metrics](), [ml-data-engineering](), [observability](), [pairing](), [presentation](), [qcon-london-2026](), [qcon-software-development-conference](), [transcripts]() ### AI overview Sarah Deitke presents Duolingo's approach to cultural AI adoption through internal AI literacy workshops, observability dashboards, and safe AI guardrails. The presentation includes a case study on redesigning code review with an automated PR risk-assessment bot and reports faster delivery without increased defect rates. ### Source excerpt Sarah Deitke discusses how Duolingo drives cultural AI adoption beyond tooling access. She explains their internal AI literacy workshops and observability dashboards, then shares a case study on redesigning code review using an automated PR risk-assessment bot. Deitke demonstrates how pairing targeted developer education with safe AI guardrails speeds up delivery without increasing defect rates. By Sarah Deitke ## Presentation: Lead Without a Ladder: How I Climbed Into Engineering Leadership DevFeed: [Presentation: Lead Without a Ladder: How I Climbed Into Engineering Leadership]() Original publisher: [Read original article]() Author: Pauline Jepp Published: 2026-09-15T09:10:00Z Content type: opinion Language: en Sources: [InfoQ]() Topics: [engineering-leadership](), [systems]() Tags: [alignment](), [careers](), [chief-engineer](), [culture-methods](), [engineering](), [engineering-leadership](), [infoq](), [leadership](), [mentorship](), [presentation](), [qcon-san-francisco-2025](), [qcon-software-development-conference](), [safety](), [team](), [transcripts](), [trust]() ### AI overview Pauline Jepp discusses how systems thinking, rock climbing, and flocking behaviors inform engineering leadership. She covers balancing team autonomy with alignment, supporting mentorship and other invisible work, and transitioning from hands-on engineering to leadership while maintaining organizational trust and psychological safety. ### Source excerpt Pauline Jepp explains how systems thinking, rock climbing, and flocking behaviors apply to engineering leadership. She shares strategies for balancing team autonomy with alignment, supporting invisible work like mentorship, and navigating transitions from hands-on engineer to engineering leader while maintaining organizational trust and psychological safety. By Pauline Jepp ## Beyond Autonomous Teams in Software Product Development DevFeed: [Beyond Autonomous Teams in Software Product Development]() Original publisher: [Read original article]() Author: Ben Linders Published: 2026-09-10T10:29:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Self-organizing Team](), [Software Engineering]() Tags: [agile-conferences](), [autonomous](), [autonomous-software-teams](), [business-value](), [complex-systems](), [complexity](), [conference](), [culture-methods](), [delivering-value](), [management](), [networking](), [news](), [product-development](), [scrum](), [self-organizing-team](), [teamwork]() ### AI overview A conference talk argues for moving from product-focused autonomous teams to value centers, with organizational design shaped by value and its dependencies. It frames agency and coherence as a trade-off and uses the Viable Systems Model to suggest five questions for teams. ### Source excerpt Autonomous teams are an article of faith in modern software development. The shape of our value determines what we can do; it determines our trade-offs between agency and coherence. We all have a purpose, and we all have agency to do something, hence the suggestion is moving from product focus to value center thinking. By Ben Linders ## Presentation: Accelerating Performance by Incrementally Integrating Rust Into Existing Codebase DevFeed: [Presentation: Accelerating Performance by Incrementally Integrating Rust Into Existing Codebase]() Original publisher: [Read original article]() Author: Lily Mara Published: 2026-09-10T09:34:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [rust refactoring](), [Refactoring](), [Integration testing]() Tags: [architecture](), [cost](), [culture-methods](), [design](), [development](), [engineering](), [infoq](), [infrastructure](), [performance](), [presentation](), [python](), [qcon-san-francisco-2025](), [qcon-software-development-conference](), [refactoring](), [rust](), [rust-refactoring](), [system-programming](), [testing](), [transcripts]() ### AI overview A presentation on incrementally refactoring Python bottlenecks into Rust with PyO3 to improve function-level performance, retain integration testing, and reduce infrastructure costs. ### Source excerpt Lily Mara explains how to avoid high-risk software rewrites through incremental FFI refactoring. She shares how engineering teams can replace Python bottlenecks with Rust via PyO3, demonstrating how to achieve dramatic function-level speedups, seamless integration testing, and meaningful infrastructure cost savings without microservice overhead. By Lily Mara