Originally Posted by
Eris
I'm not speaking of storage limitations, but development time and money. It's easily 1 month of content or QA we're missing out on.
Not to come up with perhaps, but to implement and test all achievements, certainly at least a man-month.
Source: Me (I'm work as a software developer). Time estimation for any programming task works like this: Pick the time you think it takes. In this case, about a week seems reasonable. Multiply by 3[1]. Now you've arrived at the time doing the work will actually take. The formula has a very good track record.
... so about a month.
[1] 2 for problems you'll encounter + 1 for meetings and crap you gotta be at. If you're hobby coding, you're good with 2.
Bookmarks