~/mentoria

1:1 technical mentoring, online

A recorded course does not review your code.

One-to-one mentoring with someone who has lived software for over 10 years: architecture, career and real code review.

Apply for mentoring How it works
10+ years building software that runs in production
3 active consulting clients today
30 hiring processes seen from the inside
0 recorded lessons, group sessions or fake LGTMs

Who it is for

One session a week changes the year. The path depends on where you are.

Junior to mid-level

  • Leave the copy-from-Stack-Overflow loop without understanding why
  • Write code other people can maintain
  • Defend your own PR without sweating

Mid-level to senior

  • Think about the whole system, not just the sprint task
  • Architecture, scale and trade-offs without guesswork
  • Positioning to negotiate your next salary
Not for you if:
  • you want a wall certificate
  • you want a magic formula without work
  • you want someone else to solve the PR

How it works

  1. Diagnosis

    An initial conversation to map where you are, what is stuck and where you want to get to.

  2. Plan

    Concrete goals in your stack and your reality. No generic modules.

  3. Sessions

    1:1 video calls, with your screen on the table, at the pace we agree.

  4. Continuous review

    Code, PRs and project decisions reviewed between one session and the next.

What happens in a session

Code

PR review on your real codebase, guided refactoring and the practices that actually matter.

Architecture

System design, scalability and when not to follow the trend of the moment.

Career

Salary, negotiation and a growth plan with the real market on the table.

Positioning

LinkedIn, portfolio and GitHub set up so the people hiring can find you and want you.

Where the interview bites

Interviews do not test syntax. They test decisions — and that is where good developers freeze.

record or class here, and why? A twenty-second question. And the scene repeats: the person can code, can solve the problem, just cannot explain the decision — because nobody ever rebuilt the modern C#/.NET mental model with them.

That is not a lack of ability. It is also not a lack of material: material is free, everywhere. What is missing is someone challenging your decisions with your code on the table.

In modern .NET, the question behind every question is always the same — why this path and not the other one?

  • Nullable Reference Types — the ? on the type is not decoration: it is the compiler warning you about null before it becomes an incident.
  • record, class or struct — which model of equality and mutation the data asks for.
  • Pattern matching and Span — where each one truly pays off, and where it only adds noise.
  • async/await — not memorising where the keyword goes: understanding I/O, state, and why Task.Result deadlocks.
  • Minimal APIs — what modern ASP.NET Core gained, and when a controller is still the right answer.
  • LINQ — deferred execution, N+1 and the query that passes the test and kills production.

Swap the stack — PHP, Laravel, Node, Java, React — and the question stays the same. The vocabulary changes, not the trap.

30 hiring processes seen from the inside made that clear: the question that decides is never "what does it do?", it is "why did you do it this way?". That is the kind of decision we work on in the sessions — on your stack, on your code.

The market is broken. You are not.

A seven-stage process ending in ghosting, a senior role with a 2015 salary. I lived that side of the table recently, with more than 10 years behind me. What unblocked it was not another course: it was positioning what I already knew how to do. Today I live off consulting, and that is the path I help you build.

Everton Lima, has deployed on a Friday and survived

Straight answers

Is it a recorded course?

No. One-to-one sessions, live, on video, with your screen on the table. You already have enough recorded courses.

How much does it cost?

It depends on the frequency and the plan, which we define in the diagnosis. The proposal arrives clear, and you decide with no pressure.

Do I need to be on your stack?

No. The base is conceptual, the example is your code. Up close I work with PHP, Laravel, Node, .NET, Java, React and Next.js.

I am a junior. Is it too early?

Too early is letting junior habits become senior standards. The sooner your code is challenged, the faster the level goes up.

Does it work if I do not work as a developer yet?

If you already write code, in an internship, freelance or your own project, yes. From absolute zero, not yet.

Is it in person?

Online, from anywhere. Time zones we arrange.

Let us talk

Two minutes to fill in. I read it and answer it myself.

  1. You fill it in
  2. I read it and answer personally
  3. We schedule the diagnosis

Prefer WhatsApp? +55 12 99171-3559