Code as an Artifact

(pradeeproark.com)

19 points | by pradeeproark 2 hours ago

3 comments

  • paretolaw 2 hours ago
    My 2 cents

    Dont listen salesman talking about engineering. Unless he has credibility proven by things he had done recently. Person might be zillionare but he cant buy credibility.

    • sublinear 2 hours ago
      What's stopping the salesman from lying about that too?

      The experts aren't the ones buying. The expert and salesman are getting paid by the same person.

    • cindyllm 2 hours ago
      [dead]
  • jeremyjh 32 minutes ago
    Compilers produce the same binary each time they are run on the same code in a given environment. Writing anything in response to anything tweeted by Elon is as useless as Elon Musk himself.
  • TZubiri 2 hours ago
    Yes, in agentic coding, "code" is an artifact, in the sense of "release artifacts" the word used by VCS systems like GitHub. And the agentic step is not (or less) deterministic, so the burden on VCS is augmented by the need to track target code instead of being able to generate target code on demand through idempotency. Which explains why we are seeing the main VCS under infrastructural trouble.

    Some recommendations to strengthen your theoretical framework and language.

    Code is a quite ambiguous word, try using source code and target code. You can check out different definitions of source code, but a standard definition of these terms to me is Stallman's GPL, which is not just an academic textbook, it's actual binding contractual text for a huge body of software.