Login
You're viewing the functional.cafe public feed.
  • Nov 16, 2026, 7:37 AM

    you know what AI agents can never do? think about what the right approach to a problem is for 3 days, coming up with and rejecting various solutions (all of which would have worked to some extent) before settling on the actual proper solution that is clean and adds barely any complexity

    💬 3🔄 7⭐ 0

Replies

  • Nov 16, 2026, 9:46 AM

    @eniko, my recent change at work was plus 5K lines and minus the exactly the same amount for a new feature. Mostly it's code generated by protoc for serialization purposes. No added complexity, just a new feature and some cleanup thanks for refactoring. And that's exactly how it should work, the code should be observable and reviewable, not a pile of crap thrown onto a fan.

    💬 0🔄 0⭐ 1
  • Nov 16, 2026, 1:53 PM

    @yoh : Adding and removing 5K lines for a new feature seems like a lot.

    I commend your removal of many unneeded lines, via refactoring. But the size makes me think that this work must have been put off for a long time, to have grown so large, before you addressed it. I'd want to emphasize "clean as you go" to spread out the refactoring over time.

    …

    💬 1🔄 0⭐ 0
  • Nov 16, 2026, 1:56 PM

    @yoh : …

    I do not think that protec code generation should count as "AI" (Generative AI; Large Language Models). We had code generation for decades before Generative AI was a thing. Let's not credit the latest fad with the accomplishments of all the earlier work.

    …

    💬 1🔄 0⭐ 0
  • Nov 16, 2026, 1:57 PM

    @yoh : …

    I would consider the ".proto" schema files to be the actual source code, and the generated (C#?) code to be a performance optimization side effect. Essentially "object code."

    You don't modify this generated code by hand, do you? I'd hope you'd change the ".proto" schema files and regenerate.

    💬 1🔄 0⭐ 0
  • Nov 16, 2026, 2:10 PM

    @JeffGrigg @eniko, exactly, I only change proto files and the code supporting it generates. And no, I don't count it as AI, it's just code generation. But other devs in the team are happy to beg the computer to make all the logic with numerous levels of abstractions no one actually needs and which is impossible to review at all.

    💬 0🔄 0⭐ 1
  • Nov 16, 2026, 2:16 PM

    @yoh : The Extreme Programming approach is to keep the code highly maintainable, by keeping it simple and having good regression tests (via Test-Driven Development (TDD)) instead of building in powerful abstractions today that will not really be needed until some future time. "You Are Not Going to Need It" (YAGNI) is has been our motto. IE: Don't build and pay for today, what you won't need until, maybe, in some uncertain future.

    Good work! What you're doing sounds good.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Nov 16, 2026, 2:43 PM

    @eniko web people i’ve worked with don’t do that and then they layer on unit or integration tests with mocked network / database requests that take longer to fix / maintain then their 30 loc that render some HTML.

    I honestly think the AI excitement is just people already being terrible at what they do and going “wow this codes like me but quicker”

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0