Skip to main content
Codexway

Consulting and training

Training and coaching for technical teams

I train your teams on your own projects, with exercises drawn from your code. Sessions end with usable output, not a satisfaction survey.

Request a quoteGet in touch

What it covers

Useful training happens on the company's code. Participants work on a problem they know, with their constraints, conventions and tools. By the end of the session, part of the work is genuinely delivered and the skills are immediately applicable.

Formats range from a half-day framing session to several weeks of support. For development, I favour short, repeated modules separated by periods of real practice, rather than a full week of which half is lost.

Content tailored to your context

The programme is built after a technical conversation and a review of your codebase. Examples, exercises and reviews use your files, your business rules and your past incidents, which makes the training directly transferable.

  • Programme tailored after reviewing your codebase.
  • Exercises on real cases instead of generic examples.
  • Collective code reviews with reasoned commentary.
  • Materials handed over and reusable by the team.
  • Skills assessed through output, not a questionnaire.

Problems addressed

  • External training never applies once people are back at work.
  • The team lacks shared reference points on testing and quality.
  • New joiners take months to become autonomous.
  • Good practices are known but not actually practised.
  • Production pressure slows down skill development.

Expected benefits

  • Skills immediately applicable to your projects.
  • Measurable autonomy gains on the targeted practices.
  • Materials the team can reuse and pass on.
  • A codebase improved during the training itself.
  • A shared vocabulary between developers, testers and operations.
  • A format you can adjust to production constraints.

Method and steps

  1. 1

    Needs assessment

    Interviews with technical leads and code review to identify practices to strengthen and the team's recurring difficulties.

  2. 2

    Programme design

    Defining modules, exercises and learning objectives, split in a way that fits production constraints.

  3. 3

    Sessions and practice

    Alternating short sessions with periods of real practice, including collective code reviews and reasoned corrections.

  4. 4

    Assessment and handover

    Measuring skills from the produced code, adjusting the programme, handing over materials and identifying the next areas to strengthen.

Deliverables

  • Training programme tailored to your technical context.

  • Session materials handed to the team.

  • Exercises and case studies drawn from your codebase.

  • Documented collective code reviews.

  • Skills assessment with strengths and areas for progress.

  • Recommendations for practices to consolidate over time.

Technologies used

  • Java
  • Spring Boot
  • Angular
  • GitHub Actions
  • JUnit 5
  • Testcontainers
  • Playwright

Frequently asked questions

Is remote training possible?

Yes, by video with screen sharing and paired exercises, or on site if you prefer. For hands-on modules, two three-hour remote sessions are often more effective than one continuous day.

Which topics do you cover?

Java and Spring Boot, testing and quality, Angular, containerisation, delivery pipelines, application architecture, security fundamentals and observability. The programme is built from your needs, not a fixed catalogue.

How do you measure learning?

Through the code produced during and after the training, and the team's ability to apply the practices unaided. A satisfaction survey says nothing about skills actually acquired.

Related case studies

Build a programme

Tell me the team size, the technologies in use and the difficulties you face. I will propose a tailored, progressive programme.

Build a programme