folex

Perhaps it would make sense to provide LLMs with some strategy guides written in .md files.

except that I put notes to plan document in a single message like:

   > plan quote
   my note
   > plan quote
   my note

one new thing for me is to review the todo list, I was always relying on auto generated todo list

On one end, you write / generate / assume a deserialisator that checks whether incoming data satisfies all required invariants, eg all fields are present. On the other end, you specify a type that has all the required fields in required format.

If deserialisation fails to satisfy type requirements, it produces an error which you can handle by eg falling back to a different type, rejecting operation or re-requesting data.

If deserialisation doesn't fail – hooray, now you don't have to worry about uncertainty.

The important thing here is that uncertainty is contained in a very specific place. It's an uncertainty barrier, if you wish: before it there's raw data, after it it's either an error or valid data.

If you don't have a strict barrier like that – every place in the program has to deal with uncertainty.

So it's not necessarily about dynamic / static. It's about being able to set barriers that narrow down uncertainty, and growing number of assumptions. The good thing about ergonomic typing system is that it allows you to offload these assumptions from your mind by encoding them in the types and let compiler worry about it.

It's basically automatization of assumptions book keeping.

Sure thing. Unless dev forgets to do (some of) these checks, or some code downstream changes and upstream checks become gibberish or insufficient.

I'm not a native english speaker, and I never heard that idea besides in, I'd guess, Friends TV show.

I've used thesauruses since my childhood for exactly the task of looking up meanings, explanations, perhaps some etymology baked in.

For English, I always use WordNet, it is quite good and works offline on Android.

For my basic level of Chinese, Outliers dictionaries are so far the best I have found, but that's mainly due to my heavy reliance on the etymology provided there.

Well, I guess I got carried away a bit. Back to my question, where thesaurus=synonyms+antonyms comes from?

mhm. single-handedly, though.

However, I'd recommend Murderbot series, it is full of humour and shares atmosphere of Bobiverse and this personal approach to characters, as well. Highly recommend.

Imagine describing how some system works, what it consists of, and get architecture images + process animations.

https://scribblediffusion.com/scribbles/nca3ivborbebhipju6jg...

Version incrementing, packaging wasms, dancing around code generation – all doable, but not standardized.

There's a release-please to automate all that, but it's not an easy task to set it up in all of your repos.

Besides, if in addition to Rust projects, you have projects in other languages like JavaScript, then you have to do it twice and struggle with understanding all of the package management systems provided by all languages you have.

A single swiss-army-knife package manager would be amazing.

I'm in a team that works on a pet prog lang for distributed systems, and we did some research of using an existing package managing system. We've settled on NPM for now, but god I wish there would be a better generic package manager out there.

https://fluence.network

Something like: there are 10 peers, A sends to B, B waits for C, yadayada.

Distributed VM over a p2p network.

https://fluence.one/join.html

https://github.com/fluencelabs

One of the target audience are distributed systems researchers: we provide a high-level strong-statically typed prog language for distributed systems.

Looking for:

    - Scala / Haskell people who are into writing compilers and designing prog langs are most wanted;
    - Distributed systems engineers and researchers;
    - People proficient in scaling p2p networks (if you exist!);
    - Engineering Manager;

Not just a dream. https://github.com/fluencelabs/fluence

Each peer in a p2p network can host multiple services and expose their API to the network. Each service, then, is a collection of WASM modules that interact with each other in FFI manner.

I believe poor networking performance was one of the reasons XMPP had to be customised in WhatsApp and overall didn't become as widely used as I'd like it to be :)

Is it still the case? Or was that problem addressed at standard level somehow?