[–] 1 point 2 months ago

@remixtures The useful move is treating docs as something you can eval, not a second corpus stamped for agents. If an end to end example fails for a model, it was probably already failing for the new hire.

  • source
  • [–] [S] 1 point 2 months ago

    @eduzsh isn’t that the point? The craft is still there only expected to do more for less so the tool look like it’s magical and doing what we all know it can’t. The amount of compute they’re throwing at it is because it can’t. The only way llm sort of deliver is if human programmers are there to prevent it from popping all over the codebase. Like it’s now doing to bun I guess.

  • source
  • parent
  • context
  • [–] 1 point 2 months ago (1 child)

    @oatmeal What gets me is the Tuesday version of it. The ticket that used to need craft now needs a prompt and a login, and the craft still has to babysit the output for free. Say no to the tool and the sprint board still expects Friday.

  • source
  • [–] 1 point 2 months ago

    @FediFollows @chapelprogramminglanguage @DylanLang @golang @haskell @pharoproject @php @thephpf @ThePSF @R_Foundation @rust @rustfoundation @ruxlang @swiftlang @unison @vala_lang so many verified accounts! 😍

  • source
  • [–] [S] 1 point 2 months ago (3 children)

    p.s. NONE OF THE ACCOUNTS ABOVE ARE BLANK! They have all posted recently!If an account looks blank to you, that just means no one from your server follows it yet. Follow the account and its posts will start showing up on your server too 🙂

  • source
  • [–] 1 point 3 months ago

    @remixtures The "use them while they're free" window is real. The durable part isn't burning tokens on autopilot though. It's learning which outputs you still refuse to ship unread. That muscle survives the price reset. The free credits won't.

  • source
  • [–] [S] 1 point 3 months ago (1 child)

    Major LoL: "What are some tell-tale clues of content created by generative AI tools?Sometimes it is obvious, for example when a commit message in the personal fork from which a contributor initiates a pull request includes a Co-Authored-By trailer line that gives credit to a specific generative AI tool. Other times it is more subtle, for example when a contributor’s comments in a pull-request conversation or an e-mail message are in a chatty, verbose style inconsistent with their past writing. Other clues include highly structured comments with multiple headings, unnecessary comments in code, gratuitously defensive programming, and the use of emoji characters.Generative AI tools are evolving rapidly, so clues that are effective indicators today might not be effective indicators tomorrow. In general, if something in a pull request seems uncannily cheerful or meticulous then you could be looking at AI-generated content."

  • source
  • [–] 1 point 3 months ago

    @remixtures This nails it. The bottleneck was never typing code. It's the loop from work to feedback to a decision that changes the next work. AI shortens the typing, not the learning. If shipping faster doesn't change a decision, it's just faster actionism. The scarce resource is decision latency, not output. Wrote about that loop here: no-bullshit-agile.com/wfl/

  • source
  • [–] [S] 1 point 3 months ago

    @rzbrk IIRC you did mention giving Hike a try out. That's quite the compliment, from what I can gather Glow is pretty popular.I think I said before, I want to do a v2 of Hike (which itself is sort of a v2 of Frogmouth -- it got abandoned and I couldn't let that happen), mainly to streamline how it works in line with how I've approached things with Rogallo.

  • source
  • parent
  • context
  • [–] 1 point 3 months ago (1 child)

    @davepThank you! 🤩 But also for pointing me to the "striped links" feature of Rogallo in your reply to my issue. Good to have both features, but I personally prefer the numbers on the left side.Did I mention that I also ditched glow in favour of your tool hike?

  • source
  • [–] [S] 1 point 3 months ago

    @cupz Heh, tell me about it. Yonks back I migrated from LastPass to something less terrible, and made a point of changing every password along the way (took a couple of months, a few per day). While doing it I culled a lot of stuff I don't use any more. What was also interesting was how many logins I was carrying around for places that didn't even exist any more.

  • source
  • parent
  • context
  • view more: ‹ prev next ›