DataTalksClub / DataTalksClub/faq

[FAQ] Help with agent speed of designing and coding

Open Beginner friendly
#394 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

faq-proposal
Dominant language
Python
Stars
7
Forks
19
Avg merge
3d 20h
Merged PRs (30d)
9

Description

Course

machine-learning-zoomcamp

Question

How to reduce time taken by the PM, Engineer, QA agent? Everything is so slow.

Answer
  • Make sure your tasks are not too numerous. Group them logically (or ask the AI to). 2 is too few. 99 is too many and might get stuck to infinity
  • While the Session 1 of the course focussed on a robust process, it might be overkill of simple projects. Prevent bloat and complexity by explicitly asking the AI to review against those criteria
  • Ask your AI to review the tasks and issues, it might spot some logical loops, or anomalies in the process. Correcting those before starting can save your hours.
  • Specifically ask the orchestrator to be a higher level LLM, while the doers are lower-tiers of LLM
  • Give the AI orchestrator agent some monitoring and time-control guidance
  • Ask the engineer (coding agent) to follow the lazy ponytail dev principles (https://github.com/DietrichGebert/ponytail)
  • Ask your AI to have a dry run and to monitor closely what the sub-agents are doing, it might surface further anomalies
  • Once all the above "pass" then you may run the whole process with more confidence.
Checklist
  • I have searched existing FAQs and this question is not already answered
  • The answer provides accurate, helpful information
  • I have included any relevant code examples or links

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #394 and compare its FAQ structure with the repository’s existing FAQ entries. Review the question, answer, external link, and checklist for consistency and accuracy. Done means the entry follows the project’s FAQ conventions and clearly addresses the reported agent-speed concern.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.