Rather than having agents decide to manage their own code lifecycle, define a state machine where code moves from agent to agent and isolated agents critique each others code until the code produced is excellent quality.

This is still a bit of an token hungry solution, but it seems to be working reasonably well so far and I'm actively refining it as I build.

Not going to give you formal verification, but might be worth looking into strategies like this.

Comments URL: https://news.ycombinator.com/item?id=47408238

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=45051080

Points: 1

# Comments: 0

I've been building yet another tool to let people build on Kubernetes and escape the pain of YAML. I've open sourced it under the Apache-2.0 license and would love some feedback.

The tool was inspired by KRO (https://kro.run) (a project recently released by Amazon) and builds on top of it. TypeKro is aimed at providing a declarative type-safe user experience to orchestrating complex kubernetes dependencies with TypeScript, so you get your intelli-sense and all the other benefits of a modern programming language.

It is differentiated in a few ways:

1. TypeKro provides a seamless development experience where you can access status fields that will exist at runtime like as though they're already populated to make the development experience seamless. TypeKro or KRO will be able to handle orchestration seamlessly in the javascript runtime or in the operator in the kubernetes cluster respectively.

As a illustrative example: ```typescript const database = StatefulSet({ ... }); const webapp = Deployment({ name: 'my-app', image: 'my-app:latest', env: { // This looks like a normal property access, but it's // a type-safe reference that resolves after deployment! DATABASE_HOST: database.status.host, }, }); ```

2. TypeKro has 3 deployment modes to give you flexibility including rendering gitops ready yaml, deploying directly to your kubernetes cluster with a topological sorted DAG, and deploying your infrastructure as a KRO resource graph definition.

These three deployment approaches let you develop with a short-feedback loop and give you flexibility in deployment.

3. TypeKro is Kubernetes control-plane aware and will even stream relevant kubernetes events to your terminal while you're deploying resources.

4. TypeKro is smart enough to delay Custom Resource deployments until their CRDs are ready since the Kubernetes API won't accept CRs until their CRDs are ready.

5. TypeKro tries to expose everything with a very simple API integrated with arktype so you can build and consume kubernetesComposition() using tools familiar to typescript developers, and it has built in ability to integrate with your existing tool stack. You can use it to deploy your helm charts or your yaml manifests along with your new resources.

If you're interested, a good place to start is the docs site: https://typekro.run/

You can access the source code here (all stars appreciated): https://github.com/yehudacohen/typekro

And if you want my very long winded thoughts about TypeKro's software architecture and its place in the ecosystem, you can read my very long blog post here. Fair warning it's long: https://yehudacohen.substack.com/p/introducing-typekro

And I created a discord which currently has 0 users. So if you'd like to be first, pop on in!

It's still early days, so while I hope this provides a good experience I'm sure there are still bugs that aren't captured by my test suite. I've also only tested it against my local kind cluster so far.

I'd love to improve this and make it the easiest way to deploy to kubernetes. There are many things I'd love to do with TypeKro, including integrating resources from Crossplane and cloud controllers and other 3rd party resources with their intricate composition dependencies. I'd also love to try it out with and extend it to support multi-cluster deployments where resources span infrastructure boundaries.

All contributions are most welcome!

Comments URL: https://news.ycombinator.com/item?id=45046739

Points: 1

# Comments: 0

This blog post does approximate my sentiments pretty well, although its writing style diverges from my usual style.

I too found the write-up to be a little dry and long-winded, even though the same critique might be leveled at myself [hopefully to a lesser extent]. I did feel like it was a good step up from the usual AI slop out there, and served to illustrate Kiro's capabilities.

I suppose in this context, I wanted to see whether I could take my reader on a journey long enough for them to be surprised by the AI reveal at the end. I'm not sure whether it achieved that but that was the artistic intent of this specific piece.

It is my new daily driver.

Comments URL: https://news.ycombinator.com/item?id=43400994

Points: 2

# Comments: 0

Here's a write up of me fine-tuning ModernBert for regression to try beat the market.

I hope you all enjoy!

Comments URL: https://news.ycombinator.com/item?id=42556180

Points: 3

# Comments: 1

https://stackoverflow.com/questions/5508110/why-is-this-prog...

Comments URL: https://news.ycombinator.com/item?id=40011490

Points: 40

# Comments: 37

Comments URL: https://news.ycombinator.com/item?id=35509229

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=35462071

Points: 3

# Comments: 0

This is a very in-depth treatment of the evolution of cloud development tooling from my perspective. I've been working in this space since ~2016ish

Would love to hear your thoughts!

Comments URL: https://news.ycombinator.com/item?id=35233324

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=35114880

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=34493310

Points: 2

# Comments: 0