i wished it would :-|

A hammer is a hammer because we need to drive nails .
( At least the hammers designed to drive nails.)

A hammer is a tool designed to drive nails.
The reason for building something / what is being built with the hammer,
that might be a discussion that relates to philosophy

@rendle.dev , I believe you should add some APL to the next version of BSLang

An experiment on EventSourcing & LLM & APL
"gimme an APL event sourcing lib , omit comments"
no clue of that works as I don't have the right keyboard for APL

x: "but.... what do I choose?"
Nick: [ Reply what you think @nick-tune.me would respond]

x: "I want this property"
Nick: "then do this"
x: "I want that property"
Nick: "then do that"
x: "but if I do this,I can't have that"
Nick: "yes they are mutually exclusive"
x: "and if I do that, I can't have this"
Nick: "yes, they are mutually exclusive"
Nick: "and the statement is commutative"

dual write problem ?
dual write problem ?

Keep it simple, bash and blame the rest:
Bashing anything is great for engagement,
especially among the type of folks we are, IT
It it easier and better for our ego:
we love to blame others for our problems
it is simpler to blame others for our problems
I mean we are looking for simplicity right?

additionally , a rise of serious security issues

With all the tooling we use adding Agent capabilities that we can't turn off easily we should prepare for a price increase pretty soon.

Stack.Pop()

I'd argue you should event source it :
A good article on the subject .
blog.bittacklr.be/the-workflow...

it existed in the 90s , though only a bandwidth problem back then
( and DNS of course)
paper shipping paper with text on it was way better bandwidth back then .

There is also another POV :
- Upcasting
->when you want your code to work , internally , exclusively on the new version

- Weak Schema
-> for the consumers to be able to keep their old code
( and I'd not make new field optional , I'd add with sane defaults in the producer)

AInemic model: When you delegate all modelling to a LLM

and when not possible: e.g: projecting to 1000s of file
- 1 checkpoint file to restart, can be behind: useful when restarting the projection host
each file contains the last checkpoint it was processed with , so that the projection can ignore in it receives previous data

Embrace uncertainty,
Make it explicit

Someone got to explain me Dev psychology:
Dev:

- Happily spends 100s $ monthly for a heavily rate limited LLM service. The return on investment is unproven

- Cries out loud when OSS projects try to get some money out of it to be able to sustain the project. ( proven return on investment )

All we primarily care about on the architecture , is for the bread to be edible

Tired of reading
"That is past thing stop using it, use That instead"
And, every single time, right after: a drawing / some text showing how This actually uses That .

More a museum than a garage @scott.hanselman.com !

All journeys have a beginning and an end, and sometimes, the end isn’t quite the destination you had hoped for. | 🤔 Yves L. All journeys have a beginning and an end, and sometimes, the end isn’t quite the destination you had hoped for. Today marks the end of my journey at Kurrent (formerly EventStore). While I didn't ...

Journey's have a beginning and an end.

www.linkedin.com/feed/update/...

Open For Work

Worse is the assumption that there is no process because some do not see the expected tools.
The process is not the tool .
The tool helps to accomplish task in the process

Read somewhere :"if something scares you in dev ... change the process."
What-if
1/ the process is actually ok ( more or less, improvement welcome)
2/ It's the humans who are not good / willing at following them
Seeing Too much one way thinking in the form of :
- it's the process that's wrong

Pro-tip:
Cool your web site is all based on some CSS ...
Just make sure it looks a _bit_ decent if the CSS does not load for some reason

Le fond avant la forme.
Substance before format

Not a thought leader
Just a Clueless Wanderer.
Because the journey is as important as the goal

Meaning :
* Beware of anthropomorphism.
* we _are_ being manipulated

"The discovery of the ELIZA effect was an important development in artificial intelligence, demonstrating the principle of using social engineering rather than explicit programming to pass a Turing test"

en.wikipedia.org/wiki/ELIZA_e...

Eliza Effect:
the humans’ assumption of which computer programs understand the user inputs and make analogies.