The Effective Software Engineer. How ICs at Every Level Can Leverage AI, Prioritize High-Value Work, and Lead Beyond Their Role Addy Osmani

Dostępność produktu

Produkt nie został jeszcze oceniony pod kątem ułatwień dostępu lub nie podano żadnych informacji o ułatwieniach dostępu lub są one niewystarczające. Prawdopodobnie Wydawca/Dostawca jeszcze nie umożliwił dokonania walidacji produktu lub nie przekazał odpowiednich informacji na temat jego dostępności.

Spis treści książki

• Preface
  • Becoming More than Just Efficient
  • What Is Effectiveness, Anyway?
  • The Right Things Right Spectrum
  • Why This Book, and Why Now?
  • What Youll Find Inside
  • Conventions Used in This Book
  • OReilly Online Learning
  • How to Contact Us
  • Acknowledgments
• 1. The Foundations of Effectiveness
  • Outcomes Versus Outputs: Solve the Right Problem
    • Understanding True Outcomes
    • The Spectrum of Engineering Impact
    • Developing Problem-Solution Alignment
  • Thinking Beyond Tasks: Long-Term Impact
    • Understanding Systemic Consequences
    • Strategic Prioritization in Practice
    • The Compound Effect of Quality
  • Productive Versus Effective: A Comprehensive Framework
  • Building an Effectiveness Mindset
    • Cultivating Strategic Thinking
    • Developing Influence Without Authority
    • Managing Effectiveness at Different Career Stages
  • Measuring and Developing Effectiveness
    • Personal Effectiveness Metrics
    • Organizational Context and Feedback
    • Continuous Improvement Practices
  • Setting the Foundation for Advanced Skills
• 2. Understanding the Fundamentals (Junior to Mid-Level Focus)
  • Clean, Maintainable, and Readable Code
  • Testing and Quality Mindset
  • Version Control and Debugging Discipline
    • Version Control (e.g., Git)
    • Debugging
    • Documentation and Note-Taking
  • Documentation and Communication (Even as a Junior)
• 3. Technical Depth Versus Breadth (Senior+ Focus)
  • The Value of Depth: Becoming an Expert
  • The Importance of Breadth: Being Versatile
  • Designing for Scale: Applying Depth and Breadth
    • Scaling Systems (Technical Depth)
    • Scaling the Team/Codebase (Breadth)
  • Managing Technical Debt: Depth Versus Breadth Perspective
  • How to Decide on Depth/Breadth Investment
• 4. Collaboration and Cross-Functional Influence
  • Working Effectively with Product and Design
  • Influencing Without Authority: Leading as an Individual Contributor
  • Managing Up: Collaborating with Management
• 5. Anti-Patterns That Limit Individual Contributor Effectiveness
  • Knowledge Silos: Share What You Know
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • The Hero Complex: Dont Be the Lone Savior
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Over-Engineering: When More Isnt Better
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Inability to Delegate: The Ill Just Do It Myself Trap
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Lack of Visibility: Make Your Work Known
    • Anti-Pattern Signs
    • Remedy
    • Communication Fix
    • Benefit
  • Analysis Paralysis: Overthinking Without Action
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Not-Invented-Here Syndrome: Rejecting External Solutions
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Perfectionism and Gold-Plating: Never Shipping
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Context-Switching Addiction: Lack of Deep Focus
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Scope Creep Enablement: The Inability to Say No
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Technical Debt Denial: Ignoring System Health
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Meeting Overload: Time Mismanagement
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Feedback Resistance: Closed to Input
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Tool Obsession: Chasing Shiny Objects
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Imposter Syndrome Paralysis: Fear-Driven Inaction
    • Anti-Pattern Signs
    • Remedy
    • Culture Fix
    • Benefit
  • Moving Forward
• 6. Career Growth and Leveling Up
  • How Promotions Work (and Why Tenure Isnt Enough)
  • The Unwritten Rules of Progression
  • Mid-Level Versus Senior Versus Staff: What Changes?
    • Mid-Level Engineer
    • Senior Engineer
    • Staff Engineer
  • Individual Contributor Versus Management: Two Paths
  • Advocating for Yourself: Navigating Promotions and Raises
    • Keep a Brag Document
    • Ask for What You Want
    • Use 360 Feedback
    • Be Patient but Persistent
    • Consider Lateral Moves for Growth
    • Stay Ethical and Humble
    • Know When Management/HR Processes Happen
    • Leverage Mentors or Sponsors
• 7. Leadership as an Individual Contributor
  • Leading Without Authority
  • Driving Large Initiatives Without Direct Reports
  • Mentorship and Sponsorship: Lift Others as You Climb
  • Ethical Considerations and Taking Responsibility
    • Foreseeing and Addressing User Risks
    • Handling Mistakes and Incidents
• 8. Strategic Thinking for Engineers
  • Identifying High-Impact Work
  • Aligning Engineering with Business Goals
  • Balancing Vision with Execution
  • Using Metrics and Data in Decisions
• 9. Avoiding Burnout and Sustaining Long-Term Success
  • Recognizing Burnout and Stress
  • Manage Your Energy, Not Just Your Time
  • Busting the 10x MythFocus on Team Effectiveness
  • Setting Boundaries and Saying No
    • Boundaries to Protect Personal Time
    • Boundaries at Work Too
    • Saying No to Tasks and Managing Perfectionism
    • Train Your Culture and Leverage Support
  • Cultivating a Sustainable Career
    • Lifelong Learning Without Burnout
    • Careers Are Marathons, Not Sprints
    • Pick the Right Environment and De-Stigmatize Mental Health
  • Fictional Example: From the Edge of Burnout to Balanced Success
• 10. Team-Level Effectiveness Anti-Patterns
  • Knowledge Silos: The Dangers of Having Domain Bottlenecks
    • Why Silos Form
    • The Dangers of Knowledge Silos
    • Signs of Knowledge Silos
    • How to Break Down Silos
    • Fictional Example: The One-Person Show
    • Beyond IndividualsSiloed Teams
    • Cultivating a Learning Culture
  • Rubber Stamping: Superficial Approvals That Degrade Quality
    • Why Is This a Problem?
    • Why Does Rubber Stamping Happen?
    • Consequences on Quality
    • How to Address Rubber Stamping
    • Fictional Example: The Quick OK
    • Balancing Efficiency and Diligence
    • Encourage Learning Through Reviews
  • Flaky Product Ownership and Just One More Thing: Engineering and Product Misalignment
    • Why Is This a Problem?
    • Why Product Ownership Can Be Flaky
    • How to Realign and Address This Anti-Pattern
      • Establish clear priorities and avoid mid-sprint scope changes
      • Improve communication and planning processes
      • Enforce a review of late changes (change control)
      • Maintain a backlog for next time
      • Strengthen the product-engineering relationship
      • Agree on definitions of done and acceptance criteria upfront
      • Adopt Agile ceremonies earnestly
    • Fictional Example: The Ever-Changing Roadmap
    • Engineering-Product Alignment
  • Low Bus Factor: The Risk of Team Dependencies
    • Signs of a Low Bus Factor
    • Why Low Bus Factors Persist
    • Strategies to Increase the Bus Factor
    • Fictional Example: Increasing the Bus Factor
    • Beware of Over-Specialization
    • Resilience as a Team Value
  • Ineffective Sprint Retrospectives: When Reflection Fails to Drive Action
    • Turning Reflection into Action
    • Fictional Example: Talk-but-No-Action Retros
    • Retrospectives as an Engine for Continuous Improvement
• 11. Thriving in Modern Work Environments
  • Remote Work Strategies: Thriving in a Distributed Environment
    • Key Strategies to Thrive Remotely
      • Over-communicate, but effectively
      • Use multiple communication channels for different purposes
      • Establish routines and boundaries
      • Foster human connection intentionally
      • Excel at asynchronous communication
      • Set up a productive workspace
      • Practice self-discipline and structure
      • Be mindful of tone and assume good intent
      • Invest in your communication skills
    • Fictional Example: Remote Reboot
  • Public Speaking and Communication Skills for Engineers: Becoming an Influential Technical Communicator
    • Common Obstacles for Engineers and How to Overcome Them
      • Stage fright or anxiety
      • Believing Im not a good speaker or Im an introvert
      • Not knowing how to simplify complex topics
      • Time constraints/not prioritizing communication
      • Thinking that communication is for managers
      • Underestimating the benefits
    • Building Communication Skills Beyond Speaking
      • Writing well
      • Active listening
      • Speaking up in discussions
      • Adapting to different audiences
      • Narrative and storytelling
    • Benefits of Strong Communication
    • Fictional Example: The Soft-Spoken Architect
    • The Value of Good Communication
• 12. The Future of Individual Contributors
  • Embracing AI as Your New Collaborator (Not Your Replacement)
  • The Hybrid Individual Contributor
    • T-Shaped Skills Revisited
    • Avoid Shallow in Everything, Deep in Nothing
    • Example Future Role
  • Continuous Learning and Adaptability
    • Balance New and Old
    • Lifelong Individual Contributor as a Viable Path
• 13. Practical AI for Effective Software Engineers
  • Where AI Shines (and Where You Still Need a Human Touch)
  • An AI-Enhanced Daily Workflow (That Compounds over Time)
    • Plan and Design with AI (Brainstorm, Then Draft an Architecture Decision Record)
      • Generate a decision brief
      • Pressure-test the requirements
      • Draft the architecture decision record
    • From Requirements to Backlog: Turning Product Requirements Documents into Work Items
    • Implement with a Tests First, Then Code Pattern
    • Code Review: AI as an Amplifier, Not a Gatekeeper
    • After the Code: Docs, Observability, and Communication
    • Fictional Example: Sams AI-Powered Workday
  • Feeding the AI Context: Getting Repository Awareness Right
  • Security First: Build AI into Your Secure Development Lifecycle
  • Privacy, Licensing, and Compliance: Guardrails You Cant Skip
    • Dont Feed the AI Sensitive Data
    • Watch Out for Licensing and Attribution Issues
    • Stay Aware of AI-Related Regulations Where You Operate
    • Align with Risk Management Frameworks (Theyre Helpful, Really!)
  • AI Agents: What They Can Do and How to Keep Them Tamed
  • Measuring Impact: How to Quantify AIs Effect Like an Engineer
    • Adoption and Behavior Metrics
    • Quality and Throughput Metrics
  • Prompt Patterns That Actually Work (Templates to Reuse)
  • Rolling AI Out to Your Team: A 90-Day Plan
    • Days 030: Establish Foundations and Guardrails
    • Days 3160: Scale Up and Train the Team
    • Days 6190: Optimize and Decide on Next Steps
  • A Checklist for Leaders: Evaluating AI Tools and Platforms
  • Bridging to What You Already Know (Connecting the Dots with Previous Chapters)
  • Building Consensus with Evidence: How to Have Effective Discussions About AI Adoption
• A Closing Note on Craft and Humanity
• Index

pokaż cały spis treści

ukryj recenzje