Re:You've only added two lines – why did that take two days?
by Izkata on Tuesday July 14, 2020 @11:41PM
(#23841044)
Our non-technical stakeholders are almost guaranteed to have some minor design thing they jump on, so our equivalent was to show them only things that were functionally done, no matter how un-polished. That way they were the ones blocking any release.
[ Parent
| on HN ]
Re:You've only added two lines – why did that take two days?
by bmiller2 on Wednesday July 15, 2020 @12:11AM
(#23841240)
Always include a duck https://softwareengineering.stackexchange.com/questions/1220...
Re:You've only added two lines – why did that take two days?
by benhurmarcel on Wednesday July 15, 2020 @03:45AM
(#23842387)
Never heard that name, nice to know.
We sometimes have to do that in technical reports. The proofreaders always feel like they have to give at least one comment, so you give them a clear mistake to point out to avoid useless debate over minor points.
Re:You've only added two lines – why did that take two days?
by MBCook on Wednesday July 15, 2020 @12:00PM
(#23847128)
If you can do it that sounds like a very good strategy. We needed to be able to show mock ups of what things WOULD look like before we even start at the project so that everyone was on the same page. So we couldn’t develop functional prototypes or full working implementations to show.