How we designed the B.Tech CSE curriculum: the tradeoffs we actually made
Every curriculum is a set of choices. Here are the specific design decisions behind the Kalvium B.Tech CSE programme, the options we considered, what we built in, and why.
AJ
5 posts
What industry-integrated learning actually means: three tests to tell if a programme is real
Most engineering prospectuses claim industry-integrated learning. Few define it. Here are three concrete tests that separate real programmes from ones that just say the words.
Inside Kalvium's orientation week, broken down by design choice
Kalvium's first week is not a traditional college orientation. Five design choices set it apart, and each one was a deliberate call. Here's what each is doing, and what we'd change with hindsight.
Why Kalvium's capstone projects start in Semester 2, not Year 4
Most engineering programmes put the capstone at the end. Kalvium puts the first one at the start of Semester 2. The decision had three constraints. Only one design survived all three.
Why Kalvium puts full-stack in Year 1: the design lever, not the brand statement
Most CSE programmes teach basic C in Year 1 and put real software in Year 3 or 4. Kalvium puts full-stack in Year 1. Not for ambition. For the only design that closes the gap engineering leaves open.