rbalicki

11 ms·

1.
by rbalicki 2mo ago
My "favorite" aspect of the Slack web app, which might have been fixed, as I haven't seen it recently, is if you typed up -> r (I believe it's r) to open the emoji picker, typed a few characters (e.g. "eyes"
2.
by rbalicki 2mo ago
"For AI agents". I understand why everything needs to be marketed in this way, but it's just ... an easy-to-generate language for expressing charts. That's impressive! That's useful.
3.
by rbalicki 3mo ago
Speculating here, but perhaps your coworker was too ambitious? In my opinion, you should start with AI-generated PRs that do small, linting refactors and then work up from there. In particular, if this is done in parts, one of the strategie
4.
by rbalicki 3mo ago
I'll add another use case for letting an AI go ham: many small, atomic refactors where the name of the game is never breaking anything. My personal OSS projects don't have the scale to necessarily make this worth it, but at work I
5.
by rbalicki 3mo ago
Folks that are interested in a way of doing work locally that doesn't suck, but which integrates LLMs, may be interested in [Barnum]( https://barnum-circus.github.io/ ). The TLDR is that it's a programming language
6.
by rbalicki 4mo ago
That's exactly the tradeoff I made with Barnum ( https://barnum-circus.github.io/ ). It's just not important to optimize the performance of the rust side for the reason you stated. So instead, all focus goes into ma
7.
Is GraphQL dead? (GraphQL Conf 2025 talk, YouTube) [video](youtube.com)
3 points by rbalicki 5mo ago|1 comments
8.
by rbalicki 5mo ago
Hey folks! This talk is about GraphQL in a world of fullstack, rich clients and about Isograph. The question it asks is: does GraphQL need to exist? Can we get its benefits without a GraphQL schema, without a GraphQL server, and without sen
9.
by rbalicki 5mo ago
A simple task ("convert this file from JS to TS, here are the types of all imported things") is much more likely to continue to work with a nerfed model compared to a complicated task ("convert this repo to TS, make sure to r
10.
by rbalicki 5mo ago
Yes, exactly! Check out https://github.com/barnum-circus/barnum/blob/master/demos/ba...
11.
by rbalicki 5mo ago
You may want to check out Barnum, which is a programming language/agent orchestration tool that makes it easy to build things like /loop, or Claude code routines. And you won't end up dependent on the specifics of how Claude
12.
by rbalicki 5mo ago
If you want to feel like you're using a programming language when orchestrating agents, check out https://github.com/barnum-circus/barnum
13.
by rbalicki 5mo ago
You can lessen your dependence on the specific details of how /loop, code routines, etc. work by asking the LLM to do simpler tasks, and instead, having a proper workflow engine be in charge of the workflow aspects. For example, this d
14.
by rbalicki 6mo ago
I'm as nerdy as they come (my current project is the fourth compiler I've worked on), and I absolutely love this new way of working. There's a lot more time spent in discussion with the agent (an extremely frustrating discuss
15.
by rbalicki 6mo ago
I agree. I think we simply don't have the tools yet to hold agents to that high architectural standard. It simply takes a lot of focused effort and berating and close comprehension of the code at the moment to ship anything good, but t
16.
by rbalicki 6mo ago
I think what you're implying is that the agent ships unmaintainable slop. Certainly, if I don't pay attention and review the code line by line, it will ship slop. And even sometimes, when I'm certain that it is implemented on
17.
by rbalicki 6mo ago
The skill atrophy point strikes me as tenuous at best. Obviously, the plural of anecdote is not data, but I find myself able to work on projects of greater complexity than I would have been able to otherwise. 90% of my time is spent going b
18.
Ask HN: Feature request: include the second path segment for GitHub URLs
3 points by rbalicki 8mo ago|1 comments
19.
by rbalicki 9mo ago
I may be wrong on the details, but with URQL: - you don't have a normalized cache. You may not want one! But if you find yourself annoyed that modifying one entity in one location doesn't automatically cause another view into that
20.
by rbalicki 9mo ago
You may be interested in checking out https://www.youtube.com/watch?v=lhVGdErZuN4 , where I talk about the benefits of Relay. This isn't (currently) possible without GraphQL, so it's a pretty compelling case for Gr
21.
by rbalicki 9mo ago
Yeah, you can get a lot of features out of the same primitive. The primitive (called loadable fields, but you can think of it as a tool to specify a section of a query as loaded later) allows you to support: - live queries (call the loadabl
22.
by rbalicki 9mo ago
I would encourage you to write an educated person's critique of GraphQL, because OP's article + https://bessey.dev/blog/2024/05/24/why-im-over-graphql/ etc. suck up all of the oxygen, and
23.
by rbalicki 9mo ago
This is a genuinely accurate critique of GraphQL. We're missing some extremely table-stakes things, like generics, discriminated unions in inputs (and in particular, discriminated unions you can discriminate and use later in the query
24.
by rbalicki 9mo ago
There's an informed critique of RSC, but no one is making it.
25.
by rbalicki 9mo ago
Incidentally, v0.5.0 of Isograph just came out! https://isograph.dev/blog/2025/12/14/isograph-0.5.0/ There are lots of DevEx wins in this release, such as the ability to create have an autofix creat
26.
by rbalicki 9mo ago
100% agree on the unnecessary connection between entrypoints and meta internals. I think this is one of the biggest misses in Relay, and severely limits its usefulness in OSS. If you're interested in entrypoints without the Meta intern
27.
by rbalicki 9mo ago
Just released the next version of Isograph https://isograph.dev/blog/2025/12/14/isograph-0.5.0/ TLDR the incremental compiler rewrite is finally bearing fruit. Namely, because we no longer have a ba
28.
by rbalicki 9mo ago
#1 unnecessary network waterfalls #2 downloading the same fields multiple times #3 downloading unneeded data/code Checks out
29.
by rbalicki 9mo ago
If you're interested in an example of really good tooling and DevEx for GraphQL, then may I shamelessly promote this video in which I demonstrate the Isograph VSCode extension: https://www.youtube.com/watch?v=6tNWbVOjpQ
30.
by rbalicki 9mo ago
1000%. There's almost no reason to use GraphQL unless you take advantage of data masking + fragment colocation.

More ›