Skip to content

Conversation

@Emnestu
Copy link

@Emnestu Emnestu commented Nov 3, 2025

No description provided.

@Emnestu
Copy link
Author

Emnestu commented Nov 3, 2025

For this exercise, I took an MVP approach – prioritizing business value over completeness. Without access to a design document, I used the existing code structure as my guide. For example, the app wasn’t built with dependency injection in mind, and there’s nothing to suggest that future expansion beyond a single bank is expected. With that in mind, I accepted the trade-off of tighter coupling in favor of a quicker and simpler implementation.

That said, I made sure to prioritize correctness: I familiarized myself with FX terminology, reviewed the bank’s policies on exchange rate updates, and integrated the application with the REST API they provide. In summary, my implementation delivers the necessary functionality while keeping YAGNI as a core principle, avoiding the pitfall of overengineering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant