upvote

points

by giovannibonetti8 hours ago |
comments
upvoteby verdverm8 hours ago|
[-]
> Do you want a build system like Bazel for your monorepo?

I did something like this before Ai, with CUE + Dagger wrapped in a small Go binary. One problem I have seen with Ai generated projects is that they hit a limit due to conditional complexity. They have a strong tendency to add more code (local optimizations, deep if-else nesting) for edge cases, rather than stepping back to think about how to simplify problem and code.

reply
upvoteby mxey36 minutes ago|
parent|
next
[-]
You can cut out the middle man and use https://github.com/marxarelli/masse, a CUE frontend for BuildKit.

However I don’t think anything using BuildKit is as fine grained as Bazel.

reply
upvoteby giovannibonetti8 hours ago|
parent|
prev|
[-]
Funny thing, here in my company we're doing something similar, with CUE in a small Go library. You might be interested in it [1]. It generates a lot of boilerplate infrastructure code from the reference Cue files.

[1] https://github.com/bonisoft3/bayt

reply
upvoteby verdverm7 hours ago|
parent|
[-]
Being one of CUE's biggest fans, I will definitely be interested!

I have another thing in hof that is closer to this, also CUE + Dagger

https://github.com/hofstadter-io/hof/tree/_next/examples/env

https://github.com/hofstadter-io/hof/tree/_next/lib/env

I'm gearing up for a major rewrite into a new project, based on a bunch of learning and a desire to remove a ton of cruft that accumulated over 10+ years. I still debate if I want to wrap existing tools (tf, helm, etc...) or go for a full sail replacement. Dagger handles a lot of the tooling earlier in the CI process, mainly thinking CD here. Argo-* is our bain lately...

You might find the code gen aspects of hof interesting, I opted for Go's text/template, which you can also use from CUE if you wanted to have more literate (imo) code gen in your project.

reply