# orderedItems[].object.content
@jfdm I agree that modern technology has huge potential. However there is a huge timescale mismatch between IT technology and other things like buildings and automobiles.

IT stuff seems to last a few years at most, while cars can last for decades and buildings for centuries. It would be annoying to have to scrap a car because some server ceased to operate. Even worse for buildings.

# orderedItems[].object.contentMap.en
@jfdm I agree that modern technology has huge potential. However there is a huge timescale mismatch between IT technology and other things like buildings and automobiles.

IT stuff seems to last a few years at most, while cars can last for decades and buildings for centuries. It would be annoying to have to scrap a car because some server ceased to operate. Even worse for buildings.

# orderedItems[].object.content
@dmandl These tend to imply a grid structure.
Would not work well in this city. The directions to where I used to live were "Cross the bridge and turn left at the next seven intersections."

# orderedItems[].object.contentMap.en
@dmandl These tend to imply a grid structure.
Would not work well in this city. The directions to where I used to live were "Cross the bridge and turn left at the next seven intersections."

# orderedItems[].object.content
@programming_quotes The conscious mind evolved to solve problems in our external environment, such as getting a date, or not being eaten by that panther in the bushes.

The subconscious is much better at marshaling our memories and constructing solutions to complex problems.

Hence doing something else, or getting a good night's sleep, can be very helpful in solving complex programming problems.

# orderedItems[].object.contentMap.en
@programming_quotes The conscious mind evolved to solve problems in our external environment, such as getting a date, or not being eaten by that panther in the bushes.

The subconscious is much better at marshaling our memories and constructing solutions to complex problems.

Hence doing something else, or getting a good night's sleep, can be very helpful in solving complex programming problems.

# orderedItems[].object.content
#emperordonald
Emperor Donald the First

From the other side of the planet I am having a hard time understanding why 48% of the USA voters think this is a good idea.

# orderedItems[].object.contentMap.en
#emperordonald
Emperor Donald the First

From the other side of the planet I am having a hard time understanding why 48% of the USA voters think this is a good idea.

# orderedItems[].object.content
The problem with the current LLM based AI is that it make stuff up.

The result is that the generated text has to be reviewed by a human. We all know how well people do in that sort of job. Noticing the 1 in 1000 bit of nonsense is a very difficult task.

# orderedItems[].object.contentMap.en
The problem with the current LLM based AI is that it make stuff up.

The result is that the generated text has to be reviewed by a human. We all know how well people do in that sort of job. Noticing the 1 in 1000 bit of nonsense is a very difficult task.

# orderedItems[].object.content
@burakemir The trick is to know when the old model has reached the end of its usefulness.

The same applies to software. Often programs can be maintained for many years. Then, one day a seemingly small change request will break the camel's back and a complete redesign is required.

# orderedItems[].object.contentMap.en
@burakemir The trick is to know when the old model has reached the end of its usefulness.

The same applies to software. Often programs can be maintained for many years. Then, one day a seemingly small change request will break the camel's back and a complete redesign is required.

# orderedItems[].object.content
Today's lesson: Bread making machines work much better when you fit the kneading blade.

# orderedItems[].object.contentMap.en
Today's lesson: Bread making machines work much better when you fit the kneading blade.

# orderedItems[].object.content
@dev I suspect they are just taking advantage of the systems established by far larger players based in Europe and USA.

# orderedItems[].object.contentMap.en
@dev I suspect they are just taking advantage of the systems established by far larger players based in Europe and USA.

# orderedItems[].object.content
@dev Corruption flourishes in the dark. It has been journalists that have shone the light into the dark corners.

The problem is that journalists have typically been employed by newspapers and other media companies, and they are often owned by people that associate with those behind the corruption.

We need a better way of rewarding journalists and getting their work into the public view.

# orderedItems[].object.contentMap.en
@dev Corruption flourishes in the dark. It has been journalists that have shone the light into the dark corners.

The problem is that journalists have typically been employed by newspapers and other media companies, and they are often owned by people that associate with those behind the corruption.

We need a better way of rewarding journalists and getting their work into the public view.

# orderedItems[].object.content
The Spaghetti has Escaped

From the beginning of computers we have been trying to devise programming languages that enable us to visualise the workings of the programs.

We started with flow charts, but they ended up looking like a bowl of spaghetti. We created structured code but the complexity moved to the data structures. We responded with object oriented code, but the complexity hid in the interactions between the objects.

We tried to simplify the programs with service oriented architectures but the complexity just migrated to the network.

We are now trying to develop systems where components are developed and managed by separate organisations.

All hope of being able to visualise the workings of the system has been lost.

#SoftwareArchitecture

# orderedItems[].object.contentMap.en
The Spaghetti has Escaped

From the beginning of computers we have been trying to devise programming languages that enable us to visualise the workings of the programs.

We started with flow charts, but they ended up looking like a bowl of spaghetti. We created structured code but the complexity moved to the data structures. We responded with object oriented code, but the complexity hid in the interactions between the objects.

We tried to simplify the programs with service oriented architectures but the complexity just migrated to the network.

We are now trying to develop systems where components are developed and managed by separate organisations.

All hope of being able to visualise the workings of the system has been lost.

#SoftwareArchitecture

# orderedItems[].object.content
@einarwh
You mean processes using remote procedure calls and message queues like we did in the 80's?

# orderedItems[].object.contentMap.en
@einarwh
You mean processes using remote procedure calls and message queues like we did in the 80's?

# orderedItems[].object.content
@lutzhuehnken OK, I am beginning to understand our different views. I can see some attraction in loosely coupled databases - up to the point where you want a reliable system.

Its been my experience that any data item whose value is an integration of changes is inevitably a point of failure. An entire database holding an integration of the events doesn't bare thinking about.

Perhaps a more concrete example would help.

# orderedItems[].object.contentMap.en
@lutzhuehnken OK, I am beginning to understand our different views. I can see some attraction in loosely coupled databases - up to the point where you want a reliable system.

Its been my experience that any data item whose value is an integration of changes is inevitably a point of failure. An entire database holding an integration of the events doesn't bare thinking about.

Perhaps a more concrete example would help.

# orderedItems[].object.content
@lutzhuehnken
I think I am with OK-Steak on this.

Stock levels and pricing, for example, would just be in the database. No events required. (I am assuming a corporate wide, possibly distributed, database)

If you are positing that A's database is private to A and is updated by events from other processes, then I think you are just reinventing a distributed database.

I do think your note is a valuable description of how EDA and web services can be integrated. If the arrows in that diagram were reversed I would be happy to implement such a system, however I cannot see what you seem to be proposing as being helpful. Am I missing something obvious?

# orderedItems[].object.contentMap.en
@lutzhuehnken
I think I am with OK-Steak on this.

Stock levels and pricing, for example, would just be in the database. No events required. (I am assuming a corporate wide, possibly distributed, database)

If you are positing that A's database is private to A and is updated by events from other processes, then I think you are just reinventing a distributed database.

I do think your note is a valuable description of how EDA and web services can be integrated. If the arrows in that diagram were reversed I would be happy to implement such a system, however I cannot see what you seem to be proposing as being helpful. Am I missing something obvious?

# orderedItems[].object.content
@lutzhuehnken Not really.
How could B and C possibly know beforehand what to publish?

Service A has to, as you say in the note, "handle them on its own".

I see it as A performing the user transaction and then creating an event that B and C use to perform subsequent processing (e.g pick and send, and warehouse restocking).

On the other hand if B and C are responding to A then you have just created an asynchronous SOA which would be a rather poor idea.

# orderedItems[].object.contentMap.en
@lutzhuehnken Not really.
How could B and C possibly know beforehand what to publish?

Service A has to, as you say in the note, "handle them on its own".

I see it as A performing the user transaction and then creating an event that B and C use to perform subsequent processing (e.g pick and send, and warehouse restocking).

On the other hand if B and C are responding to A then you have just created an asynchronous SOA which would be a rather poor idea.

# orderedItems[].object.content
@lutzhuehnken
Mostly a good description of how to integrate #EDA into a real world system.

However I am a bit confused by your third diagram and what the arrows labelled with "i" represent. Event messages would surely go the other way?

It might be worth reinforcing the idea that the user interface process replaces any of its processing that is not vital for the transaction with an event that can be handled later.

# orderedItems[].object.contentMap.en
@lutzhuehnken
Mostly a good description of how to integrate #EDA into a real world system.

However I am a bit confused by your third diagram and what the arrows labelled with "i" represent. Event messages would surely go the other way?

It might be worth reinforcing the idea that the user interface process replaces any of its processing that is not vital for the transaction with an event that can be handled later.

# orderedItems[].object.content
@GeePawHill
I guess I am saying that a UBI needs to be provided by something similar to your Federal Reserve Bank and based on some sound economic theory (that might be an oxymoron).

Otherwise it will be just a political plaything that will end up as a mess.

# orderedItems[].object.contentMap.en
@GeePawHill
I guess I am saying that a UBI needs to be provided by something similar to your Federal Reserve Bank and based on some sound economic theory (that might be an oxymoron).

Otherwise it will be just a political plaything that will end up as a mess.

# orderedItems[].object.content
@GeePawHill
True, but it is mostly fairly indirect. UBI would be a very direct mechanism.

# orderedItems[].object.contentMap.en
@GeePawHill
True, but it is mostly fairly indirect. UBI would be a very direct mechanism.

# orderedItems[].object.content
@GeePawHill
The benefits seem to be real.

The issue I have is how do you stop it from becoming a means for controlling the population?

# orderedItems[].object.contentMap.en
@GeePawHill
The benefits seem to be real.

The issue I have is how do you stop it from becoming a means for controlling the population?

# orderedItems[].object.content
@oldrawgabbit
My go to for that sort of task is FFmpeg.

# orderedItems[].object.contentMap.en
@oldrawgabbit
My go to for that sort of task is FFmpeg.

# orderedItems[].object.content
@FantasticalEconomics
What is required is something that acts to counter market concentration.
A tax that was proportional to market share is one idea, but I expect some smart economists can think of other mechanisms.

# orderedItems[].object.contentMap.en
@FantasticalEconomics
What is required is something that acts to counter market concentration.
A tax that was proportional to market share is one idea, but I expect some smart economists can think of other mechanisms.