HN user

ucirello

57 karma
Posts12
Comments25
View on HN
Local Git Remotes 2 months ago

That's what I used to do with git (just recently moved off of SVN) in a shared computer predating github. It works very well!

author here! Good suggestion, we should probably come up with some GOAL.md examples. With that said, one-shotting a pretty large app is a somewhat doable task, and that's one of the reasons we have introduced the interview step: exactly to let the model pull from you (instead you pushing into the model a spec document) what it needs to know to be able to work autonomously.

author here! I am not sure if I would phrase it as sane Gas Town. The design constraints are very different. For example, I tried to optimized for output density (the number of tokens that I didn't have to rewrite because the output quality was bad), instead of treating it as a distributed system and coordination problem. SGAI, for example, runs one agent at a time - maybe one day it will run more agents in parallel, but only as much that I can obtain better outputs (not more outputs).

Also, I am not a cryptocurrency enthusiast - and therefore, I wouldn't accept creating a memecoin out of it.

author here! it is my daily driver for quite some time; with that said, its current shape is a bit of a more recent development. Initially, I would manually handle jj workspaces and fire out screen/tmux sessions; but over time, I figure it would be nice to have an UI that I could browse from anywhere through a VPN.

It does take some investment -- by adding customizations through the overlay folder (`sgai/` directory at the root of the repository) -- but eventually it should be able to code in a way that you would approve in a PR.

author here! the decision was mine; if anything, the senior leadership was fine with an unencumbered open-source license. What I didn't want was someone using it to make a business out of this tool without me in the mix.

In a sense, a futile effort; because if you reverse engineer a nlspec and rebuild it, then you can have it with any license you may want.

author here!

I have been working on this for my own use until recently, when I shared with the rest of the team, and we thought it would be nice to let the world see it.

I have been interested in autonomous code development for quite some time (at least since March/April 2025) - and summer '25 is when I felt the models were good enough to be pushed to autonomy.

I wrote a bit about it[0], and sgai is the incarnation of my take on AI autonomous coding.

sgai is not even v0 yet, a lot of work to be done to improve its implementation - but I think it should be usable enough for those willing to give it a try.

0: https://cirello.org/aifactory.html

I will disagree with this list, in part. And I am thinking specifically of PHP. I am an emigrate from PHP ecosystem, I departed from PHP 11 years ago and never looked back. The number one reason that I left PHP is that #1 in your list was plainly false. There were _not_ high paying jobs in PHP, no matter how good you were or not. The whole point of using PHP is to pay as little as possible; and make developers as fungible as possible. And if a certain demographic yielded good quality developers for an even lower price point, I would certainly see whole teams being replaced to fit it. I was actually recruited, more than once, exactly for this reason.

Languages don't die, they ride into the sunset. There is enough inertia in PHP-ecosystem that you can still find jobs, but they are very often just legacy work jobs (at least in my area). No serious technical leader would pick PHP to execute on new work, except of course, if their main driver is to pay as little as possible and the language choice doesn't bubble up to investors' keyword-driven investment thesis.

VB6 and PHP are nice. I am skeptical of the affirmation that there is a lot of money in these ecosystems. The pie may be currently large, but I do not see it growing.

In the box of QuickBasic 4.25 Professional it has a BAS file that was exactly like this. Really neat. It even played sounds!

I am not sure any of what you described can be declared a success in any sense.

Failure #1: The language deployed a non-backward compatible change. Failure #1b: and their ecosystem thinks that's OK.

Failure #2: users only saw the need to upgrade the dependency because the language broke that dependency first. So unless they had some other reason to update the given dependency ahead of the compiler upgrade, they would be hit by the problem no matter what.

Failure #3: downplaying The importance of the breakage by implying the blast radius would've been smaller if the victim of the first two failures was a lesser known dependency.

I can't see any success - of the release process or in any other way.

And finally, framing a failure as success is one central problem I have with Rust ecosystem's toxic positivity. In any other healthy community the answer would be "OK, we made a mistake, let's run a post-mortem and do better", or even plain embarrassment - but Rust's ecosystem is the only one in which there's a failure in the joint of two releases processes and claim it as a "success story for [one of the] release process".

My hope, as bigger games adopt Rust (US Gov, MS, Linux etc) these attitudes will change.

Location: SF Bay Area, CA

Remote: Yes

Willing to Relocate: No

Technologies: Go, Docker (Dockerfiles creation, Hub publishing), Git, Test-driven development and generative-based testing, NSQd - deployment in HA mode, 12 factors, Shell scripting with Bash, Lock services (etcd, Consul, DynamoDB), Implementation of systems using Raft (etcd raft), Domain-driven design, BASE architecture, CAP theorem, Memcached, Object-oriented programming, Linux (Ubuntu), MySQL, PostgreSQL, VPN (Wireguard), AWS (EC2, ELB, EIP, Route 53, RDS), Scrum, 5S, Lean startup, XP, Proven record of project leadership, QFD

CV: https://cirello.org/cv.html

Email: hire@cirello.eu

----

I am interested also in positions involving Rust or Python

  Location: SF Bay Area, CA
  Remote: Yes
  Willing to relocate: No
  Technologies: Go (concurrent programming and network engineering) | Docker (Dockerfiles creation, Hub publishing) | Git | Test-driven development and generative-based testing | NSQd - deployment in HA mode | 12 factors | Shell scripting with Bash | Big data processing – Go (MapReduce) | Lock services (etcd, Consul, DynamoDB) | Implementation of systems using Raft (etcd raft) | Domain-driven design | BASE architecture | CAP theorem | Memcached | Object-oriented programming | Linux (Ubuntu) | MySQL | PostgreSQL | VPN (Wireguard) | AWS (EC2, ELB, EIP, Route 53, RDS) | Scrum | 5S | Lean startup | XP | Proven record of project leadership | QFD
  Résumé/CV: https://cirello.org/cv.html
  Email: hire@cirello.eu

Off-topic re: OP blog's and domain name.

These are nice and subtle nods to the tetralogy of the Book of New Sun. House Absolute is the palace of the Autarch, the ruler of the Commonwealth, a southern hemisphere nation in a far future when the Sun is dimmed.

(If my memory serves me well...)