4 ms·
I was all-in with six. Three people to write the code. Two people to write the documentation and otherwise interface with the public. One person to answer all o
by stuckagain 10y ago
I was all-in with six. Three people to write the code. Two people to write the documentation and otherwise interface with the public. One person to answer all of the emails and attend all of the meetings and make sure nobody interrupts the other five people.
If you have headcount for "testing" then I don't want to use your software. Tests are integral to coding and should be written first.
- majewsky 10y agoGrandparent's not talking about unit tests. A good human tester can be very useful in finding the mysterious edge cases where the bugs roam, without wasting your developer's time doing the same.
- maxxxxx 10y agoThat would be a dream but I have never seen that I a large company. Every little thing gets huge overhead.
- pshposh 10y agoDo you have a publicly accessible project I could inspect how this all worked out for you?
- landryraccoon 10y agoDo you use Apple software? I understand they are pretty big on manual testing. Your process description doesn't sound anything like how I understand products are developed at Apple. Where's the headcount for the designers / UI specialists? Are you counting them as engineers?
- CamperBob2 10y agoIf you have headcount for "testing" then I don't want to use your software. Tests are integral to coding and should be written first. Yeah, if everything were synchronous, deterministic, linear, and non-interactive, life would be so much easier, and test-driven development might actually work.