Frequently asked questions about formats, schedules, and enrollment

lumionyx runs instructor-led online courses (2–3 week cohorts), live webinars (single sessions), focused masterclasses, and short intensives. Each format includes an outline, a practice plan, and a clear expectation of what you will produce—such as a language draft, a mini-project, or a documented AI workflow.

Most lessons run 60–75 minutes. Webinars are typically 75 minutes including Q&A. That timing supports a balanced block: a short lecture, guided practice, and a brief assignment handoff. We avoid marathon sessions because fatigue reduces retention and makes feedback less usable.

Most cohorts run 2–3 weeks. This is a deliberate “tight loop”: it is long enough to practice a skill with repetition, but short enough to keep momentum. Cohort structure also makes it easier to coordinate feedback windows and maintain a consistent rubric across participants.

We teach languages (English, Chinese, Arabic), applied AI workflows, coding fundamentals with small projects, and modern digital skills. Not every topic runs every week; availability depends on the calendar. For the nearest dates, request the schedule through the form.

You receive a short outline, practice prompts, and any templates used in class. Language cohorts typically include a manageable spaced repetition list and correction notes tied to a rubric (clarity, tone, word order, and typical error patterns). AI cohorts include prompt patterns, evaluation checklists, and a simple “red team” review step to catch uncertainty. Coding cohorts focus on small builds, debugging habits, and clean naming conventions.

Assignments are part of the design, but they are small and concrete. The aim is retrieval practice and a visible checkpoint—an email draft, a short speaking script, a mini-function, or a documented workflow. If you skip all practice, outcomes will be limited, which is why we keep the deliverables short enough to finish during a normal week.

Feedback maps to a rubric so it stays consistent across the cohort. In language tracks, corrections prioritize a small set of high-impact changes and explain why the change improves clarity or tone. In AI workflow training, we evaluate outputs against a checklist (source handling, uncertainty flags, and a final review step). In coding, feedback focuses on correctness, readability, and debugging method rather than “clever” tricks.

We focus on learning artifacts and documented progress rather than marketing-style guarantees. Outcomes vary with starting level and consistency. If a cohort includes a completion note, it reflects participation and submitted work—never a promise of a specific career or financial result.