Meringue Philosophy

&gt; Meringue is an object-oriented implementation of datetime functionality in php. It’s built atop the few fundamental universal abstractions, so it’s minimalistic, intuitive and extendable. At the same time, it allows carrying out complex datetime calculations due to its inherent declarative nature.<p>And there I was, expecting this to be a novel food-based metaphor about how certain kinds of philosophy are sweet and delicious, yet crumble easily under the slightest pressure.

Funny, I just recently commented on a different post laying out what I think is a disagreement with the basic idea here.<p>The assertion that &quot;metaphysics fits enterprise software development discovery and implementation needs perfectly&quot; overlooks a critical distinction between philosophical inquiry and practical application. Metaphysics, which delves into the nature of reality and existence, often involves abstract categorization and the pursuit of understanding universal truths. However, enterprise software development is fundamentally a practical discipline aimed at solving specific business problems.<p>When software engineers model a domain, they are not engaging in an Aristotelian or Platonic exercise to capture the true essence of entities. Instead, they are creating representations that are useful for achieving particular business objectives. The primary goal is not to uncover ontological truths but to develop functional, efficient, and scalable solutions that meet the needs of users and stakeholders.<p>Theoretical unifications and abstractions, while intellectually stimulating, can often lead to over-engineered solutions that do not align with the practical demands of enterprise software. Software development requires pragmatism: the ability to prioritize utility and business value over philosophical purity. Abstractions in software are useful only insofar as they contribute to the effectiveness and maintainability of the system within the context of its intended use.<p>I&#x27;m not suggesting there aren&#x27;t <i>some</i> situations where applying metaphysical thinking can be helpful. However, using this approach as a general, top-down strategy doesn&#x27;t make much sense. Software engineering, by definition, is a practical discipline, involving concerns and objectives that differ fundamentally from those of metaphysics.

I appreciate linked data &#x2F; the semantic web and its domain model-forward approach, labeled &quot;ontologies&quot;. Organizing relationships between objects and actors contextualizes them and forces you to pursue parsimony. It&#x27;s nice to see this philosophy appreciated elsewhere.<p>My projects usually start with a &quot;goblin mode repo&quot; to explore the domain, its possible representation in code, and settling on a suitable domain model for the problem in question. It&#x27;s explicitly a place for prototyping, experimentation, and breaking changes galore. Naturally this technique doesn&#x27;t extend much further than a small, tight-knit team, but once you find something that works you can formalize it in a new repo and share access with a wider group. If you did it right, those others will have no trouble comprehending the domain from the organization of code structures you&#x27;ve provided and extending that code in ergonomic ways to add features.

1. Some philosophers think many metaphysical debates meaningless. Consider the debate about ordinary objects such as chairs. These typically are the result of composing more fundamental entities (such as those of the Standard Model). Mereological nihilists say: there are no ordinary objects (such as chairs). Others disagree. &#x2F;Relativists&#x2F; about metaphysics say that these disputes are merely verbal. There is no fact of the matter to discover and expound. Whether or not there is such a thing as a chair is simply a matter of convention.<p>2. I disagree. But I think one point is right. Relativists point out that it is often (or maybe even always) possible to translate statements between the languages promoted by different metaphysical schools. For example, nihilists translate ‘the chair is on the ground’ to ‘some particles arranged chairwise are such that the particles at the bottom touch the ground’ (or something similar). For this reason, they claim not much hinges on whether nihilists are actually right.<p>3. Despite my antirelativist metaphysical inclinations, I think it is possible to translate statements in the language given by the ‘same ontology that constitutes reality’ systematically into languages that reflect different metaphysical views.<p>4. Some of those erroneous metaphysical views may correspond to how we naturally tend to think about certain areas, or the needs of computation (e.g. in being better complexity-wise). For this reason I am sceptical about the (admittedly very interesting) technique advanced in this essay, since it seems to assume that no conflict between these demands will arise.<p>5. A final worry is that metaphysics does not really speak with one voice. Many philosophers are quite sympathetic to the sort of picture outlined at the start of the essay, but e.g. mereological nihilism is surprisingly popular! If resolving these questions definitively is too much even for philosophers, those applying their conclusions will have some trouble too.

Enterprise software is just a shadow of the ideal software

Definitely agree with the author on this one in the general sense of programing is an act[1] of defining ontologies and programmers who are aware they&#x27;re doing this can be more effective. Likely because doing anything deliberately is more effective.<p>What I wish he touched on is indiscernibility of identicals. That is, drawing a comparison between the idea that we can perceive two object having the same color that have two wildly different spectral distributions we can, also have two objects that are indistinguishable based on identical relations.<p>&quot;Where does &#x27;green&#x27; occur?&quot; is a perfectly valid question for green objects. If we insist that green is an essential characteristic of the object, then why is it that one object emitting 525nm light and another emitting both 450nm and 575nm light are both the same color? It would seem as though green <i>isn&#x27;t</i> an essential characteristic of the object and instead it&#x27;s a characteristic of perception. Ie: green objects are perception-interchangable.<p>Similar to perception-interchangability is duck typing. Ie: if a thing is in all ways that matter, perceived the same as another, then they can be substituted. Though one does have to rather careful about what actually matters lest they find themselves in a plucked chicken scenario[2] with someone trying to point out the metameric folly of comparing them to men.<p>1. among others<p>2. <a href="https:&#x2F;&#x2F;www.worldhistory.org&#x2F;Diogenes_of_Sinope&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.worldhistory.org&#x2F;Diogenes_of_Sinope&#x2F;</a>