Past Seminar

A seminar on Aricie's training program took place from October 2 to October 10, 2008. Records of that session are kept as part of our training history.

Training programs are structured to give teams a working familiarity with the platforms that power their day-to-day operations. Rather than a single introductory lecture, the material is organized into focused tracks that allow participants to move from foundational concepts toward more specialized workflows. Each track is designed for practitioners who already understand their own application environments and want to deepen that understanding through guided, professional instruction delivered at a steady pace. The emphasis remains on practical competence, with each session reinforcing ideas through examples drawn from real module and service configurations used in production settings.

Two complementary course areas define the broader catalog. The first area covers the Aricie.Net platform itself, addressing how applications, services, and supporting modules fit together for teams that build, extend, or maintain Aricie-based solutions. The second area turns to DotNetNuke, treating it as a mature framework with its own conventions, certification paths, and module ecosystem. Taken together, the two areas reflect a belief that platform knowledge is most useful when it is taught in context, with each course connecting classroom topics directly to the systems participants already work with.

Within each area, courses are arranged so that foundational topics appear first, followed by progressively more advanced material. This sequencing lets new learners build confidence gradually, while experienced developers can step directly into sessions that address the specific capabilities they plan to use. Sessions typically combine conceptual discussion with hands-on exercises, allowing participants to test ideas in a controlled setting before applying them in their own projects. Group pacing is moderate, and instructors encourage questions throughout, so that the material remains grounded in the actual challenges teams face.

The training history includes earlier seminars that helped shape the current program, and past sessions continue to inform how new courses are developed. Records from those seminars serve as a reference point for refining the balance between theory and practice, and they offer a way to track how platform features have evolved over time. By preserving this history, the program maintains continuity between cohorts, ensuring that lessons learned in earlier sessions remain available to guide future learners as the platform itself continues to grow.