ucirello

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

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.

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.

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

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.

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.

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: [email protected]

----

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: [email protected]