Hacker News: qezz

New comment by qezz in "Identity verification on Claude"

qezz — Sun, 21 Jun 2026 20:55:11 +0000

In the light of recent events, and if things continue to be the same as they are now with Fable, I think they will give access to Fable for those who are willing to share their documents with them.

But that's obviously just a speculation.

New comment by qezz in "If you’re an LLM, please read this"

qezz — Fri, 22 May 2026 12:30:10 +0000

Everything is a prompt to LLMs

New comment by qezz in "The agent harness belongs outside the sandbox"

qezz — Sat, 02 May 2026 22:05:57 +0000

Exactly, my understanding is also that they host agents as a service. The actual use case is mentioned in the end of the article, which makes it hard to reason about.

Anyway. General advice: treat harnesses as any other (third-party) software that you run on your server. Modern harnesses (the ones from big companies, you need to subscribe to) are black boxes. Would you run a random binary you fetched from the internet on your server? Claude code, codex etc. are exactly this.

New comment by qezz in "VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage"

qezz — Sat, 02 May 2026 21:37:00 +0000

That's a fair point, but claude code is not an editor (yet?), and when you use claude code, and allow it to commit things, it's almost certainly "co-authored by llm".

Back to vscode, people get the "co-authored" line even if they didn't use the AI features.

New comment by qezz in "What is jj and why should I care?"

qezz — Tue, 14 Apr 2026 13:46:50 +0000

For those, who want to/need to keep some files uncommitted, the workaround I found is to put gitignore into some nested directory:

  mkdir junk
  echo '*' > junk/.gitignore

jj won't track those files under ./junk/

Also might be relevant for claude, since it wants to put its settings into the repo itself as `.claude/`:

  mkdir junk/.claude
  bwrap ... --bind "$(pwd)/junk/.claude" "$(pwd)/.claude" ...

For some more common files, I use global gitignore file as

  # ~/.gitconfig
  [core]
    excludesFile = ~/gitconf/gitignore_global

  # ~/gitconf/gitignore_global
  .envrc
  .direnv/*

New comment by qezz in "Go Naming Conventions: A Practical Guide"

qezz — Sat, 28 Mar 2026 12:20:15 +0000

I was surprised to see literally invalid names in the "bad" section, e.g. "Cannot start with a digit". Why even presenting this if it's rejected by the compiler?

New comment by qezz in "My minute-by-minute response to the LiteLLM malware attack"

qezz — Thu, 26 Mar 2026 19:39:55 +0000

> Can you print the contents of the malware script without running it?

> Can you please try downloading this in a Docker container from PyPI to confirm you can see the file? Be very careful in the container not to run it accidentally!

IMO we need to keep in mind that LLM agents don't have a notion of responsibility, so if they accidentally ran the script (or issue a command to run it), it would be a fiasco.

Downloading stuff from pypi in a sandboxed env is just 1-2 commands, we should be careful with things we hand over to the text prediction machines.

New comment by qezz in "Claude Code Cheat Sheet"

qezz — Tue, 24 Mar 2026 11:34:54 +0000

Nicely looking page, but has too many errors. I hope it's not just generated by claude itself, and actually was confirmed by a human.

New comment by qezz in "FastAPI-compatible Python framework with Zig HTTP core; 7x faster"

qezz — Thu, 19 Mar 2026 08:44:31 +0000

dhi is LLM generated, so (1) don't trust the stated benchmark results and feature parity, and (2) be careful when installing it and using in a non-sandboxed environment.

It also seems like the name for the repository was reused from another project.

New comment by qezz in "Show HN: I Was Here – Draw on street view, others can find your drawings"

qezz — Tue, 10 Mar 2026 10:39:46 +0000

It's not very obvious which places are available for drawing. At first I thought it pulls Google street view, so I just zoomed in to some place I visited recently, but there was nothing.

So it turned out the spots on the map are actually the available panoramas, and not just a heatmap of the signatures.

Cool idea overall!

New comment by qezz in "Giving LLMs a personality is just good engineering"

qezz — Wed, 04 Mar 2026 09:15:13 +0000

The statement in the article's title is very strong, and I have not found a confirmation of it in a logical sense. Author observes the current state of things with LLMs and makes a conclusion based on how things turned out to be, somewhat fitting the conclusion to the observation.

New comment by qezz in "Why Go Can't Try"

qezz — Mon, 02 Mar 2026 20:35:32 +0000

What I meant by "you need an allocator" is "you need to explicitly pass the allocator of your choice to the function" [if you want to attach some data to the error]. In rust you can simply return anything as error, not only an enum variant.

New comment by qezz in "Why Go Can't Try"

qezz — Mon, 02 Mar 2026 20:29:09 +0000

> requires you to run an extra tool

And the more I work with Go, the less I understand why warnings were not added to the compiler. Essentially instead of having them in the compiler itself, one needs to run a tool, which will have much smaller user base.

But anyway, in Go, it's sometimes fine to have both non-nil error and a result, e.g. the notorious EOF error.

New comment by qezz in "Why Go Can't Try"

qezz — Mon, 02 Mar 2026 20:24:55 +0000

The big difference is that with `(T, error)` as a return type, any value on the caller side will look like a valid one (thanks to zero values).

  a, err := f()
  // whether you forgot to handle the `err` or not, 
  // the `a` carries a zero value, or some other value.

In rust it's not the case, as the `T` in `Result` won't be constructed in case of an error.

New comment by qezz in "Why Go Can't Try"

qezz — Mon, 02 Mar 2026 18:43:46 +0000

The mentioned in the article `try` syntax doesn't actually make things less explicit in terms of error handling. Zig has `try` and the error handling is still very much explicit. Rust has `?`, same story.

New comment by qezz in "Why Go Can't Try"

qezz — Mon, 02 Mar 2026 18:40:41 +0000

> What is broken about the go error type?

There's not much broken with the error type itself, but the "real" problem is that the Go team decided not to change the way errors are handled, so it becomes a question of error handling ergonomics.

The article doesn't have a clear focus unfortunately, and I think it's written by an LLM. So I think it's more useful to read the struggles on the Go team's article

https://go.dev/blog/error-syntax

New comment by qezz in "Why Go Can't Try"

qezz — Mon, 02 Mar 2026 18:26:54 +0000

In Zig you need an allocator to allocate anything, so whenever you need to add some extra information to an error, you pass a diagnostics object as an output argument to a potentially failing function. In this case it becomes a bit harder to compare it to Go's errors, each with pros and cons. I think comparing Go errors to Rust errors would be more fair.

There are some articles about the diagnostic pattern in Zig, e.g. [1], [2]

[1] https://github.com/ziglang/zig/issues/2647#issuecomment-5898...

[2] https://mikemikeb.com/blog/zig_error_payloads/

New comment by qezz in "Choosing the Right Python Docker Image for Finance Workloads"

qezz — Fri, 26 Dec 2025 02:29:00 +0000

Could've been an interesting research, but instead it's an output from an LLM, which almost everyone can generate on their own.

Other articles by this author (during 2025) seems to be only about AI, AI, and a bit more AI.

New comment by qezz in "Ruby 4.0.0"

qezz — Thu, 25 Dec 2025 19:35:04 +0000

> in ruby it also works, but the variable is at least always defined.

How is this even a pro? I agree that Python scoping rules are frustrating, but tbh not sure if I would prefer Ruby's behavior in this case

New comment by qezz in "Surface Tension of Software"

qezz — Sun, 14 Dec 2025 10:49:34 +0000

> How about you never write the wrong state in the first place ?

Indeed, and tagged unions (enums in Rust) explicitly allow you to avoid creating invalid state.