Ben Darfler

You need to think about both: "Push communication ensures clarity and direction from leadership, aligning teams with the overarching goals. … Conversely, pull communication empowers team members to proactively seek information, driving bottom-up innovation."

- Principle 1: Citations are the Currency of Trust - Principle 2: Designing for the Editor State - Principle 3: The Power of ‘I Don’t Know’

Mentorship programs that develop theory-building skills

I appreciated the 7 practical suggestions that ground what can be a fluffy topic: - Demonstrate Leadership Commitment and Role Modeling - Encourage and Reward Collaboration - Promote Psychological Safety - Implement Blameless Postmortems - Strive for Information Transparency and Clarity - Celebrate Innovation, experimentation - Foster Continuous Learning

I appreciated the set of patterns (very on brand for thoughtworks): • Knowledge Priming • Design-First Collaboration • Context Anchoring • Encoding Team Standards • Feedback Flywheel

I appreciated the terms "attended" and "unattended" parallelism as well as this observation: "The engineer’s job … [is] splitting into two distinct halves … building the environment … [and] managing the work"

We are shifting from generating more code to verifying more code.

Nice framing for giving agents more programmatic feedback and needing less human feedback.

I love where this ends: "The next level is humans directing agents to manage and improve the harness rather than doing it by hand."

Another excellent strategy article from Jason Cohen

Companies constantly overthink goals: "Goals are a communication tool. That’s it."

Read past the title and stay for the leaning on Deming in an attempt to see around the AI corner.

I'm collecting perspectives on a vibrant software engineering practice for the AI future. I appreciate the thinkers who are finding a middle way between the hype and the doom. -

"Don’t start with product, features, ideas, or hypotheses. Start with a good understanding of target audiences’ tasks, experiences, and pain points. Be solution-agnostic early in your process. Avoid the feature factory and order taking."

Ever since coming across "Demanding and Supportive" a few months ago, I find myself thinking about it and referring back to it regularly.

Regular refresher on the distinction between product output, customer outcomes, and business impacts.

I love when Buddhist content crosses over into leadership content. This maps nearly 1:1 with RAIN - Recognize, Accept, Investigate, Nurture