jasebell

Done me fine for the last decade. Along with all the other languages that kept me in employment. I still use it daily.

I absolutely loved it!

Gave me the old ZX Spectrum vibes when I first started, that adds to the charm.

More of this please!

Does anyone remember SpikeSource?

Could the code be open sourced? I care about whiskey much more.

I can provide slap bass if anyone needs it while reading.

If you career depended on it then you'd be nowhere near a LLM.

There are so many pointless waffle papers on LLMs now.

I've only seen one article predicting this. Bankruptcy means different things in different countries, so assuming a restructure of finance and payment of suppliers.

Still interesting to me. Is the AI winter coming (again)?

If you had access to the suppliers then it was an easy concept to copy. Those with the marketing budget were then going to be the winners.

That aside it was an interesting exercise of the combinatorial optimisation problem at scale.

Do away with cash and track everything. It's not a good look.

Nice work. Are you going to write a blog post on the process. Would love to read it.

Definitely worth looking at, the Bellman-Ford algorithm can traverse negative edges but is slower than Dijkstra's.

An interesting read!

First place I heard that question was on a Jasper Carrott concert from the late 70s. :)

Not looked, can't see me looking at this rate.

Years and years ago I worked at an organisation where I was expected to role play Dungeons and Dragons (polystyrene swords and all). When I refused it got tense.

The tipping point happened when I found a bug in the CTO's database code and it would run out of memory (not closing JDBC ResultSets). Then I started finding coins on the floor, I'd just pick them up and hand them in, I knew what was going on.

I didn't last long, glad I was ejected when I was.

Fortune’s Forumla by William Poundstone is an excellent book. Edward Thorpe has most of his papers published too, they’re all good for a read [though I cannot be held responsible if you’re going to beat the dealer at Blackjack, I don’t need Kelly to know how that will turn out :)]

No I haven't but I appreciate the headsup. It's been a few years since I even looked at anything on Azure in all honesty.

<<but one disk of one machine satisfies that need>>

Right now it does, later on it won't. Then it moves to Kafka.

It does ignore fault tolerance yes I agree, because right now I don't need it. When you're bootstrapping this stuff you want to be as lean as you can. The plan is to move to Kafka, which I do use a lot btw, when there's a case to move to that level of throughput. If I had my way now I'd use Kafka, my wallet on the other hand disagrees.

I know the reason for needing three machines for a Kafka cluster. And I'm certainly not pitching Durable Queue as a Kafka alternative unless, as in my case, the throughput will be so low in the initial stages as not to warrant a full Kafka cluster.

I could have run Kafka on a single node.....

The "a bit like Kafka", weak yeah it is but the solution posted presented a fairly quick way to establish a queue and decouple messaging from the running application, that was the whole point.