Common Questions

All the common Singapore curriculum languages, and most production stacks. Python (CS1010, CS1101S, DSA1101, FYP work), Java (CS2030S OOP, NTU SC1003), C and C++ (CS2100, CS2106 systems), JavaScript and TypeScript (web modules, React projects), R (data-science modules, ggplot2), SQL (CS2102 databases, BT2102), plus HTML and CSS for any frontend coursework.

Frameworks: React, Node.js, Express, Flask, Django, Spring Boot, FastAPI, plus the data stack (pandas, NumPy, scikit-learn, PyTorch, TensorFlow). For deployment I cover Docker, basic AWS, and Cloudflare Workers. If your module uses something else, ask and I will tell you honestly whether I can help, often I can.

Singapore-based across the board. Universities: NUS Computing (CS1010 through CS3xxx, DSA1101, ST2334, FYP), NTU SCSE (SC1003, SC2002, FYP), SMU (IS111, IS200), SIT, SUTD, and SUSS. Polytechnics: SP DAAA / DCITE, NP DCITE / DIT, NYP DIT / DSA, TP CSF / DIT, RP DCS / DDP. ITE for foundational programming.

I know how SoC marks functional programming versus how SP marks Java assignments, and what NYP's data-engineering capstone usually looks like. That context matters because the same code can score very differently across institutions.

International students on equivalent programmes are welcome too, but Singapore curricula are where I have the deepest module-by-module pattern recognition.

Realistic ranges, not promises. Same day for one-function debugging, single-file walk-throughs, or a Past Year Paper question (typically 2-6 hours from message to delivery if I am free). 24-48 hours for full assignments under ~500 lines, including testing and an explanation. 3-7 days for FYPs, capstones, and projects requiring research or larger architecture decisions.

Replies on Telegram are usually within the hour, afternoon to past midnight Singapore time. If your deadline is tighter than what I can deliver well, I will tell you upfront rather than rush something that hurts your grade more than missing the deadline does.

Yes, strictly. What you send stays between us. I do not resell, republish, share with other clients, or use your work as portfolio examples. Names and module details are never mentioned in reviews on the /reviews/ page (each quote there is anonymised at source).

Storage: form submissions go through a Cloudflare Worker into a private Telegram chat (Worker memory only, no Cloudflare retention). Telegram conversations stay in my account for future reference and to support repeat clients; only I can access them. If you want a specific exchange deleted, ask and I'll do it. Email enquiries sit in my Gmail inbox under standard Google Workspace retention. Full details on the /privacy/ page.

No, and you should be careful with anyone who does. Grades depend on your final submission, the marker's interpretation, your demonstration or viva (if any), and factors outside both our control. Anyone promising a specific grade is either lying or doesn't understand how marking works.

What I can guarantee: working code that runs against the requirements as written, clear explanations of every section so you can defend it under questioning, honest feedback on where your existing work stands before we start, and a fixed price agreed before any work begins. The track record on the /reviews/ page reflects that, not grade promises.

Reasonable revisions are included for two cases. One: the code does not meet the brief as we agreed it (a function returns the wrong output, a feature is missing, a test fails). Two: a bug appears in normal use that should have been caught before delivery.

Out of scope: new requirements added after delivery ("can you also add this feature?"), changes because the brief itself changed mid-way, marker feedback that asks for a different approach. Those are quoted separately and fairly. Full terms on the /terms/#revisions page.

PayLah (preferred, instant, no fees) or local bank transfer (FAST/PayNow) for clients in Singapore. For overseas clients, Wise or PayPal on request.

Standard arrangement: full payment upfront, before I allocate time to your task. Keeps the engagement simple and avoids back-and-forth on small and medium jobs. Exception: large commercial jobs running into the multi-thousand-S$ range, where milestone payments make sense (typically a 30% deposit, milestone payments thereafter, balance on final delivery). The split is agreed in writing before work starts, never negotiated mid-engagement.

No payment until you've seen the quote, agreed the scope, and confirmed in writing on Telegram. The full pricing structure lives on the /pricing/ page.

Yes. Exam weeks (typically late April / early May for Sem 2, late November for Sem 1) are the busiest times of the year for me, and slots fill up 1-2 weeks ahead.

What's most asked for: Past Year Paper walkthroughs (CS1010, CS2030S, CS2040S, DSA1101, ST2334), concept revision sessions (recursion, pointers, recurrence relations, dynamic programming, SQL joins), and last-minute clarifications during reading week. Sessions are typically 1-2 hours over Telegram screen-share, billed per hour.

If you are reading this within 7 days of an exam, message immediately rather than waiting until the week before.

Yes, and a good chunk of my work is exactly this. About a third of my tutoring clients have written zero lines of code before their first session, often they're polytechnic students hitting CS1010 or NUS BBA students taking IS111 as a required module.

Sessions start with what's actually confusing you (variables, functions, loops, error messages) rather than a fixed curriculum. No judgement, no "you should know this already", no assumed knowledge. If you can read English and use a laptop, we can get you to a working programme by the end of session two.

First session is 1 hour, no commitment beyond that.

Yes. Typically one teammate engages me as their personal coding consultant: I help that person specifically, and they bring the work back to the group as their contribution. The group's other members never need to know I exist (and often don't).

I match the existing codebase style: same naming conventions, same level of comments, same testing approach. If the team's code is messy I will not silently rewrite it; if it's clean I will not introduce inconsistencies.

What I won't do: pretend to be a teammate in group meetings, log into anyone else's account, or contribute to the group's shared repository directly. Your name on the work, every time.