HackerLangs
トップ新着トレンドコメント過去質問紹介求人

nivertech

no profile record

投稿

Beads: A coding agent memory system

steve-yegge.medium.com
19 ポイント·投稿者 nivertech·9 か月前·1 コメント

コメント

nivertech
·先月·議論
The Soviet computer industry had only two secrets:

1. how far behind the West it was, and

2. that there were no other secrets
nivertech
·先月·議論
This Soviet project developed two Russian-language PLs: Robic[1] and Rapira[2]. Robic was similar to Logo, but unlike Logo, which had only one actor - a turtle, Robik had several: a Train, an Ant, a Painter, and so on

Rapira was more like SETL + Python. It was a dynamic interpreted PL with a rich set of compound data types, such as sets, records (associative arrays), and so on. Compared to the contemporary BASIC, it was ADVANCED

Like Logo, Robik was used to teach programming to kindergarthen-age children, while Rapira was aimed at high school students

---

1. https://en.wikipedia.org/wiki/Robic / https://ru.wikipedia.org/wiki/%D0%A0%D0%BE%D0%B1%D0%B8%D0%BA

2. https://en.wikipedia.org/wiki/Rapira / https://ru.wikipedia.org/wiki/%D0%A0%D0%B0%D0%BF%D0%B8%D1%80...
nivertech
·2 か月前·議論
Even if you have an insurable interest, moral hazard may arise - acting recklessly or other abuse, while knowing you are insured/covered. Somewhat similar to friendly fraud in retail/ecommerce.
nivertech
·2 か月前·議論
AI talk is turning into Silicon Valley pseudo-math slang. Priors, exponentials, latent space

You get lines like “no priors” or “embracing exponentials” that sound smart but mostly signal status

Same move as N Taleb and “convexity.” A real idea turned into a generic intellectual flex
nivertech
·2 か月前·議論
> slow is smooth, smooth is fast
nivertech
·3 か月前·議論
https://paulgraham.com/articles.html
nivertech
·3 か月前·議論
It's better to first show truth tables, then K-maps, and only then logical formulas.

But the main question is: does this FP2 have any real applications? Maybe it could be useful when only one operand is FP2? Especially for vectorized math.
nivertech
·3 か月前·議論
What about comparison operators?
nivertech
·3 か月前·議論
The Five Levels: From spicy autocomplete to the dark factory

https://www.danshapiro.com/blog/2026/01/the-five-levels-from...

January 23, 2026

72 comments

https://news.ycombinator.com/item?id=46739117

There are several other similar posts/videos. Steve Yegge also talks about it.
nivertech
·3 か月前·議論
FP2 spec:

  00 -> 0.0
  01 -> 1.0
  10 -> Inf
  11 -> NaN
or

  00 -> 0.0
  01 -> 1.0
  10 -> Inf
  11 -> -Inf
nivertech
·3 か月前·議論
The number of traditional public companies has been cut in half.

The number of alternative public and semi-public companies went up exponentially (Reg CF/Reg A, crypto ICOs).

After reaching some thresholds a Reg A company can become public and even trade on OTC markets.
nivertech
·3 か月前·議論
Windows (arm 64), but no official Linux (x86) support?

There is only unofficial build:

Claude Desktop for Debian-based Linux distributions

https://github.com/aaddrick/claude-desktop-debian
nivertech
·3 か月前·議論
statistics == lies
nivertech
·3 か月前·議論
BTW: some early filesystems were more database-like:

https://en.wikipedia.org/wiki/ISAM

https://en.wikipedia.org/wiki/Record_Management_Services

They were more like BerkeleyDB and lacked Query Planner.

I think Oracle internally using something similar, i.e. a native filesystem optimized for an RDBMS.
nivertech
·3 か月前·議論
“The North Atlantic Treaty Organization Without Atlantis?”
nivertech
·3 か月前·議論
The slogan of the Russian Revolution of 1917 was: "Factories to the workers, land to the peasants."

If the factory is yours, then everything inside is yours ;)

But it's funny how low wages under the broken Soviet economic system turned such things into a semi-official, informal work perks, allowing people to make ends meet.
nivertech
·3 か月前·議論
1. The problem is with using HTTP for APIs, not with GraphQL. HTTP was designed for rich (hypertext) documents, not for APIs. So layering GraphQL or any other APIs over HTTP is a hack.

2. GraphQL is useful for small remote teams b/c of mandatory staticly-typed schema and built-in schema documentation. Otherwise it's lots of back-and-forth between backen, frontend, QA, etc. You forced to use external tools like Postman collections, and still having communication problems.
nivertech
·3 か月前·議論
> After years of debate and confusion, the GraphQL Working Group has reached a historic decision: starting with the October 2027 spec release, all GraphQL responses will return random HTTP status codes between 100 and 599.

> Additionally in order to make GraphQL AI Agents friendly, the GraphQL response body will be switching from JSON to Markdown.
nivertech
·3 か月前·議論
Imagined vs discovered tasks

The way to really figure out what needs to be done is to start doing real work.

https://basecamp.com/shapeup/3.1-chapter-10#imagined-vs-disc...

  imagined   tasks ==      Jira
  discovered tasks == Dark Jira
IMO, tickets for planned work are an anti-pattern. Tickets are good for reactive work: bug reports, support, etc. Use Kanban board for tracking them.

Planned work should be organically discovered from the plan by the developers (or agents) who will be implementing it, not assigned via Jira tickets by the project manager. Shape Up recommedns using Hill Charts for per-scope (vertical slice) progress updates.
nivertech
·4 か月前·議論
yes here voice mode != hands-off mode, so you can't DWC (Driving-While-Coding)