Defining types is part of software design. The design is the second step I do. The first step is the requirements. I write it in the form of a users manual. What does the user see and do? What are the inputs and outputs?
Once I write the requirements, I know that the software will be about 4 times the size. Skipping the requirements step is the biggest mistake my students make. It inevitably leads to failure. On Mon, Nov 4, 2019, 9:07 PM <[email protected]> wrote: > the first thing i do when i start a project is define my types, good way > to start. But I dont like nesting too much, I like doing it all with as > least type nesting as possible these days, saves alot of typing. > *Artificial General Intelligence List <https://agi.topicbox.com/latest>* > / AGI / see discussions <https://agi.topicbox.com/groups/agi> + > participants <https://agi.topicbox.com/groups/agi/members> + delivery > options <https://agi.topicbox.com/groups/agi/subscription> Permalink > <https://agi.topicbox.com/groups/agi/T252d8aea50d6d8f9-M26f367ea3e8e403c233a70f3> > ------------------------------------------ Artificial General Intelligence List: AGI Permalink: https://agi.topicbox.com/groups/agi/T252d8aea50d6d8f9-M6d7338e94c4acf02e25fa4dd Delivery options: https://agi.topicbox.com/groups/agi/subscription
