Where we go deep
The work is broad, but it is not generic.
We work inside mature open-source platforms, beside them, and underneath them. That means product work,
interoperability work, and serious backend work, often in the same project.
Open-source LMS product engineering
Assignments, grading, quizzes, rubrics, and the real semester path
We have spent a lot of time in open-source LMSes, especially Sakai, building and repairing the paths that
faculty and students use every day. That includes Assignments, Gradebook, Tests & Quizzes, rubrics, portal
navigation, accessibility, and the administrative edges that determine whether support tickets pile up.
Assignments Gradebook Tests & Quizzes Rubrics Accessibility
Assessment engines and authoring
Timed assessments, item logic, QTI, and authoring workflows
Assessment work is its own discipline. We have been deep in timing logic, accommodations, statistics,
scoring, question behavior, and authoring constraints. QFlowLearn extends that work into a dedicated QTI 3.0
authoring system built for cleaner authoring and better interoperability.
QTI 3.0 Item authoring Accommodations Statistics Validation
SCORM and content portability
SCORM 2004 runtime work that can survive real use
We have modernized SCORM runtime flows, launch behavior, site-to-site import, and REST-backed player
plumbing so packaged content is easier to debug and easier to carry forward.
Read the SCORM work →
Academic integrity systems
Plagiarism detection that is actually ours
We have built plagiarism detection from scratch, including the workflow and system behavior underneath it,
not just the last-mile integration to an external service.
Platform architecture
Concurrent systems, queues, and big weird data structures
Some projects need more than a clean UI and a sensible schema. We have built high-concurrency systems,
queue-driven services, and large ring databases where the traffic shape and data model called for them.