Contact | Shiksha Tech

Clarifications and Definitions

Before you start a module, a few terms are worth pinning down. What follows is not legal boilerplate — it is the working vocabulary we use across the platform, so that a lesson, a forum thread, and a support reply all mean the same thing when they say "module", "track", or "exercise". If a term here contradicts something you read elsewhere on the site, this page wins.

Module vs. track A module is a single self-contained unit: one topic, one set of exercises, one review checkpoint. A track is a sequence of modules that build on each other, for example the backend track or the frontend track. You can take a module on its own. A track assumes you finish it in order, because later modules reuse code and concepts from earlier ones.
What "beginner" means here We label a module beginner when it assumes no prior code, only that you can install software and follow written steps. It does not mean the module is short or easy. Some beginner modules take several weeks of regular practice, and the exercises get harder as you go.
Exercises are not graded Exercise solutions are checked against expected output and common failure cases, but there is no score and no ranking. The point is to find out where your understanding breaks, not to compare you with other learners. If an exercise passes but you cannot explain why, treat it as unfinished.
Code samples and version drift Every code sample is written for a specific language version, noted at the top of the lesson. Libraries change, and a snippet that ran cleanly two years ago may need a small adjustment today. When you hit that, the error is usually in the dependency, not in your setup. Check the version note first.
Support scope We answer questions about the material, the exercises, and the platform itself. We do not debug your personal project, review production code, or advise on hosting, hiring, or contracts. If your question is outside the curriculum, we will say so plainly rather than guess.
Certificates and completion Finishing a track produces a record of the modules you completed and the checkpoints you passed. It is a summary of your work on this platform, not an accredited qualification, and it does not replace a formal degree or a professional certification from another body.

Book a walkthrough of a module

Tell us which part of the curriculum you want to see in action. A short session with one of our instructors, focused on the scenario you pick, usually answers more than a page of text.

Before you send, it helps to know that the policy and terms pages describe how we handle your details and what the platform expects from learners.

Reaching the Shiksha Tech team

Questions about module order, prerequisites, or where a topic fits in the curriculum usually get answered the same day. Write, call, or stop by during office hours. If your question concerns a specific track, mention it in the subject line so it reaches the right tutor.

Address

Eberlplatz 193
2232 St. Johann im Pongau

Phone

0650 6119054

info@shikshapatra.com

Office hours

Monday to Thursday, 09:00 - 17:00
Friday, 09:00 - 13:00
Closed on public holidays in Salzburg.

How to get a useful answer faster

Most messages we receive fall into a few categories. Picking the right channel saves a round trip.

Curriculum and module order - email with the track name and the topic you are stuck on.
Enrollment and access - call during office hours; we can check your record while you are on the line.
Technical issues with exercises - email a short description and the exact error text, no screenshots needed.
Visits and campus questions - come by Eberlplatz 193; someone is at the desk on weekday mornings.

We do not run a contact form. A direct email or a phone call reaches a person, not a queue.