Technical mentoring works best when it develops both engineering judgment and the person using it. Daniel Llach’s January 2, 2025 article, “Technical Mentoring: The Art of Seeing The Whole Person,” argues that a mentor should make room for trust, confidence, autonomy and life beyond work—not only code reviews and architecture discussions. His advice is practical professional guidance, not independently tested evidence of outcomes.
Why technical skill is only part of mentoring
A developer’s work is shaped by more than technical knowledge. Confidence, communication, personal circumstances and the freedom to make decisions can all affect how someone participates and grows. Llach’s central point is that a mentoring relationship should account for that whole person rather than treating the mentee as a set of coding skills to improve.
As an Amazon Associate I earn from qualifying purchases.
This does not mean avoiding technical topics. It means letting technical development sit alongside questions about what the mentee wants to learn, what feels difficult, and where they need more room to act. In Llach’s framing, conversations that are not about code can still support technical growth by helping build the trust and judgment that make independent work possible.
How to set a mentoring rhythm that can change
Llach proposes starting with weekly 30-minute meetings, then moving to biweekly sessions as the mentee develops, and eventually holding monthly, deeper conversations while staying available between them. These are suggested practices, not a universal schedule. The useful principle is to revisit the cadence as the mentee’s needs and independence change.
#1 Best Overall
Keep meetings open enough for the mentee to set priorities. A session can cover a technical challenge, a decision they are unsure about, or something affecting their work. The mentor can help make space for those topics without assuming every meeting needs a fixed agenda or a code-focused outcome.
How to transfer judgment instead of supplying answers
Direct advice can help with an immediate problem, but mentoring also offers a chance to show how decisions are made. Llach recommends first making the mentor’s reasoning visible, then shifting toward questions that help the mentee examine options and reach a conclusion themselves.
- At the start: Explain how you are assessing the problem, including the trade-offs behind a recommendation.
- As confidence grows: Ask what options the mentee sees and what evidence or risks matter to them.
- With greater independence: Let the mentee lead the reasoning and use your input as a sounding board when needed.
The aim is not to withhold useful answers. It is to avoid making the mentor the permanent decision-maker. A mentee who can explain and defend a choice is better positioned to handle the next unfamiliar problem without waiting for approval.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesHow to increase responsibility without removing support
Responsibility can grow in stages. Llach describes moving from joining technical discussions, to letting the mentee lead while the mentor remains available as backup, and finally to joining only when asked. That progression gives the mentee practice while preserving a route to help.
- Start with lower-risk work. Choose tasks where the mentee can practice making decisions without an outsized cost if they need to revise them.
- Increase complexity or visibility gradually. Invite the mentee to lead a discussion, contribute to an architecture conversation, or present work as their readiness develops.
- Agree on the safety net. Clarify when the mentor will observe, when they will step in, and how the mentee can ask for support.
- Give credit for contributions. Recognize the mentee’s work publicly where appropriate, rather than treating visibility as a reward reserved for people who already have senior titles.
Support should enable the mentee to take ownership, not quietly take the work back at the first sign of uncertainty.
How to account for life outside work
Llach’s approach treats personal context as relevant to professional development. He recommends supporting personal milestones and time-off requests, and assessing value delivered rather than hours worked. In practice, that means listening without demanding personal disclosure and responding to the information a mentee chooses to share with respect.
A mentor is not a substitute for a manager, therapist or workplace policy. But a mentoring conversation can acknowledge that people have lives beyond their tasks, and can help a mentee think through boundaries, workload or a professional challenge without implying that commitment is measured by constant availability.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat growth can look like beyond completed tasks
Technical output matters, but Llach suggests watching for changes in how the mentee approaches work and colleagues. His examples are observations to guide a conversation, not a validated measurement system or a scorecard.
- Taking initiative or proposing solutions instead of waiting for instructions.
- Becoming someone colleagues turn to for advice.
- Communicating with more confidence and taking on challenges willingly.
- Making more considered decisions about work-life balance.
These signs are most useful when discussed in context. A quiet person need not become more outspoken to be progressing, and a busy stretch of work does not by itself demonstrate growth. Ask the mentee what feels different to them and what kind of challenge they want next.
What Llach’s story illustrates—and what it cannot prove
Llach recounts recommending a technically strong candidate whose English was still developing, despite a manager’s hesitation. He says he supported her on English-language calls; over the following two years, she became a trusted contributor and was promoted to technical lead. Later, she told him she planned a month-long trip to Japan and described seeing autumn leaves for the first time.
The anecdote illustrates the author’s emphasis on seeing a person’s strengths and circumstances together. It is one account from the author, however; it does not independently verify the events or establish that his mentoring caused the reported career progression.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
A practical way to put the approach into practice
- Ask what the mentee wants from the relationship and agree on a meeting rhythm you can adjust.
- Use some conversations to understand priorities and obstacles, not just review technical work.
- Explain your reasoning, then make room for the mentee to reason through decisions aloud.
- Offer progressively more ownership and visibility, with clear, dependable backup.
- Notice multiple forms of growth and invite the mentee to define what progress means to them.
- Respect boundaries and personal context without making assumptions about what someone should share.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
