t-kalinowski

5 ms·

1.
by t-kalinowski 1mo ago
Seeing that list of tools you're using in automations, I'm guessing you'll enjoy this, as another tool to add to the pile: https://t-kalinowski.github.io/yamark/ (disclosure: I wrote it)
2.
by t-kalinowski 3mo ago
One project I’d add to the comparison is raghilda from Posit: https://posit-dev.github.io/raghilda/ raghilda is deliberately narrower than LangGraph/Haystack/etc. It focuses on the RAG parts: document ingesti
3.
by t-kalinowski 4mo ago
I wonder if YAML is better than JSON for LLMs, because the indentation keeps the nesting level information local to the content.
4.
by t-kalinowski 4mo ago
Because YAML is the worst config format, except for all the others. https://opensource.posit.co/blog/2026-05-21_in-defense-of-ya...
5.
by t-kalinowski 5mo ago
Memories are failable :) Here is the PR you merged June of last year, changing the file extension from `.qmd` to `.qd` after a discussion about Quarto: https://github.com/iamgio/quarkdown/pull/90
6.
by t-kalinowski 5mo ago
Counterpoint from a doctor: https://substack.com/inbox/post/189714240 Scribes _feel_ good in the short-term, but it's not clear if they're actually good on longer time horizons.
7.
by t-kalinowski 5mo ago
Very cool! We’ve been exploring a similar direction too, but with a plain REPL and a much thinner tool surface. In our case, it’s basically one tool for sending input, with interrupts and restarts handled through that same path. Marimo seem
8.
by t-kalinowski 5mo ago
I agree that at first glance, it seems like tmux, or even long-running PTY shell calls in harnesses like Claude, solve this. They do keep processes alive across discrete interactions. But in practice, it’s kind of terrible, because the inte
9.
by t-kalinowski 1y ago
Posit offers something similar to Microsoft’s CRAN Time Machine, but it works not only for CRAN, but also for Bioconductor and PyPI. You can add a date to the Public Posit Package Manager URL to access a snapshot of all packages from that d
10.
by t-kalinowski 1y ago
Or, don't even write the fortran manually, just transpile the R function to fortran: https://github.com/t-kalinowski/quickr
11.
by t-kalinowski 1y ago
This was the main reason I wrote promptdown. I want to be able to edit the full chat history every turn, and the append-only standard chat interfaces don't make that easy. https://github.com/t-kalinowski/promptdown
12.
Keras 3 for R(blogs.rstudio.com)
4 points by t-kalinowski 2y ago|0 comments
13.
by t-kalinowski 2y ago
The Python interop is in the blog post because it makes for convenient and compact examples, not because it motivated any of the features. If you're interested in what motivated S7, you may enjoy this talk Hadley gave: https:/&#x
14.
by t-kalinowski 2y ago
R does have namespaces. Take a look at the NAMESPACE file found at the root of every R package, which defines the symbols and methods exported by the package. Note for many R packages, the NAMESPACE file is autogenerated from roxygen docs:
15.
by t-kalinowski 3y ago
It's a new OOP system for R. repo: https://github.com/RConsortium/OOP-WG talk: https://www.youtube.com/watch?v=P3FxCvSueag&t=258s