User Tools

Site Tools


sweater:implementation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
sweater:implementation [2019/03/05 03:02] – [Sweater Implementation] mithatsweater:implementation [2019/03/05 03:06] (current) – [Sweater Implementation] mithat
Line 1: Line 1:
 ====== Sweater Implementation ====== ====== Sweater Implementation ======
  
-A crucial question we need to decide is what technology the Sweater app will be built with. In general, this decision depends ideally on the design goals of the project and the business needs of the project. It may also depend on what the development team already knows and what kind of time budget there is for learning new technologies.+A crucial question we need to decide is what technology the Sweater app will be built with. In general, this decision is likely to have a dependencies on the design goals and the business needs of the project. It may also depend on what the development team already knows and what kind of time budget there is for learning new technologies.
  
-The potentially evolving design requirements for this project are discussed [[design|elsewhere]]. You can (and we will) always start dabbling with implementations before a solid understanding of the design requirements congeals, but if you do so you should be prepared to throw away everything and start again. In fact, so matter what you should always be prepared to throw away everything and start againWe are constantly spiraling toward wisdom.+The potentially evolving design requirements for this project are discussed [[design|elsewhere]]. You can (and we will) always start dabbling with implementations before a solid understanding of the design requirements congeals, but if you do so you should be prepared to throw away everything and start again. In fact, no matter whatyou should always be prepared to throw away everything and start againWe are constantly spiraling toward wisdom.
  
 Some of the business needs you might need to consider in a project include: Some of the business needs you might need to consider in a project include:
-  * How soon must the app ship? +  * How soon must it ship? 
-  * How important is it that features can be added?+  * How important is it that new features can be added?
   * How important is it that the UI/styling can be changed?   * How important is it that the UI/styling can be changed?
  
-For Sweater, I am going to say that the app needs to ship only as soon as it's ready, but preferable not before another major JavaScript release. I'm also going to say that the app will always be simplethat's its main draw, so adding a lot of new features will be unlikely. Finally, it would be cool if Sweater could wear different sweaters, so it would be good to design the apps structure to make applying different UI/styling not unreasonable. But this isn't a must-have.+For Sweater, I am going to say that the app needs to ship only as soon as it's ready, but preferably not before another major JavaScript release. I'm also going to say that the app will always be simple -- that's its main draw! So adding a lot of new features will be unlikely. Finally, it would be cool if Sweater could wear different sweaters, so it would be nice to design the app'structure to make applying different UI/styling not unreasonable. But this isn't a must-have.
 ===== Choosing technologies ===== ===== Choosing technologies =====
  
sweater/implementation.txt · Last modified: 2019/03/05 03:06 by mithat

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki