“Thanks, man.”
He smiled. Wrote the code. Handled edge cases. Added comments.
Outside, the summer sun blazed. Inside the computer lab, two students sat in the fading glow of CRT monitors, talking about stacks and queues and why break statements shouldn’t be overused.
“A library has issued a book to a member. Write a Python function to calculate the fine if the book is returned after 15 days, where fine is ₹5 per day for the first 5 days and ₹8 per day thereafter.” computer science grade 11 cbse
Three days later, in the exam hall, Rohan read the first question:
Ms. D’Souza, invigilating, watched Rohan finish early and flip through the paper, checking his SQL JOIN syntax, his network topology diagram, his truth table for (A ∧ B) ∨ ¬C .
“Done,” he whispered, exhaling.
“Ten more minutes,” Ms. D’Souza announced, her sari rustling as she walked between the rows.
Rohan’s logic was solid. He had defined classes: Book , Member , Library . Methods for borrow_book() , return_book() , display_available() . But somewhere, a bug lurked. When a member borrowed a book, the availability status updated correctly, but the due date kept resetting to the current date instead of current_date + 7 .
Aarav frowned. “No. That’d be chaos.” “Thanks, man
Ms. D’Souza collected the submissions. “Before you leave—your theory exam is in three days. Cover Boolean algebra, SQL queries, and networking fundamentals. Any last-minute doubts?”
Somewhere in the back, Aarav wrote the same function—a little slower, but correctly.