TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: How do you split time between design, coding and testing for a feature?

5 pointsby kkcorpsover 3 years ago
Suppose 10 days were allotted to add a feature on which solely you are working on. How many days will you allot to create class/architecture designs, coding and testing the feature. Feel free to elaborate the approach for each although not necessary.

1 comment

rossdavidhover 3 years ago
I would aim to get _some_ minimum testable version done in 2 days. It would likely be missing many essential features, but it would at least accept input, do something with it (perhaps just parsing it), and then return output. Then I begin testing. Thereafter, I am adding a piece to it at a time and testing.<p>Sometimes I do this with automated testing, but I&#x27;ll admit that sometimes I don&#x27;t. I never regret the time to set it up as automated testing early, though.<p>I try to finish by day 8, which means that I won&#x27;t actually finish then but in the last 2 days I&#x27;m taking care of the fiddly bits (more elegant error handling, logging if necessary, weird edge cases), basically things I didn&#x27;t even think of needing to do when I started. So, I plan to finish by day 8 so that I have some time left for things that were not initially in scope which (for whatever technical, business, or political reason) cannot be left out in version 1.