Skip to content

A training partner for your team.

Build a team
that understands.
And delivers.

Hands-on technical training shaped around your people, your projects and the work they need to own.

I’m Ragav. Whether you’re onboarding new hires or growing experienced engineers, I work with you to understand their starting point, agree useful goals and build a programme around real practice.

Find a starting point Discuss your training needs ↗

Designed & delivered by Ragav Kumar V · Live online & onsite

curiosity goes in.capability comes out. ↗
Small steps.
A bigger leap.
ASK. EXPERIMENT. UNDERSTAND.↓
professionals trained
3,000+
batches delivered
100+
training experience
Since 2016
client organisations
18

Across teams & industries

Training delivered for
18 client organisations.

Explore the Sanlam programme ↓Read learner recommendations ↓

First, understand what matters to you.

Your team has a goal.
Let’s understand it together.

A topic is one part of the brief. The work ahead, your people and the time you have help shape a useful programme.

A starting point for our conversation

Start with their foundations and your first project.

We can explore what learners already know, where they need practice and the work they will join. That helps shape a connected route, with room to ask questions.

A few things we can explore

  • What will their first project ask of them?
  • Which foundations need attention?
  • How much time can the cohort spend learning?
Talk about this need

No finished brief needed. Share what you know, then choose email, WhatsApp or a call.

How we shape the programme

Designed and delivered by Ragav, with the route agreed for your team.

  1. Understand the team

    Your work goals, the learners’ starting point and where they need support. Bring the L&D and engineering perspectives into the conversation.

  2. Agree a practical route

    Connect the curriculum to useful practice. Discuss prerequisites, pace, delivery, available time and the evidence you want to review.

  3. Learn, review and carry forward

    Use questions, attempts and project reviews to discuss understanding and next practice. Agree the handover; learners can reach out afterwards for occasional clarification.

See a delivered programme ↓

A route we can shape together.

What does your team
need to build?

These paths show how the skills can connect. Choose a starting point; the stack, depth and pace follow your team’s needs.

Full-stack development

Connect the interface, the API and the data in a working application.

  1. Interface
  2. API
  3. Database
Explore example technologies
JavaScriptReactAngularNode.jsJavaSQL
View sample curricula

Cloud & DevOps

Take an application from a local machine to repeatable cloud delivery.

  1. Build
  2. Deploy
  3. Automate
Explore example technologies
AWSDockerTerraformKubernetesCI/CD
View sample curricula

Data engineering & AI

Turn raw data into useful insights and reliable pipelines. Add AI after the foundations.

  1. Collect
  2. Transform
  3. Use
Explore example technologies
PythonPandasDatabricksPySparkAzure Data FactoryAirflow
View sample curricula
Include the foundations when needed

New to the web? Start with the browser before the framework.

HTML, CSS & JavaScript See the foundations curriculum

The habits around the code

Test it. Review it. Improve it.

Connect testing, version control and productive developer workflows to the work your team is building.

GitJestCypressVitestLinux
Explore testing & developer workflows ↗
Looking for a particular technology?Find your starting point among 35 courses.

Each course includes prerequisites, a sample curriculum and a practical project. Scope, pace and duration are agreed for your team.

Corporate training

Build a learning path around your team's experience, technology stack, and project goals. Combine foundations, hands-on labs, and a capstone.

Focused workshops

Work through a specific skill or challenge with live demonstrations and practical exercises, from accessible interfaces to data pipelines and cloud deployments.

Project mentoring & curriculum design

Connect learning with implementation through guided projects, code reviews, and a curriculum adapted to the skills your team needs next.

Unsure which path fits?
Start with the work your team needs to do.

Talk through your requirement

The approach, in practice.

Every cohort
has its own story.

A starting point. A connected curriculum.
Practical work that brings it together.

Sanlam · South Africa · Live online

64days

From web foundations
to their own insurance apps.

JavaScript and React. Python and SQL. AWS, Docker and Terraform. A 64-day live online programme connected the pieces through a classroom movie app, then learner-owned insurance capstones.

UnderstandConnectBuild & present
Explore the programme
The connected stack: web interface, API and logic, data model, and cloud delivery.
A way to picture how the layers connect. The actual Sanlam sequence is described below.
  1. 01

    Web foundations

    JavaScript & React

    Learners began with the web layer, connecting new concepts through a shared movie application in the classroom.

  2. 02

    Connect the stack

    Python & SQL

    The programme continued into backend logic and data, linking those parts to the wider application.

  3. 03

    Deliver the application

    AWS, Docker & Terraform

    Cloud and delivery topics extended the learning beyond the web interface.

  4. 04

    Make it their own

    Insurance capstones

    Learners went beyond the classroom example to build their own insurance applications and present their work.

This is one programme, with its own curriculum and duration. Your team’s route is shaped around its starting point, goals and available time.

Hear from the learners ↓

The learning stays with them.

Small moments.
Lasting confidence.

Highlights from real recommendations.
Open a tile to read the complete message.

Ragav Kumar V speaking during a technical training session
Ragav Kumar V
Corporate trainer & mentor

The person you’ll work with.

Hi, I’m Ragav.
Let’s make it click.

I want to understand what your team needs before we choose what to teach.

We connect the work ahead with what learners already know, then agree a route they have time to practise. In the classroom, I use familiar stories, clear diagrams and small experiments. Questions and reviewed attempts help me see which ideas need another explanation.

I’ve been training teams since 2016, and I design and deliver the programme myself. My aim is to help learners understand what they’re building and explain their decisions. Afterwards, they can reach out for occasional questions and clarification.

Tell me about your team ↗Connect on LinkedIn ↗

Look closer at the teaching.

See how the learning
comes together.

Explore a connected project, teaching previews and a sample review. Each shows a part of the approach we can adapt for your team.

A programme is a journey.

One goal.
Every step connected.

Follow one example from an agreed route
to a learner’s own decisions.

01 / Agree the route

Give the learning a destination.

Start with what your team needs to build. Connect their starting knowledge, your technology stack and available time to a curriculum with a practical purpose.

A CONNECTED PROGRAMME01 / 04
  1. 1Route
  2. 2Idea
  3. 3Project
  4. 4Ownership

The goal shapes the curriculum

One application.
A reason for every topic.

  1. 01

    Build the interface

    JavaScript · React

    A catalogue with filters and saved films

  2. 02

    Connect logic and data

    Python · SQL

    An API and a data model for the same app

  3. 03

    Prepare it for delivery

    Cloud · containers

    Connect the application to its environment

Start with learner experience, your stack and available time. Agree the route before teaching begins.

Explore a React curriculum ↗

Representative teaching example · fictional film titles · scope shaped for each team

What makes the progress visible

An agreed curriculum, prerequisites and a shared classroom project.

02 / Understand the idea

Make one idea click.

Move from a familiar example to the concept behind it. Predict what will happen, try it and explain why. Here, a save button makes React state something you can see.

A CONNECTED PROGRAMME02 / 04
  1. 1Route
  2. 2Idea
  3. 3Project
  4. 4Ownership

A small idea, made visible

My movie shelf

Saved 0
Shelf mood
Illustrated poster for Night Lights
Adventure

Night Lights

Try the button. The interface remembers your choice.

const [saved, setSaved] = useState(false);

// A click changes state. React updates the UI.
setSaved(!saved);

Saved is false. Click to change the value and see the result.

Predict → try → explain. Then apply this idea to the next part of the project.

Representative teaching example · fictional film titles · scope shaped for each team

What makes the progress visible

Questions and small attempts show where the explanation needs another pass.

03 / Build the connection

Let the pieces work together.

Return to the same application as new topics arrive. State becomes a saved list. Data becomes a catalogue. In a full-stack programme, an API and database connect to the same interface.

A CONNECTED PROGRAMME03 / 04
  1. 1Route
  2. 2Idea
  3. 3Project
  4. 4Ownership

The ideas start working together

The film catalogue

Saved 0
Shelf mood
Illustrated poster for Night Lights
Adventure

Night Lights

Illustrated poster for Small Worlds
Drama

Small Worlds

Illustrated poster for The Long Way
Adventure

The Long Way

3 films shown · 0 saved

InterfaceAPIData

The interface runs here. In a full programme, learners connect the classroom app to backend logic, data and delivery.

Representative teaching example · fictional film titles · scope shaped for each team

What makes the progress visible

Working features, reviewed practice and reasoning behind the solution.

04 / Take ownership

Give the next decisions to them.

In a longer programme, learners move beyond the taught example to a capstone of their own. They choose a domain, connect the stack and present how and why it works.

A CONNECTED PROGRAMME04 / 04
  1. 1Route
  2. 2Idea
  3. 3Project
  4. 4Ownership

A new brief. Their decisions.

Build a catalogue
for your own domain.

Take the patterns you understand. Decide what your users need, design the data and explain your choices.

  • What should a user be able to do?
  • Which data and validation will it need?
  • How will you test and present the result?
BuildA working projectExplainDecisions and tradeoffsContinueA useful next step

Independent capstones suit longer programmes. Shorter programmes use focused practical work.

See how the Sanlam cohort made it their own ↑

Representative teaching example · fictional film titles · scope shaped for each team

What makes the progress visible

A project review, strengths, improvement areas and a useful next learning step.

A CONNECTED PROGRAMME01 / 04
  1. 1Route
  2. 2Idea
  3. 3Project
  4. 4Ownership

The goal shapes the curriculum

One application.
A reason for every topic.

  1. 01

    Build the interface

    JavaScript · React

    A catalogue with filters and saved films

  2. 02

    Connect logic and data

    Python · SQL

    An API and a data model for the same app

  3. 03

    Prepare it for delivery

    Cloud · containers

    Connect the application to its environment

Start with learner experience, your stack and available time. Agree the route before teaching begins.

Explore a React curriculum ↗

Representative teaching example · fictional film titles · scope shaped for each team

A glimpse inside the classroom.

See an idea click.
Then try it yourself.

Watch the explanation. Explore the slides. Try an activity. Three ways to take part in the same learning journey.

Watch a teaching moment

A familiar story. A new idea.

TEACHING ILLUSTRATIONFood → machine learning
A warm kitchen counter with a rice meal, ingredients and a recipe notebook, illustrating how ingredients become a finished meal.
THE FAMILIAR EXAMPLEEvery meal gives us clues.
Meal ASpice 1 · 10 minLiked
Meal BSpice 2 · 12 minLiked
Meal CSpice 5 · 8 minToo spicy
Meal DSpice 6 · 9 minToo spicy
01 / 04

Start with something we know.

A cook makes different meals and listens to the reactions. The ingredients and preparation give us clues about what people might enjoy.

First, make the idea easy to picture.
Motion is off. Use Next to explore.

Imaginary meal data illustrates the idea. Real models need suitable data and evaluation. This example draws on Ragav’s actual Scikit-Learn cooking analogy—another subject taught with the same known-to-unknown approach.

Next: explore the teaching slides

Explore the teaching slides

See how the explanation connects.

ORIGINAL TEACHING SLIDESPurpose → analogy → working process

Open any slide to see the detail. Zoom, pan and move through all three at your own pace.

ORIGINAL TEACHING SLIDE · 1 / 3

Start with the purpose.

100%
Purpose First teaching slide: raw data crosses a bridge to a useful model, beginning with why, then what is possible, then how.

Why are we learning this? Establish the destination before the tools.

Zoom, then drag or use the pan buttons. Arrow keys change slides.
Next: try a classroom activity

Try a classroom activity

Put the idea in your hands.

TRY A LITTLE OF THE LEARNINGClassroom previews

A little practice. A new way to see it.

CSS games, a JavaScript walkthrough and a small SQL exercise.

The interactive previews load as you reach this part of the journey.

Explore the JavaScript learning platform ↗

These are teaching previews across subjects. Your programme combines the concepts, exercises and project work that fit your team.

For the L&D team.

See the attempt.
Understand the next step.

A plan before training. Evidence while learning.
A useful handover afterwards.

Before: agree the goals
Discuss the starting point, practical goals and what your L&D team needs to see.
During: discuss the evidence
Review participation, attempts, practical work and explanations to identify the next practice.
After: carry the learning forward
Connect reviewed work to useful next steps and an agreed handover.

Reporting scope is agreed for your programme. The example below lets you inspect how one attempt can inform feedback and follow-up.

Participation, practice work, quiz signals and next steps contribute to a learning conversation.

A response starts
a conversation.

A completed exercise tells part of the story. The explanation, review and next attempt help show where understanding is growing.

  1. BeforeMake a plan
  2. DuringAttempt & review
  3. AfterCarry it forward

Follow one example from the brief to the next practice. Your reviewed answer carries into the handover.

Explore the learning platform ↗
THE COHORT NOTEBOOKIllustrative preview

A sample review flow, with no real learner data.

Agree what the team needs.

A useful learning review starts with a clear brief.

THE PRACTICE BRIEFJavaScript / value copying
Starting point
Learners can write simple expressions and declare variables.
Practice goal
Explain how primitive values behave when copied and reassigned.
Review scope

Look at the answer and the thinking behind it.

  1. Predict
  2. Explain
  3. Apply

Agree the starting point, the goal and what to review.

Curriculum, participation, attendance when requested, submissions and feedback can be included. Reporting scope is agreed for each programme.

Training around the world

Different places.
Shared learning.

From local classrooms to teams across borders. Follow the journey, or stop somewhere and look around.

Connections include online training and participant regions. Sanlam and CIC pins mark their head offices. Japanese CIC cohorts trained in Chennai. Place illustrations are decorative.

Online books & teaching notes

Open a guide.
Follow the idea.

A look at the explanations behind the training.
Explore Ragav's published learning notes.

Stories, examples and a path from familiar ideas to new concepts.

Browse all teaching notes ↗

Before we talk.

A little clarity.
A better beginning.

Still shaping the requirement?
That's a good place to start.

We know the challenge, but not the curriculum. Is that enough?

Yes. Bring the work your team needs to do, what learners already know and any time or delivery constraints. We can use that starting point to choose the foundations, practical work and review points together.

How do we agree what training should achieve?

We discuss your team’s starting knowledge and the work you want them to practise. Then we agree the curriculum, prerequisites, pace and how the work will be reviewed. Focused exercises suit shorter engagements; a learner-owned capstone can be scoped for a longer programme.

What cohort size works best?

Around 20 learners is ideal for individual attention. Cohorts of around 30 are also workable; the scope, pace and group size are agreed before training.

Can this work for experienced engineers?

Yes. The same approach can be adapted for engineers deepening their existing skills, moving to another stack or tackling a specific technical challenge.

How long does a programme take?

Duration depends on starting knowledge, the depth of the curriculum, contact hours and project goals. Shorter programmes use focused exercises; longer programmes can include an independent capstone.

Do you deliver online and onsite?

Both. Live online training is available to teams worldwide. Onsite delivery can be arranged in India or overseas, with travel and accommodation agreed during planning.

What support is available afterwards?

Learners can reach out through LinkedIn, WhatsApp or a call after training for occasional questions and clarification. Programme reporting and any handover are discussed upfront so your team knows what to expect.