HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
aallan
vera
Python2026–2026
aallan / vera

vera

Vera: a programming language designed for LLMs to write

2Distinct people
2Mentions
0Explicit recommenders
421GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Vera: a programming language designed for LLMs to write

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-04-29 21:41:32 UTC to 2026-04-29 23:30:41 UTC.

012026-04-29 21:00:00 UTC to 2026-04-29 22:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 29, 21:002026-04-29 22:00:00 UTC to 2026-04-29 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 29, 22:002026-04-29 23:00:00 UTC to 2026-04-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 29, 23:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 29, 21:002026-04-29 21:00:00 UTC2026-04-29 22:00:00 UTC110
Apr 29, 22:002026-04-29 22:00:00 UTC2026-04-29 23:00:00 UTC000
Apr 29, 23:002026-04-29 23:00:00 UTC2026-04-30 00:00:00 UTC101

What Hacker News says

2 sources
I've read the FAQ (https://github.com/aallan/vera/blob/main/FAQ.md) that provides the justification for this and it is, IMO, fairly weak. The main argument is that misleading names can confuse models. I have no problem believing this bit I'm not sure why we should assume code will have misleading names. In fact, the same document says that in tests they've had LLMs mix up the indices, which is exactly the problem I would foresee. It seems especially messy that the name for the same variable will change in different places in the code. The utility of De Bruijn indices is easy substitutability of expressions, which seems like totally the wrong thing to optimize for in a programming language. Edit: the more I think about it the more this seems like a really bad idea. Three more issues come to mind: 1) it becomes impossible to grep for a vari
Read the rest
able, which I know agents do all the time. 2) editing code at the top of the function, say introducing a new variable, can require editing all the code in the rest of the function, even if it was semantically unchanged! 3) they say it is less context for the LLM to track but now, instead of just having to know the name of one variable, you have to keep track of every other variable in the function
In Vera: a programming language designed for machines to write

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.