joshka

9 ms·

151.
by joshka 5mo ago
Is this comment LLM generated?
152.
by joshka 5mo ago
Ha - I see it's Ratatui based. Nice work there :D
153.
by joshka 5mo ago
I recommend VHS generally for these (we use them for all the ratatui screenshots generally). I'm also playing around with doing a rust version of this ( https://www.joshka.net/betamax/ )
154.
by joshka 6mo ago
I haven't used homebridge, but have used HA in the past when I had lights and things hooked up. The UX and configuration surface always felt janky to me. So many little paper cut annoyances across every control / window / men
155.
by joshka 6mo ago
Mitchell Hashimoto has a great response on lobste.rs https://lobste.rs/s/ifbdw1/text_mode_lie_why_modern_tuis_are... > It isn't fair to blame TUIs. > The real problem is that pretty much the whole stack
156.
by joshka 6mo ago
It feels like this should be no_track, for consistency with no_color
157.
by joshka 6mo ago
A much more charitable reading of the article is "here's some observations I found interesting / different". I met the author at the conf and watched their talk. Their perspective was very much in the camp of exploration
158.
by joshka 6mo ago
Probably on topic here - I talk like an LLM sometimes, and parse my points through them sometimes. I’d reasonably use that terminology and think nothing of it as it’s precise and correct. That said, this was partially LLM and my thinking he
159.
by joshka 6mo ago
The weird-looking Rust isn’t really Rust being weird, it’s the type telling the truth. Result<Option<Result<Message, WsError>>, Elapsed> That’s three independent “not the happy path” channels: timeout, stream close
160.
by joshka 6mo ago
The author's premise is that these all follow similar models to github and that's the problem they're calling out.
161.
by joshka 6mo ago
yeah, you can have github actions setup on arbitrary pushes to your branches, but there's not a good interface for linking actions to bare commits, and then having conversations etc. The place where that happens is usually a PR.
162.
by joshka 6mo ago
>it is mostly your build-systems' job to be hermetic, run anywhere, handle cross-builds etc. yes, and... the idea here is that it would be neat to extend the hermetic builds idea such that this can be run locally / anywhere whe
163.
by joshka 6mo ago
*.localhost works btw https://datatracker.ietf.org/doc/html/rfc6761#section-6.3
164.
by joshka 6mo ago
A similar term (often found as a reaction to Amazon LPs) is frupidity.
165.
by joshka 6mo ago
If you want to go much deeper, https://www.copyright.gov/ai/ is particularly good at least on the side of comprehensiveness.
166.
by joshka 6mo ago
Awesome. Definitely need to highlight this better somewhere on the main page (probably /pricing and in the /docs pages), but https://dashboard.plaid.com/ has it. More vague plans right now.
167.
by joshka 6mo ago
I love the phrasing of this line in the article: > It quietly defines the ceiling of your ambition and the floor of your operational risk.
168.
by joshka 6mo ago
try `git clone --filter=blob:none` instead https://github.blog/open-source/git/get-up-to-speed-with-par... https://gitperf.com/chapter-11.html
169.
by joshka 6mo ago
I'm curious how reasonable it would be for a person, rather than a company, to have a plaid sub.
170.
by joshka 6mo ago
> Don’t meet your heroes. I paid 5k to take a course by one of my heroes. He’s a brilliant man, but at the end of it I realized that he’s making it up as he goes along like the rest of us. Ha yup - I've felt this one before :D
171.
by joshka 6mo ago
> The most underrated skill to learn as an engineer is how to document. Fuck, someone please teach me how to write good documentation. Seriously, if there’s any recommendations, I’d seriously pay for a course (like probably a lot of mone
172.
by joshka 6mo ago
jjk or jjview I have a PR up for jjk that does the full change as a review changes, and there's another user's PR that allows diffs over arbitrary ranges (i.e. when working out whether the commits that make up a PR are good as a w
173.
by joshka 6mo ago
> An open question is whether the AIs could find optimizations that are not possible if we use a higher-level language like C or C++. It is an intriguing question that I will seek to answer later. For the time being, the AIs can beat my
174.
by joshka 6mo ago
The rust crate clap which is one of the more well known crates for command line parsing gets about 2M downloads a day and has this convention built in. This convention existed before clap came into being, but I don't recall when I firs
175.
by joshka 6mo ago
> Does JJ really prefer for me to think backwards? It wants me to start with the new and describe command, but with git I first make the changes and name the changeset at the end of the workflow. A good way to think of it is that jj new
176.
by joshka 6mo ago
The cli and a few concepts have evolved with time past the model's knowledge cutoff dates, so you have to steer things a bit with skills and telling it to use --help a bit more regularly. I find it reasonably good with lots of tweaking
177.
by joshka 6mo ago
The last reviewed sha is generally available on the PR page (not the changes page) when you force push. There should be a changes since review link somewhere near the push. When reviewing, you can also mark individual files as reviewed (use
178.
by joshka 6mo ago
I use jj fairly regularly and I'm trying to understand what your approach means, but having difficulty following what you want to acheive here. Seems like you're using ambiguous language that isn't aligned - wdym by marks?
179.
by joshka 6mo ago
yeah - absolutely. I use codex all the time with jj and encourage it to check the help for details about how to run commands as the commands / args / flags have evolved post training-cutoff date.
180.
by joshka 6mo ago
Any rust cli built with clap or go cli built with cobra supports short and long help and surface these with `-h` and `--help` (I think cobra surfaces this in the help command rather than in the --help, which is probably a reasonable alterna

More ›