I honestly like the simplicity of HCL. When a module gets painful, I know I'm doing something weird. It's all fancy JSON at the end of the day. Many teams look at modules like they are some amazing artifact to be preserved, I see them more as light abstractions hiding the operational bits from devs.

Didn’t notice carbon shit the bed on those images.

2. It's also a tracks preloads ...

We have an opts field on all get/list domain functions that let you request add'l info similar to JSONAPI, but at the elixir func level.

1. Inside the deploy/1 function, if the relations aren't loaded, it will load them and emit a telemetry event so you can find call sites missing data.

We collapsed about 6-7 services back into our monolith, cut out about 26 AWS services, refactored our storage engine on OCI, and of course we name our first test "poop" because we don't expect it to work and ... it did!

I’ve had pretty good success so far writing my tests and then using my tests as my prompts, but this was my first time just straight up vibe coding / talking to cursor - literally not touching the keyboard at all, and wow, holy fuck it’s a mess

Yes lol

Yep a WIP. Trying my hand at vibe coding but the code is a bloodbath so I’ll probably actually write code like a 2024 troglodyte.