Arye hoffmann

=== Category mistake ===
All the blog entries below are examples of a Category mistake.
https://web.archive.org/web/20170515093021/http://aryehoffman.com/reference/structured-objects-approach/
https://web.archive.org/web/20190109021100/https://aryehoffman.com/entry/understanding-an-object-oriented-approach/
https://web.archive.org/web/20160821212336/http://aryehoffman.com/entry/examples-object-technical-rules/
https://web.archive.org/web/20160821210824/http://aryehoffman.com/entry/are-you-an-object-or-functional-thinker/ In an object-oriented approach, one represents concepts, real or abstract, as objects. Like the objects you see and imagine around you, they have attributes and behavior. They can collaborate together to represent a problem or system
https://web.archive.org/web/20160824195552/http://aryehoffman.com/entry/which-side-of-computing-do-you-work-on/ Ones perspective on solving problems in computing is typically determined by whether your experience has been in what I call the “left” side of computing or the “right”. The left side is dominated by problems in computer and data science. There is particular emphasis on data structures, algorithms, parallelism and technologies, and increasingly today, dealing with big data and infrastructure. The right side is dominated by problems and systems in business, commerce and industry. The emphasis is on structured programming, data modeling and object-orientation as a way to represent functional requirements and complex domain concepts in code.
=== links ===
Oop comments
Oop
Category:Oop