A central place for skill discovery, measurement, challenge, and exposure across software engineering, CS, AI, and beyond.
This version treats the platform as a competency system. Domains contain tracks, tracks contain subtracks, subtracks contain skills, and skills are only completed when the learner clears real implementation challenges.
Discovery
Find what matters next instead of guessing. The platform surfaces skills, prerequisites, and adjacent topics across software engineering, CS, and AI.
Measurement
Progress is earned through challenge completion, not passive reading. Every skill has explicit demonstrations of competence.
Exposure
Learners should see the full terrain: frontend, backend, systems, data, ML, security, and the links between them.
Core model
Domain to challenge, with no ambiguity about what is being measured
The key shift is that a topic is not the same thing as a skill, and a skill is not complete until the learner can repeatedly perform it under challenge conditions.
Domain
Software Engineering
The broad area a learner wants to enter and eventually master.
Flows into next
Track
Data Structures & Algorithms
A major competency area inside software engineering.
Flows into next
Subtrack
Strings
A focused concept cluster with reusable patterns and repeated failure modes.
Flows into next
Skill
String manipulation and reasoning
The concrete developer capability being measured.
Flows into next
Challenge
Reverse, replace, compress, compare, scan, parse, and 100+ more
A learner proves the skill by implementing a large challenge set successfully.
Competency graph
Click through a real branching sample structure
This is the first interactive slice: select a domain, drill into tracks, then subtracks, then skills, then challenges. Each click loads the next branch.
Interactive structure
Click a node in any column. The next branch loads immediately, and the explorer walks down the first available child path so the full structure stays visible.
Domain
Track
Subtrack
Skill
Challenge
Selected node
Reverse a string
Reverse a string correctly, handle unicode caveats, and explain time-space tradeoffs.
Node type
Why this matters
In the real product, this panel can hold prerequisites, completion rules, challenge counts, recommended next nodes, and proof-of-skill artifacts.
Signals
Path preview
Software Engineering -> Data Structures & Algorithms -> Strings -> String transforms -> Reverse a string
Software engineering map
One domain, many deep branches
Foundations
Product Engineering
Systems
AI + Data
Skill example
Strings as a real measurable developer skill
Software Engineering / DSA / Strings
To complete the strings skill, the learner should successfully implement a broad set of string algorithms, not just watch an explanation once.
Product rules
What this platform needs to enforce
If the product is meant to measure engineering ability rather than just host content, these rules need to be designed into the system early.
Every skill should declare prerequisites, challenge count, and completion criteria.
Every challenge should be graded by correctness, efficiency, and explanation quality.
Tracks should expose nearby skills so learners can branch without getting lost.
A user profile should show what they can actually do, not just what they have viewed.