Hacker News Reader

> Objects don't live on their own, in a typical OOP program there are bits of code all over the place that operate on your data objects. Finding all the ways that a personel record is modified can be a tricky problem.

Searching for all the code that touch an Employee record class is much easier than searching for all the code that touch a generic hashmap that supposes to contain the employee data.

View on HN

This a property of static typing, not object oriented design. Take for example Typed Clojure, where you could define an Employee as a hashmap with a set of static constraints which can then be analyzed for, without having to invoke any of its proper OO constructs.

Why on earth would you use an untyped generic hashmap for employee record data? What kind of language do you think forces you into that kind of architectural decision?

Certainly no language I have or would develop an MIS in, regardless of paradigm.

Reply on news.ycombinator.com