Egregoros

Signal feed

Timeline

Post

Remote status

Context

2

When I'm up to look for work again, I am just going to have to counter pitch every "AI accelerated agent flow" position with "show me your AI code and if I can tell you 2 things that are structurally preposterous about it that have made you sink more time than you thought you saved, then you hire me and I don't have to do that."

I have a range of expertise and diagnosing the many ways stirring a vat of hogwater can feel like jet fueled rocket skates is increasingly one of them.

@jonny customers don't care if the code is poorly structured. managers don't care if the code is poorly structured. The C-suite definitely doesn't care if the code is poorly structured.

All they care about is that it works.

but also I think you'll be shocked at how well structured and clean it is if the person driving it was half competent.

@feld
"How the code is written" is more than aesthetics, unfortunately, and even though it feels good to get high on massive token counts, needing to spend a week churning your agents on a problem that is a byproduct of previous bullshit decisions that in turn generates a dozen more bullshit decisions that need to be undone later is not more productive than "just doing it right"

Replies

5
@jonny if you already know what the output should be it should be super easy to review, right?

how hard is it to make the tools use the tools?

- make it pass your code formatter / style guidelines
- make it pass your linter
- make it pass your static analysis
- make it pass your test cases

it's not hard to make it do these things before you review the code, and then -- shockingly -- what you get is very high quality output that's probably better than what you'd get otherwise