9diov

il y a 3 ansdiscuss

Haha lovely, clearly we are in agreement here. You even put that in your book isn't it?

> The Visitor pattern is really about approximating the functional style within an OOP language (source: https://craftinginterpreters.com/representing-code.html)

The expression problem is one of those "mathematical duality" or yin-yang thing in software design that are less well-known for some reason. People keep pointlessly arguing in favor of one or another without knowing this duality.

Another favorite of mine is SQL vs NoSQL which Erik Meijer mathematically proved to be dual of each other using category theory (https://queue.acm.org/detail.cfm?id=1961297).

9diov

il y a 3 ansdiscuss

There are cases when the OOP way clearly has the disadvantage. That's why you need visitor pattern (https://en.wikipedia.org/wiki/Visitor_pattern?useskin=vector). The ADT approach is superior in those cases, as stated in the link above.

9diov

il y a 6 ansdiscuss

The paper "Out of the tar pit" (https://github.com/papers-we-love/papers-we-love/blob/master...) discusses this in more details. Basically it argues that one needs to separate the complexity into essential complexity (complexity inherent to the problem) and accidental complexity (complexity due to the way the solution is designed). The idea is to reduce accidental complexity as much as possible while making the essential complexity more managegable.

The paper also discusses that you can separate a program into

1. state (data that changes over time)

2. behavior (computational logic)

In order to reduce the accidental complexity, you can use functional programming (which is purely behavior, devoid of complexity due to state mutation) for the behavior part. For the state part, you can use a relational database to manage it in a more systematic manner. They call it functional-relational approach to software design.

If you do game development, you likely heard of ECS (entity-component-system) and data oriented programming which in a way promotes this approach to software design.

9diov

il y a 7 ansdiscuss

Looks like you discovered Taoism on you own

9diov

il y a 7 ansdiscuss

For anyone who is not familiar with Looker, I wrote a write-up and review about it here https://www.holistics.io/blog/looker-review-and-breakdown/. Here are the key points:

- Its use of LookML provides a steep learning curve, yet provides a maintainable and reusable data modeling

- Looker's drill-down ability is decently powerful and easy to use once you are familiar with LookML.

- Looker does not have its own storage layer but instead relies on customer's data warehouses

- Looker, in essence, is a SQL query builder engine that converts business users' drag-and-drop inputs into SQL queries.

- Looker provides highly flexible and sophisticated access control and permission management, sacrificing simplicity for power.

- Looker has limited data preparation capabilities compared to other tools, delegating this task to its partners to provide these capabilities.

Submissions

Ask HN: How do you manage dependencies between multiple repos?

comments