chthonicdaemon

Metaculus has released a node based probabilistic calculation tool. They describe it as a tool for "mapping the forecasts behind a decision"

`.pgpass` is the second item in the setup after `.pg_service.conf`.

Tips for making the CLI expierience nicer for PostgeSQL databases

The notebooks aren't evaluated in reverse, but rather in the order they need to be to get the final results. Observable builds a DAG, similar to Marimo. You can put cells in any order you'd like.

I think that in all the notebook solutions I've seen that allow this, a culture emerges where the "final result" is put at the top so that you can find it easily and interact with it as a user. The actual development process involves writing stuff top down and then re-ordering it for use.

Most people really cannot tell you what they want in any reasonable way. So expecting good specs for software without a very laborious interview and review process is pure wishful thinking. People "know what they like when they see it", so spend time rapid prototyping.

Smaller and more recent: iTerm has deep tmux support. Just do `tmux -CC` to start your session or `tmux -CC a` to attach to it and you don't have to memorise all the tmux commands.

OP said they tried cursor and didn't experience a speedup over their vi macros.

Logseq is block-based while Obsidian is more focused on pages. If you want to build something like Wikipedia, Obsidian fits that well. If you're more used to notion and you think more in bullets, Logseq could be a better fit.

This still relies on being able to name the notes. My point was that you can play the music without knowing the names, so you need some other system like yours to get from the notated signature to the name (or other way around).

It sounds like you expect the collaborator to have one jupyter installation that you would pollute with the kernel. In my projects that use jupyter, I always have jupyterlab as one of the dependencies. Not sure about the naming part, since I usually just put my project in a directory named for the project, and uv uses that name for the venv, so I literally have never had to "come up with some name for the kernel".

In my case, I usually cd to the project directory, activate the associated environment, then do one of the following to work on a notebook in one of my projects, `jupyter lab`, `pycharm .`, or `code .` and go from there. In all of these cases, I get the ability to open notebooks that make use of this environment, either in the actual Jupyter lab interface, or in the tool's notebook interface (pycharm or vs code). All of these options make it pretty effortless to use the kernel associated with the environment - it's either automatically selected or it's the default in the dropdown.

I think there is true utility in choosing a unit scheme that matches your number scheme. So we use decimal numbers, makes sense to use decimal units. It seems you're arguing that the real mistake is using decimal numbers to begin with?

I have considered lessons but I didn't like the prospect of searching for a teacher. This particular piece of practice is only one part of my larger music-making activity. I make mostly electronic music using Ableton Live and a Push 2. I play guitar with enough proficiency that I don't feel like I need lessons. I started this sight reading excercise to access the sheet music I have and I'm using that just fine to learn pieces. So I guess I don't feel any particular frustration in my learning right now that would push me to ask for help. The main challenge I face in my music making is finding longer stretches of time to work on my songs.

I have found it immensely useful for quick GUI building on my phone.