Skip to content

Instantly share code, notes, and snippets.

@bdfinst
Created January 29, 2024 18:30
Show Gist options
  • Select an option

  • Save bdfinst/9cda7d82a756a97a97720810df3c7acd to your computer and use it in GitHub Desktop.

Select an option

Save bdfinst/9cda7d82a756a97a97720810df3c7acd to your computer and use it in GitHub Desktop.
# Perform a similarity search between the embedding of the query and the embeddings of the documents
query = "How big should a story be?"
results = vector_search.similarity_search(query)

print(results[0].page_content)

Stories should be sliced vertically. That is, the story should be aligned such that it fulfills a consumer request without requiring another story being deployed. After slicing, they should still meet the INVEST principle.
Example stories:

As an hourly associate I want to be able to log my arrival time so that I can be
paid correctly.
As a consumer of item data, I want to retrieve item information by color so that
I can find all red items.

Stories should not be sliced along tech stack layer or by activity. If you need to deploy a UI story and a service story to implement a new behavior, you have sliced horizontally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment