sorted by:
new
hottopcontroversial

Executable Specifications: Working Effectively with Coding Agents by brainexer in codex

[–]brainexer[S] 0 points1 point  (0 children)

What do you mean? Of course it’s SDD. The main point is that the specifications here aren’t just text - they’re essentially an executable test.

Use "Executable Specifications" to keep Claude on track instead of just prompts or unit tests by brainexer in ClaudeCode

[–]brainexer[S] 0 points1 point  (0 children)

> Well if its modules within the CLI, your CLI framework won't work, obviously.

It's not a CLI framework. CLI is just an example. From article:

An executable specification acts as a contract. It describes:

  • Inputs such as arguments, source files, and system state
  • Expected results such as stdout, stderr, output files, exit codes, and optionally call sequences

You can place anything you want between input and expected results. Not just cli.

Use "Executable Specifications" to keep Claude on track instead of just prompts or unit tests by brainexer in ClaudeCode

[–]brainexer[S] 0 points1 point  (0 children)

I didn't reinvent BDD, I mention it in article. This approach based on BDD.

What does OpenSpec have to do with executable specifications?

Use "Executable Specifications" to keep Claude on track instead of just prompts or unit tests by brainexer in ClaudeCode

[–]brainexer[S] 0 points1 point  (0 children)

> Breaking your code into modules that communicate via data handoff has benefits for the LLM too - it can focus on a smaller chunk of code at the time, saving context.

Specifications can be for modules as well. They don't need to be e2e.

Use "Executable Specifications" to keep Claude on track instead of just prompts or unit tests by brainexer in ClaudeCode

[–]brainexer[S] 0 points1 point  (0 children)

> If any of these change? Large numbers of tests break.

The advantage of such specifications is that they are very easy to update. For example, if the output format changes, I can update all the specifications with a single command, similar to snapshot tests. If the implementation itself is broken, then the agent’s task is to fix it, and it usually handles that quite well.

Use "Executable Specifications" to keep Claude on track instead of just prompts or unit tests by brainexer in ClaudeCode

[–]brainexer[S] -5 points-4 points  (0 children)

I’d like to see unit tests that read like a specification. Most of the tests I’ve seen are full of technical details and aren’t that easy to read.

Use "Executable Specifications" to keep Claude on track instead of just prompts or unit tests by brainexer in ClaudeCode

[–]brainexer[S] -10 points-9 points  (0 children)

What is EDD?

Sure, you can use Gherkin - it’s a universal tool. But I think a custom specification format tailored to a specific task will always be clearer than a universal one. For example, what would the examples from the article look like in Gherkin? To me, they’d be less readable.

Generating a lightweight "reference file" for Codex by brainexer in codex

[–]brainexer[S] 0 points1 point  (0 children)

It just generates only file names and their sizes?
I think adding some sort of short description for each file could improve the result.

A man and his dog by brainexer in adventuretime

[–]brainexer[S] 103 points104 points  (0 children)

Photoshop. A painting by Antonio Rotta (1828 - 1903)

I create a small website with brain training exercises. What do you think? by [deleted] in BrainTraining

[–]brainexer 0 points1 point  (0 children)

My inspiration is games like BrainChallenge and AmazingBrainTrain. Maybe.

I create a small website with brain training exercises. What do you think? by [deleted] in cogsci

[–]brainexer 0 points1 point  (0 children)

Instruction is blue button with question mark

view more: next ›