Web/SeM2x/Weather CLI Challenge

[SeM2x]

Design Decisions

Since I’m already comfortable with the basics of Node.js, I wanted to make this challenge more interesting by going beyond the minimum requirements.

Instead of building a simple one command script, I added:

• An interactive REPL mode for continuous querying

• An in-memory cache with TTL (time to live) to reduce redundant API calls

• A structured, modular architecture

• Optional IP-based city auto-detection

The goal was to challenge myself from a design perspective, not just make it work, but make it scalable and maintainable.

So I intentionally approached this project using object-oriented principles, focusing on:

• Clear separation of concerns (CLI, services, providers, utilities)

• Interface-driven design (ICacheService, provider abstractions)

• Dependency inversion where appropriate

• Extensibility

I also chose TypeScript even though this could have been written in plain JavaScript, using TypeScript helped formalize DTOs, interfaces, and service boundaries in a more production like way.

This project was as much about architecture and clean design as it was about fetching weather data.