3 ms·

If the hypothetical API is taking 2 months to implement best case scenario I assume it's doing multiple things and each of those things can be done and tested p

• Traster 6y ago
  I really think you're missing the forest for the trees. His point was simply a big task can be broken down into smaller tasks that don't necessarily magically fit into 2 week chunks, and if you pick tasks that you know you can do within 2 weeks, often you're picking between 1-2weeks worth of work, and then the work stretches to fill the time. It's not about how many actual endpoints there are or how you actually choose to split the tasks.
• choeger 6y ago
  Or maybe, the model is actually just rather complex and a good API cannot be just a bunch of random methods on some losely related entities. Or maybe the non-functional aspects of the implementation need to be carefully considered before releasing an API that makes safety, correctness, security, or performance impossible. Or maybe the developers have an inconsistent specification and delivering piece A now makes it logically impossible to ever deliver piece B, which is arguably more important, but got lower priority because noone took the time to understand the whole thing.