liveBook · Manning

Training

As explained in Lead Developer Career Guide

The process of acquiring knowledge, understanding, or ability through study, experience, or instruction.

Training develops a specific skill through instruction and practice. In technical training, the learner works toward doing something—not just recognizing the terms. A trainer can provide instructions, hands-on work, and feedback, while the learner tests whether they can apply the skill independently. section 2.1.5 section 9.1.1

Good training starts with the learner’s goals and clear learning objectives. It need not look the same for everyone: some people want instruction before a task, while others learn best on the job. To find a useful format, try a video and written documentation on the same topic, then compare what you understand and retain. section 2.1.5 section 4.1.1

Turn instruction into ability with a repeatable routine:

  • Choose a specific objective and schedule practice at a time that suits you; even 30 minutes a day can be useful when you are consistent. section 3.4.4
  • Apply the idea in an exercise or small project. Check whether you can implement it yourself, and note which parts need more study. section 4.1.1
  • Share what you learned through a post, video, talk, or answer. Explaining a solution can help other developers—and give your future self a record to revisit. section 3.4.4 section 4.1.4

Practice a new technology

Build a simple timekeeping application, then rewrite it as you learn a new language, database, or framework. Compare how confidently you can follow instructions, read sample code, and implement each concept on your own. section 4.1.1

Training and mentoring can overlap, but they serve different needs. A trainer usually concentrates on a defined competency and may have little contact with students afterward. A mentor may meet regularly to work through problems and career decisions. If you teach, ask learners how they might solve a problem before giving the answer; the dialogue helps them retain knowledge and practice critical thinking. section 9.1.1 section 2.1.5

Expect progress to take time. When a deadline calls for a quick answer, learn enough to solve the immediate work problem and return later for a fuller understanding. Treat mistakes as information for the next attempt rather than a reason to stop practicing. section 3.4.4 section 11.5.3

How Lead Developer Career Guide covers it

How deep it goes
Explains learner goals, format selection, practice, and feedback, but does not provide a detailed curriculum-design procedure.
Examples
Uses video-versus-documentation comparison, a rewritten timekeeping application, and regular 30-minute practice as concrete tactics.
What it assumes
Assumes an interest in developer skills while explaining how to select learning formats and begin with a small exercise.
What you can do after
Practice/perform skill development by choosing an objective, trying a format, applying the skill, and checking what needs more study.
How it connects
Connects instructional design and hands-on practice to mentoring, self-assessment, and knowledge sharing.

Also explained in

Compare how 24 books explain training →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.