liveBook · Manning

Lifelong learning

As explained in Think Like a Software Engineering Manager

Continuous learning is the ongoing acquisition and application of knowledge and skills through study, practice, and reflection.

A new engineering manager may know how to solve technical problems but still need practice delegating, communicating with stakeholders, and helping others grow. Lifelong learning means repeatedly identifying what you need to learn, gaining knowledge or skills, applying them, and adjusting based on feedback. It is not limited to a transition period or to keeping up with technology. section 2.4.2 section 15.2

Make learning a manageable cycle:

  • Set a goal and find the gap. Decide whether you need broader knowledge or deeper skill, then turn that choice into a specific action. section 15.2
  • Protect time to learn. Use a course, reading, a mentor, or training offered at work; ask for resources when you need them. section 2.4.2 section 15.6
  • Put the lesson to work. Practice a leadership skill such as delegation, or use a small pet project to explore a technical interest. section 15.2 section 15.3.3
  • Seek feedback and revise. Regular input from engineers, a manager, and cross-functional partners helps reveal what is not working before it becomes a surprise. section 2.4.2

Learning also belongs in the team's work. One-on-ones and career discussions can connect an individual's aspirations to stretch goals, onboarding, or training. Code reviews, knowledge-sharing sessions, and mentorship give engineers ways to learn from one another. Development can support both stronger skills and retention, but the opportunity should fit the person rather than follow a single path for everyone. section 8.4.1 section 12.2.1

Learn against a real need

An engineering manager interested in artificial intelligence built a spare-time chatbot to explore whether frequent customer inquiries could be automated. Experimenting with Amazon Lex, AWS Lambda, and Amazon CloudWatch developed technical knowledge while testing a possible workplace use. The project was a learning exercise, not a requirement that every manager keep coding outside work. section 15.3.3

Choose one skill that would help you or your team now. What small action would let you practice it, and whose feedback would tell you what to change next? section 15.2 section 2.4.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Outlines a practical cycle of goals, learning actions, application, and feedback, without prescribing a fixed schedule or curriculum.
Examples
Uses introductory machine-learning training, an internal role transition, and a chatbot pet project as concrete development cases.
What it assumes
Assumes an engineering-management context but gives accessible starting actions, including scheduled study, support requests, and hands-on practice.
What you can do after
Practice/perform iterative learning by choosing a skill gap, applying a learning activity, and using feedback to adjust.
How it connects
Links learning to delegation, feedback, mentoring, career development, code review, and knowledge sharing.
Cover of Think Like a Software Engineering Manager
liveBookmanning.com
Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

Compare how 3 books explain lifelong learning →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.