4 ms·

I work on projects where we measure the output. There's nothing "pseudo" about it.

• zbentley 6mo ago
  Tell me, what do you measure? Changes shipped? Lines of code? Customer satisfaction? Defect rate? MTTR? New engineer onboarding time/TTFC? Security/compliance audit turnaround time? Uptime? Employee retention? Rollback/forward-fix rates? Linter errors? Test coverage? Meaningful test coverage?
  • vidarh 6mo ago
    Depends on the clients maturity, but some places all of the above.
    • adyavanapalli 6mo ago
      What are the numbers you are getting?
      • vidarh 6mo ago
        Initial drop, as people learn to use the tools, and while they keep babysitting their harnesses. Then significant boost once people start getting used to running the agents in the background, especially once they start running multiple sessions in parallel. I'd say you need a ~6 month push of getting people trained if they are not used to this way of working, and to customised setups etc. for your organisation, and then you start seeing significant payoff.
        • ai_fry_ur_brain 6mo ago
          Was there previously huge backlog of work to do, or are you just building tons features for the hell of it because you can?
          • vidarh 6mo ago
            I've never once in 30+ years worked on a project where there weren't a lot of work we didn't get to because of lack of resources. So, yes, there's always been huge backlogs.