News for hackers. Stuff that matters.
Re:Low Code Software Development Is a Lie by e12e on Saturday April 15, 2023 @01:47PM (#35582810)
> "Business logic" normally dictates the relative ordering and contextual legality of certain operations and data values.

Wikipedia gives the following definition for "business logic"

> In computer software, business logic or domain logic is the part of the program that encodes the real-world business rules that determine how data can be created, stored, and changed. It is contrasted with the remainder of the software that might be concerned with lower-level details of managing a database or displaying the user interface, system infrastructure, or generally connecting various parts of the program.

I (and i believe op) lean on the "domain logic" end when talking about business logic.

So the fader toggles bits in the raw data, but in a way that input and output is sound data that can flow through the application. Your DAW needs both the bit fiddling - and the "flow input through the fader and out to file" parts.

> Musicians typically have only a vague idea, if they have an idea at all, of what they are trying to accomplish.

I'm talking much more abstract here - "improve recording" is a goal - there's a current domain state, and the goal is to modify it in some way. I'm talking about user intent in interacting with the domain.

Re:Low Code Software Development Is a Lie by PaulDavisThe1st on Saturday April 15, 2023 @01:57PM (#35582911)
From the wiki quote:

> the real-world business rules

what are these for creative apps, and where do they come from?

Re:Low Code Software Development Is a Lie by e12e on Saturday April 15, 2023 @02:24PM (#35583195)
> ... determine how data can be created, stored, and changed.

So you can record sound, store it in a "track", transform it to "mono" etc?

> ... It is contrasted with the remainder of the software that might be concerned with lower-level details of managing a database or displaying the user interface, system infrastructure, or generally connecting various parts of the program.

You might store the sound as a wav, export it as an mp3 - the undo tree might be in SQLite...

Ed: might make more sense with the term "domain"; domain logic, domain rules.

Ed2: somewhat tangential, but see also the original model-view-controller-(user) paper - the user holds a mental model of data/objects in the domain - and the application holds raw data in ram/disk - the UI needs to bridge these two domains so that a user can "apply reverb" from the domain concept to the actual data model (modify a wav file).

https://folk.universitetetioslo.no/trygver/themes/mvc/mvc-in...