Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove tach #648

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Remove tach #648

merged 1 commit into from
Jan 16, 2025

Conversation

teocns
Copy link
Contributor

@teocns teocns commented Jan 16, 2025

For a small/medium codebase like AgentOps, tach is probably overkill:

  • codebase is relatively small and focused
  • The module dependencies are straightforward (event → session, etc.)
  • Small team size means architectural decisions can be enforced through code review
  • It wasn't providing any meaningful value the way it was configured
  • Slows down development unnecessarily

Cases where tach is actually helpful is far from our reality. Let me give some examples:

  • Large enterprise codebases with 100k+ lines of code
  • Microservices with strict boundaries that must be enforced
  • Teams of 10+ developers working across multiple modules

Signed-off-by: Teo <teocns@gmail.com>
@teocns teocns requested a review from areibman January 16, 2025 19:29
Copy link

codecov bot commented Jan 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

@teocns teocns merged commit 29027bd into main Jan 16, 2025
9 checks passed
@teocns teocns deleted the chore/remove-tach branch January 16, 2025 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants