A project workshop for students in Surat

How we work

Scope first, hardware second. Before anything is ordered or written, we agree what the project has to demonstrate, which components it needs and what you will receive at the end. That conversation takes twenty minutes and prevents most of the problems that show up in week three.

Projects are built to be handled by a student, not only by whoever made them. Wiring is routed and terminated properly rather than left as loose jumpers, thresholds are adjustable and labelled, and firmware is commented so you can read it rather than just run it. If a sensor needs re-tuning the morning of your exhibition, you should be able to do it yourself.

What we tell students honestly

A project that works but cannot be explained will not survive a viva. So the handover covers the working principle, why each major component was chosen, and — importantly — what the limitations are. Knowing the limitations is usually what separates a confident viva from an uncomfortable one.

We will also say when a topic is a bad idea for your timeline, when a simpler approach would score better, and when a project is better done in simulation than in hardware. That is more useful than agreeing to everything.

Where we draw the line

We build models, kits and prototypes and teach students how they work. We do not sit examinations, impersonate students, or promise particular marks, and we expect students to understand what they are submitting and to follow their institution's rules on outside assistance. If your college requires disclosure of external help, disclose it.