Post History
I'm a self-taught programmer which means I started writing software by sitting down at an IDE and hammering out some code. When my decisions ultimately coded me into a corner I would refactor and r...
#3: Attribution notice added
by
System
·
2019-12-08T11:00:02Z (about 5 years ago)
Source: https://writers.stackexchange.com/q/42548 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
AGirlHasNoName
·
2019-12-08T11:00:02Z (about 5 years ago)
I'm a self-taught programmer which means I started writing software by sitting down at an IDE and hammering out some code. When my decisions ultimately coded me into a corner I would refactor and rewrite. This was a great learning experience for me but I want better for myself now. I am starting to see the benefit of creating design documents. So far this has been rough sketches of what I want GUI elements to look like and a few flow charts. A few other things I've been doing: - Top-down and Bottom-up design - Design Patterns - Requirements - Trying to understand the needs of my apps - Designing classes before implementing them But what I am having trouble with is putting it all together. Is there a process or method that works well? Is there an approach to writing the document that I can follow? Perhaps a few steps. Are there questions that I can ask myself? The answers to which will be useful in the creation of an outline for my projects and applications.
#1: Imported from external source
by
System
·
2019-02-24T04:44:14Z (almost 6 years ago)
Original score: 7