SYCGeeks

Vancouver, Canada · Prices in CAD

SYCGeeksSYCGeeks

Support · Your account · 15 min read

Student orientation and the hour log

Finish the studio steps, then log date, hours, and a sentence another person can staff a Friday from — a habit you can take to any internship.

AI-generated packed product ready to ship

You get a student dashboard so the week is readable

Students join with a different dashboard on purpose. You do not see a merchant’s projects, purchases, and store notes first. You see orientation, then Hours. A Vancouver studio that invoices in CAD and ships English and French cannot treat a student login as a junior merchant account. You are here to learn the week, the tools, and how to write time another person can read — the same skill a Toronto internship or a Montreal shop will ask for. Pick the student role before you connect a wallet or finish email registration. Existing wallets keep the role they already have. If you connected as a merchant by mistake, write admin@sycgeeks.ca. Do not log salon sales on a student hour; money and learning sit in different files so neither gets lost.

Wallet login is a signed message, not a password. Email login is the other door. Both land in the student view if the role is student. If the nonce route returns empty, the studio database is unreachable — try email, or call +1 (672) 200-7924 if you cannot get in and a deadline is today. A blank error is not your fault and not a reason to invent hours in a spreadsheet. Wait until the log can save, then write the line. Hours that only exist in a private sheet cannot staff a Burnaby Saturday. The same rule applies at any studio: the official log is the capacity map.

You can book a Square appointment with no account if a mentor hour was offered. Times show in your timezone. The studio is open 24/7 except Canadian statutory holidays, unless the matter is urgent. Bring questions that orientation did not cover. Booking does not unlock the log, and a long email does not either. Completing the steps does. That rule is how we know you saw the week, the tools, and the way we write time. If you are stuck mid-orientation, write admin@sycgeeks.ca with the step name and the error text. Heat is “I cannot get in today and hours are due.” Everything else can wait for a sentence.

Same-week path for a new student. [ ] Pick student before you connect a wallet. [ ] Finish orientation on a laptop you can keep open. [ ] Save a test hour of 0.25 with a factual line so you know the log works. [ ] Write your class hours and timezone in an orientation note so launches are not assigned to a morning you have a lab. [ ] Bookmark the three doors: phone for lockout, email for “how do I describe this,” Square for a mentor. That path works here and it works at the next placement that uses a timesheet instead of Hours.

What orientation covers before the log opens

Work through the studio steps first: how a week looks on Pacific time, which tools we use, and how to write hours another person can read. A week here is not a campus timetable. Discovery, build, review, and launch sit on a merchant project. Your time sits on the hour log. If you will touch a live cart — Square, Stripe, PayPal, Apple Pay, Interac e-Transfer, optional ETH — orientation will say who may touch it. Students do not “just quickly” refund a CAD order because a demo felt safe. Money has a named owner. That sentence is useful in any shop: if you cannot name who may refund, you are not the person who refunds.

Orientation also covers the three doors. Call if you cannot get in or if production you were asked to watch is down. Write admin@sycgeeks.ca if the question can wait for a sentence. Book if a mentor wants to speak. You do not need the heat line to learn that 0.25 hours is allowed (it is, up to 24). You do not need it to learn that this studio uses illustration instead of stock people photos. You do not need it to negotiate care prices for a merchant; those numbers are public — Essential $199 CAD, Business $399 CAD, Engineering $450 CAD a month or $4,500 CAD a year — and they are not your invoice. Unused hours on care do not roll, and they are not a student coupon.

You will see how English and French work on a Canadian site. Bilingual work is not a toggle. Button widths change. Receipts must be correct. A checkout that fails in French is a product bug. If your French is stronger than your English, say so; we will assign review that matches. If you only have one language, do not machine-translate a legal page and log it as “localization.” Orientation says so before you can save a line that claims you shipped both languages. The same discipline will save you at a federal or Quebec placement: legal pages need a human reviewer.

PIPEDA and WCAG are not elective modules. Collect only what a form will use. Contrast, labels, keyboard paths, and real alt text are launch work. If you are asked to add an analytics script “because the template had one,” write the reason you paused and ask a lead. If you are asked to drop a chatbot without a privacy sentence, pause the same way. Orientation exists so those pauses are muscle, not a surprise in week three. Finish the steps. Then the log will save. Take that muscle to the next job: purpose on the form, keyboard on the path, language on the receipt.

How to write an hour another person can read

After the steps are complete, open Hours. Enter the date, the time you spent (0.25 to 24), and a general description — what you built, reviewed, or unblocked. “Reviewed French receipt on the Montreal retailer checkout; HST line still missing for Ontario” is a description. “Worked on stuff,” “misc,” or “learning” without a noun will come back, because the next person cannot staff a Friday from it. The next person should know what moved. They should not need to ping you on a Saturday. That is the whole job of a timesheet, here or at a co-op in Halifax.

Copy-paste patterns. Review: “Reviewed [surface] in [language]; found [fact]; next step [owner].” Build: “[Workflow step]: wired [processor] on [page]; CAD test order [passed/failed]; blocker [if any].” Blocked: “Blocked on Square test account; cannot place a CAD order; booked Thursday mentor slot in my timezone.” Care (only if assigned): “Care hour: patched [label] on [URL]; note added to merchant project.” Keep descriptions short and factual. Name the surface: homepage, booking path, dashboard note, privacy page. Name the language if the work was language work. Name the processor if you tested a rail. Name the city if the bug is local — “Burnaby salon book button still shows 2019 walk-in hours” is better than “fixed UI.”

Date is the day the work happened. The studio clock is Pacific; if you worked a Toronto evening that was still afternoon here, use the date the studio will recognize and mention your timezone in the line if it would otherwise look like a night shift. Do not split a two-hour task across three creative dates to make a week look even — capacity maps break. Do not log 24 hours unless you were actually on the task for 24 hours; that field exists for rare live events, not for ambition. 0.25 is fifteen minutes. If the task was five minutes, wait until you have a quarter hour of related work, or write that you unblocked a five-minute item and spent the rest on the named review.

If you are stuck, write that you are stuck and book time. Sitting on a ticket for three days and then logging eight hours of “investigating” hides the blocker from the person who can unblock Square. This log is how the studio understands capacity. Inflated hours make the next week staffed wrong. Missing hours make a Burnaby launch look uncovered. Either mistake costs a merchant. If a line comes back empty of facts, rewrite it with the surface, the language, and the next step. That rewrite is the skill; it is not a scolding. Do not paste client personal information into the description. The log is capacity, not a CRM. PIPEDA does not pause for internships.

Worked examples you can steal. Good: “Active / build: wired Interac instructions on CAD invoice page; English done; French button overflows — noted for bilingual review.” Good: “Unblocked HST on Ontario shipping for the Montreal retailer; merchant approved in notes; no live refunds.” Weak: “Various frontend.” Weak: “Helped the team.” The good lines tell a lead whether Friday needs a French reviewer or a tax person. Practice until the weak lines feel unfinished in your hands.

What you may touch, and how to pause a risky ask

You may write notes a merchant can read if you are asked to sit on a project. Use their dashboard language: decisions, not chat. You may test a path on a staging URL. You may prepare illustration instead of stock people photos. You may check GST versus HST on a receipt if that is the assigned task. You may not invent a price. You may not publish a live change without the named approver. You may not add a payment rail we did not quote. You may not “improve” French with a machine and call it done. Write those limits in your own words once during orientation so they are easy to find on a Friday.

If someone asks you to hide a disclaimer in six-point type, to build a second inventory next to Square POS, to make crypto the only way a salon takes money, to collect a phone number “just in case,” or to skip alt text because a launch is Friday, pause. Write the pause in the hour description and tell a studio lead. The log is also how we see pressure. A student who silently ships a bad cart is not being helpful; the receipt is how a customer in Ontario knows HST was collected. The pause is the contribution. You can use the same pause at any internship: name the rule (PIPEDA, WCAG, tax, language), name the ask, ask who owns the exception.

Care work — the reserved studio hour on Engineering, the small-copy hours on Business, the watch on jobs that move money — is assigned, not assumed. If you are asked to spend the care hour, log it as care work and name the change. Post-launch add-ons at about 25 percent off for Business and Engineering are merchant purchases, not student discounts. Essential care is $199 CAD and has no reserved hour. Do not tell a retailer you can “just add a collection this afternoon” because you have time in the log. That is a quote in CAD on the same project. Your unused hours are not a coupon, and unused care hours do not roll either.

Questions to ask a lead this week, useful anywhere. Who may refund a CAD order? Which processor is the system of record? Is French in the quote or a later add-on? Where do secrets live (not in Hours)? What is the current workflow step, and what would be out of step? If the merchant’s cart is down, do I call, write, or both? Write the answers in a note you can find. Orientation is not a video you survive. It is a map you will use on the first blocked afternoon.

Pacific time, national clients, and when to stop

The studio clock is Pacific. A Montreal retailer who answers at 9 a.m. Eastern is 6 a.m. here. Do not book yourself into that unless a lead asked you to. Do not log a late night because the merchant is on Atlantic time and you felt polite. Overlap is a constraint you can plan, not a personality test. If your class schedule only allows evenings, say so in orientation notes so we do not put you on a morning launch. Honesty about the clock is part of capacity. Appointments you book with a mentor show in your timezone; read the confirmation across a daylight-saving weekend.

Stop when the assigned task is done or blocked. Extra polish on a launched page to fill a four-hour gap can change what the merchant bought, or break French spacing you will have to log again tomorrow. If you have time left, ask for the next named task or write that you are available. Empty heroics read as risk, not initiative, because a live page is a contract in CAD. The useful move is a short note: “Two hours free after 15:00 Pacific; can take bilingual review or a staging cart test.” Leads can staff that. They cannot staff a surprise redesign.

If you are sick or in an exam week, write before the day starts. An honest zero is more useful than eight hours of fog. The log is not a moral score. It is a map of who can watch a processor on Friday. A Burnaby long weekend is when that map matters. Logging twelve hours of backfill on Monday after a silent week hides the gap that already happened. Log the day you worked. Write the day you could not. Statutory holidays close ordinary bookings unless urgent; if you were asked to watch a live cart on a holiday, call if it dies, then log the report.

How student hours meet merchant files without mixing roles

When your work touches a merchant project, the merchant still owns status, progress, and notes. You may be asked to draft a note. You do not change launched to paused because you felt nervous. You do not open a purchase. You do not apply a care discount. You do not move a Square appointment. If the merchant’s cart is down and you are the person who saw it, you call and write the URL. Then you log “reported dead Square checkout on Montreal retailer; called studio.” That is the job. Heroic silent fixing is how receipts go missing. The same split — report, then log — will serve you in any operations internship.

Workflows show the current studio step. Read them before you start. If the step is bilingual review, do not redesign the homepage. If the step is intake, do not write production code. If the step is launched, defects are care; new collections are add-ons. Your hour description should name the step you were in. Matching the workflow is how a student hour and a merchant file stay one story. If the step and the ask disagree, write that disagreement and ask; do not resolve it by shipping.

Never paste a merchant password into Hours. Never paste a customer name. Never paste a card. If you need a secret to do the work, ask a lead for the proper vault, then write “used staging Square login” with no value. PIPEDA does not pause for internships. WCAG does not pause for internships. Official languages do not pause for internships. The hour log should prove you understood that, one factual line at a time. If you are unsure whether a screenshot contains personal information, crop it or describe the bug in words.

After orientation: a week you can actually keep

A keepable week looks like this. You know the Pacific hours you can work, and you have written your class constraints. You have a named task or you have written that you are waiting. You log the same day, not the following Friday in a batch. You use the three doors correctly. You do not invent scope. You do not decorate a live page with stock faces. You leave a description a merchant, a lead, or a future you can read in February. That is the whole point of the log. Capacity you can trust. The same week will impress a co-op supervisor who has never heard of SYCGeeks.

If the week goes wrong — you cannot get in, the log rejects a save, a live path dies — escalate the same day. Phone for heat. Email for a sentence. Square for a mentor hour in your timezone. Do not wait for the next orientation video. You already finished those steps. The dashboard will not love you more for suffering quietly. It will show a hole where a Burnaby Saturday needed a human. Escalation is professionalism. Silence is how a processor goes unwatched.

Finish the studio steps. Then write the date, the hours, and what you actually did. Short. Factual. Dated. No stuffing. No secrets. No machine French. No stock people. No silent refunds. That is student work at SYCGeeks. It is how we have brought people into a bilingual Canadian studio since we opened the student view. The log is small on purpose. The week is real. Save the line. Then stop. If you want more responsibility later — watching a processor under care, sitting a launch, writing a quote draft — it will show up as better lines in this log, not as a title you gave yourself. We promote from sentences we can read. Start there. The rest of the studio is the same voice. You already heard it in orientation. Use it every time you save.

Pocket card. Call +1 (672) 200-7924 if you cannot get in or a live path you watch is down. Email admin@sycgeeks.ca to describe work or a blocker. Book a mentor hour in your timezone, 24/7 except statutory holidays unless urgent. Log 0.25–24 with surface, language, processor, next step. Never paste secrets. Match the workflow step. Pause risky asks and name the rule. Care prices and add-on discounts belong to merchants; your hours are not a coupon. That card is enough for the first month.

Keep reading