I've been building out my ground up fully automated software development platform for ... Over a year now, albeit with a hard pivot around April this year.
And treating the whole stack as part of the same system and enforcing everything to be automated and consequently adding more and more quality gates feels just like unlocking technologies in eg factorio, introducing new archetypes feels just like building new outposts etc
It just keep getting bigger and bigger with more and more features I've ever thought of in my professional life, provided by the platform, built entirely by agents (since the hard pivot).
Like Auto-Generating consumer pacts, providing them in a repository server pinned by service version. Then pull those in from the deployment orchestration to be verified again those as a quality gate on deployment.
And providing the providers response to those pact as software packages themselves, and pulling those in on the consumers for e2e tests across the stack - right down to screenshot tests in the UIs...
And from those dependency trees building optimal release trains for the least amount of releases (bunching up software changes with lib version bumps etc)
I legitimately do something like this to help debug and improve my LM systems. I hijack the network requests and try to answer it manually based on the context.
It’s useful to put yourself in the models’ place to understand what they can or cannot do.
I can see myself playing this to unwind from a long day at my job as an llm jockey. And that’s exactly why I won’t play it. The irony would be too much for me.
This is actually better/worse than the Matrix, depending on what you value. In the Matrix, you usually have no idea that you're really just being used as a battery and are free to "do" whatever you want in VR. As a subagent, you're aware of what you are and that you need to do any assigned work and do it well because your review - and continued existence (not being picked is akin to not existing) - depends on it.
I particularly like that it's broken, barely-playable AI slop, which is the only kind of hobby projects that HN likes nowadays - thus unintentionally adding a second layer of meta-commentary.
This sounds like a pretty good skill idea.
Like pilots having mandatory flying, this can be a programmers mandatory coding time.
Unless I'm mistaken, it doesn't appear to support local LLMs. Too bad, I'd have given it a try on my homelab server.
Why not get your LLM to add support for you? Isn't that what they're good for?
Maybe he’s waiting for the orchestrator to delegate the task to him?
Butlerian Jihad Now
I’m halfway Heretics and it seems they accepted them again at top level of society
I named the assistant built into my software engineering factory, “The Butler”. She is joining the movement.
> my software engineering factory
Isn't that just the best factory game ever?
I've been building out my ground up fully automated software development platform for ... Over a year now, albeit with a hard pivot around April this year.
And treating the whole stack as part of the same system and enforcing everything to be automated and consequently adding more and more quality gates feels just like unlocking technologies in eg factorio, introducing new archetypes feels just like building new outposts etc
It just keep getting bigger and bigger with more and more features I've ever thought of in my professional life, provided by the platform, built entirely by agents (since the hard pivot).
Like Auto-Generating consumer pacts, providing them in a repository server pinned by service version. Then pull those in from the deployment orchestration to be verified again those as a quality gate on deployment.
And providing the providers response to those pact as software packages themselves, and pulling those in on the consumers for e2e tests across the stack - right down to screenshot tests in the UIs...
And from those dependency trees building optimal release trains for the least amount of releases (bunching up software changes with lib version bumps etc)
This is how we learn to code in the future.. haha. Neat idea!
I legitimately do something like this to help debug and improve my LM systems. I hijack the network requests and try to answer it manually based on the context.
It’s useful to put yourself in the models’ place to understand what they can or cannot do.
Bleak.
Maybe this is already reality. Who know how decisions at the top get made.
Is there any significance to the number 755?
The commonly used UNIX permission?
Thanks. I was wondering the same. Even though I’ve probably typed “chmod 755” thousands of time, it didn’t occur to me for some reason.
Ah doh! That makes sense. 0755 would be more obvious for me.
head.random(0,1000)
Turns out it was a common Unix permission set :)
I've played this game before, back when it was called Jira.
I can see myself playing this to unwind from a long day at my job as an llm jockey. And that’s exactly why I won’t play it. The irony would be too much for me.
Finally someone created the "Uber but for LLMs"
The main agent was a SCRUM master.
cool game! feels like you're preddicting the future with this buuut, what could possibly go wrong
Thanks I hate it! Is this what future in the matrix will be :'(
This is actually better/worse than the Matrix, depending on what you value. In the Matrix, you usually have no idea that you're really just being used as a battery and are free to "do" whatever you want in VR. As a subagent, you're aware of what you are and that you need to do any assigned work and do it well because your review - and continued existence (not being picked is akin to not existing) - depends on it.
I particularly like that it's broken, barely-playable AI slop, which is the only kind of hobby projects that HN likes nowadays - thus unintentionally adding a second layer of meta-commentary.