In a recent LinkedIn post, 🌀 Luca Rossi shared his weekly roundup of the most impactful articles and books he has consumed, offering insights into enhancing engineering team performance, strategic thinking, and effective management practices. Rossi’s practice of publicly sharing his reading list, he explains, fosters accountability for quality consumption and sparks valuable reader exchanges.
Key Insights from Rossi’s Reading List
Rossi’s curated list this week touches upon several critical areas for modern businesses, particularly within technology and engineering leadership. A prominent item is the book “Frictionless” by Nicole Forsgren and Abi Noda, which Rossi describes as a follow-up to Forsgren’s seminal work, “Accelerate.” The book focuses on identifying and removing impediments that hinder the progress of engineering teams.
“I just finished reading the new book by Nicole Forsgren (co-author of Accelerate) and Abi Noda (co-founder of DX) about removing barriers that slow engineering teams down. I loved it, and it feels like the perfect follow up to Accelerate.”
As 🌀 Luca Rossi highlights, the core idea of “Frictionless” aligns with improving operational efficiency by systematically addressing bottlenecks. This focus on reducing friction is a recurring theme in discussions about high-performing technology organizations.
Strategic Thinking and Serendipity
Another piece that caught Rossi’s attention was Jason Roberts’ article, “Increasing Your Luck Surface Area.” Rossi emphasizes the author’s perspective that luck is not purely random but is influenced by proactive efforts and communication.
“Your luck is not random, it’s a function of doing things + telling people about them. The more you do, and the more you share, the more serendipity finds you.”
According to 🌀 Luca Rossi, this suggests that individuals and teams can actively cultivate opportunities for positive outcomes by increasing their activity and visibility. This concept underscores the importance of both execution and effective communication in achieving success.
Leadership Models and Code Quality
Rossi also featured James Stanier’s application of Charlie Munger’s “Invert, Always Invert” mental model to engineering leadership. This approach encourages leaders to consider the causes of failure to avoid them, a perspective Rossi found highly practical.
Furthermore, an article titled “How Good Engineers Write Bad Code at Big Companies” by Sean Goedecke resonated with Rossi. He points out that the article connects poor code quality and high turnover to systemic issues, such as incentives prioritizing rapid shipping over long-term maintenance, rather than a lack of talent.
“Great take that connects the dots between bad code, short tenure, and incentives that prize shipping rather than maintaining. That’s how you get great engineers to write bad code. It’s a systemic issue, not a talent one.”
In 🌀 Luca Rossi’s view, this distinction is crucial for organizations seeking to improve code quality, suggesting that solutions must address underlying incentive structures and processes.
Revisiting Manager READMEs
Finally, Rossi highlighted Camille Fournier’s updated take on “Manager READMEs.” While initially critical, Fournier revisits the concept, arguing that while not inherently bad, the effectiveness of Manager READMEs can be significantly improved by decentralizing information into existing processes and ceremonies, making them more actionable and less focused on the individual manager.
🌀 Luca Rossi concludes his post by inviting readers to share their own valuable reads, fostering a collaborative environment for continuous learning.
📝 About This Content
This article is based on insights shared by 🌀 Luca Rossi on LinkedIn.
📅 Originally posted on December 11, 2025 | View original post on LinkedIn →