Hacker News: Firfi

New comment by Firfi in "Guide to data tools landscape for developers"

Firfi — Thu, 16 Jul 2026 15:31:13 +0000

Now I'll be thinking of "L" in ETL as "Land" and not "Load". Although the article doesn't propose that but uses a lot of "Land" terminology. "Load" => "load where? or FROM where?" - ambiguous "Land" => "land where?" - clear

New comment by Firfi in "Model-Based Testing for Dungeons & Dragons"

Firfi — Fri, 10 Apr 2026 16:32:35 +0000

That's a great idea, in fact. I'll try it out next time. Maybe even a mix, because I do sometimes want to be very specific about some expressions and experiment with wordplay

New comment by Firfi in "Model-Based Testing for Dungeons & Dragons"

Firfi — Fri, 10 Apr 2026 16:28:58 +0000

In my view, the edge cases like so (I think peasant railgun even mentioned in dm handbook) are more of a community problem than the game's. If it can be called a problem, of course - some tables enjoy those shenanigans, some don't.

What players and DMs are forgetting more often than not is the wording somewhere in the start of dm book: dm can overrule any rule. [to facilitate the game mood and direction that the table has agreed upon] [and a larger overarching problem is probably that there's often no such agreement before the game]

New comment by Firfi in "Model-Based Testing for Dungeons & Dragons"

Firfi — Fri, 10 Apr 2026 16:22:26 +0000

That's the plan! D&D combat can be a slog sometimes, and when it is, that kills a lot of fun for me as a story-first approach adept. I'd really just ask about that or that rule from a chatbot, or have a list of weighted actions presented to me at my turn. That's where I'm moving towards - a good spec is hopefully what should enable that direction. Hopefully...

New comment by Firfi in "Model-Based Testing for Dungeons & Dragons"

Firfi — Fri, 10 Apr 2026 16:03:57 +0000

Sorry for that, everyone. I did use the AI to help me with structure and English. I thought I'd proofread and edited that enough to be readable, but apparently it still smells. I'll update the wording soon.

New comment by Firfi in "Model-Based Testing for Dungeons & Dragons"

Firfi — Fri, 10 Apr 2026 15:49:53 +0000

Right. Quint is not used in runtime and is not supposed to be. It's a strong testing layer. But there's much more to it. My bigger idea is that I would generate whatever implementation from it, hopefully, with an agentic loop - the MBT test is a natural feedback harness to leave coding overnight. So dnd-rust at some point, maybe? If someone develops a game, they would be able to generate a core logic in rust for bevy, in c# for unity, in (whatever it's used there) for godot. That's in an ideal world.

New comment by Firfi in "Model-Based Testing for Dungeons & Dragons"

Firfi — Tue, 07 Apr 2026 13:15:41 +0000

Dungeons & Dragons rules are a spec spanning thousands of pages, not formalized, but thoroughly tested by the community. Moving them to a formal specification language (Quint) was an obvious next step. It worked and proved to also be a great LLM self-checker.

Model-Based Testing for Dungeons & Dragons

Firfi — Tue, 07 Apr 2026 13:15:41 +0000

Article URL: https://www.loskutoff.com/blog/model-based-testing-dnd/

Comments URL: https://news.ycombinator.com/item?id=47674894

Points: 109

# Comments: 76

New comment by Firfi in "Vibe code isn't meant to be reviewed"

Firfi — Mon, 16 Jun 2025 15:10:00 +0000

Thank you (twice!) for reading it. The idea wrapped in a scandalous topic indeed, but the PR process ambiguity was also what was the last straw for me to write it.

New comment by Firfi in "Vibe code isn't meant to be reviewed"

Firfi — Mon, 09 Jun 2025 16:53:25 +0000

That's one of my biggest frustrations - I wasted a lot of time on reprompting. I was making myself stick to 100% LLM approach for a while, in order to learn.

I can't say for everyone, but for me it's hit-and-miss: if LLM starts with "Oh, sorry, you're right" that's a STRONG signal I have to take over right now or rethink the approach, or I get into the doom spiral of reprompting and waste half a day on something I could've done myself by that point, with only difference that after half a day with a coding agent I discovered no important domain or technical knowledge.

So, "how much" to me depends so very much on seemingly random factors, including the time of the day when Antropic decides to serve their quantised version instead of a normal one. On non-random too, like how difficult the domain area is, how well you described it in the prompt, and how well you crafted your system queries. And I hate it very much! At this point, I'm trigger-happy to take over the control and write the stuff that LLM can't in the "controlling package" and tell it to use it as an example / safety check.

New comment by Firfi in "Vibe code isn't meant to be reviewed"

Firfi — Mon, 09 Jun 2025 16:36:25 +0000

It seems to me we have to find out how to figure out "what matters" to have the benefits that 10x vibe coder bros promise. I think we still have to review (despite my clickbait title), it's just different things that we are looking for in slop, and different type/amount of mental strain required. For more important libs, I guess we can "overshoot" a bit and put more time into vetting vibe code (and making it the guardrail code). While in the "next revolutionary React Todo App" the balance could be much farther towards vibe...

New comment by Firfi in "Vibe code isn't meant to be reviewed"

Firfi — Mon, 09 Jun 2025 16:14:05 +0000

I actually do recommend reviewing manually - it's just very convenient to see when a person wrote something (then much more scrutiny can be applied) vs. when the work was outsourced to AI. I feel like there is another application though, but didn't mention it for it's not that clear to me yet: you can yet again estimate whether a new programmer can actually code or if they 10x YOLO their way slowly bringing codebase maintainability down.

New comment by Firfi in "Vibe code isn't meant to be reviewed"

Firfi — Mon, 09 Jun 2025 15:59:29 +0000

Just feeling and experience, really. For me, if I spent time with the vibe code snippet and improved it until I can say "yes I would've written this" it's not slop anymore, even if it was written by Claude initially.

On the contrary, if I glanced over the code and could say "ok it doesn't look terrible, no obvious `rm -rf` and all", even if I changed a couple obvious mistakes, I still consider it vibe.

New comment by Firfi in "Vibe code isn't meant to be reviewed"

Firfi — Mon, 09 Jun 2025 15:34:29 +0000

After some vibe coding frustrations, ups and downs, I found that splitting the code explicitly into well-curated, domain-heavy guidance code and code marked “slop” can solve a lot of frustration and inefficiency.

We can be honest in our PR, “yes, this is slop,” while being technical and picky about code that actually matters.

The “guidance” code is not only great for preserving knowledge and aiding the discovery process, but it is very strong at creating a system of “checks and balances” for your AI slops to conform to, which greatly boosts vibe quality.

Helps me both technically (at least I feel so) with guiding claude code to do exactly what I want (or what we agreed to!) and psychologically because there's no detachment from the knowledge of the system anymore.

Vibe code isn't meant to be reviewed

Firfi — Mon, 09 Jun 2025 15:34:29 +0000

Article URL: https://monadical.com/posts/vibe-code-how-to-stay-in-control.html

Comments URL: https://news.ycombinator.com/item?id=44225543

Points: 19

# Comments: 26

New comment by Firfi in "Mindfulness in TypeScript code branching, or how to if/else"

Firfi — Thu, 09 Jan 2025 15:21:56 +0000

Hey folks, sometimes on PRs, I find that people aren't well-versed in the intricacies of code branching. So, I wrote a short article to educate fellow engineers and point to it sometimes so I don't have to explain things over and over.

Specifically, many people apparently don't know yet about exhaustiveness and the statement/expression dichotomy and how TS type system can help with it.

Mindfulness in TypeScript code branching, or how to if/else

Firfi — Thu, 09 Jan 2025 15:21:55 +0000

Article URL: https://monadical.com/posts/if-else-1.html

Comments URL: https://news.ycombinator.com/item?id=42646517

Points: 6

# Comments: 1

New comment by Firfi in "TypeScript Validators Feature Comparison"

Firfi — Fri, 20 Sep 2024 14:49:36 +0000

An app with typescript validators features tests. The test case is based on real use cases but is kept generic. Tests more advanced stuff like algebraic data types, template literals, nominal types, and recursive types. It's not a performance/size benchmark; there's a really nice performance benchmark app that exists already (I linked it there).

TypeScript Validators Feature Comparison

Firfi — Fri, 20 Sep 2024 14:49:36 +0000

Article URL: https://www.typescript-validators.com/

Comments URL: https://news.ycombinator.com/item?id=41602550

Points: 8

# Comments: 1

New comment by Firfi in "Building a Ticketing System with Solana Mobile and Metaplex Foundation Umi"

Firfi — Tue, 16 Apr 2024 18:03:15 +0000

Hey, sharing my colleague's @juanArias8 article on Solana Mobile here. He'll answer questions/comments in this thread if any popup.