Is there a logical continuation of application development?

I am currently working on an application in WPF / C # for personal use. I am not a "classically trained" programmer. Just an amateur who loves to write in his spare time. Is there an acceptable approach to the development of application development? IE Make it work, add fault tolerance, create gui, then optimize performance. Or maybe I need to develop an entire graphical interface first? Basically, I am going to start a new project in the near future and would like to have some kind of “checklist” for each program.

+3
source share
7 answers

Actually there is no “every program that needs this” list, because absolutely nothing that every program requires.

Some tips, however: don't “make it work,” then “add fault tolerance.” Protective programming and error reporting should be an integral part of development. This is much simpler (and usually more efficient) if you consider errors and unexpected input when writing a piece of code, and not after it has been executed.

Regarding whether you need to make a GUI first, answer this question: is the most important aspect of the program what it does or what it looks like? This is a serious issue, which, frankly, can vary from application to application (although this is usually the first, more important).

, "-" ( , , , ), , .

, , - .

. ( Wikipedia), , " ".

+2

, , , , ( ), . ( !)

, , , , . , , , , , .. , , .

.

+1

, , .

, ( WPF, SketchFlow Blend ). , "" , , ..

, , - . . , "", " ", , "" , , , ...

+1

. , , ..

:

  • : , , , , , , , .

  • : , , , , , " ", " gui", " ", " CRUD"

  • : 2., , , 2. , , / - ( , , ).

, ( ) ( ).

0

. , , . , , , .

, , .

0

, , , , : , . , . TDD - , , . , .

0

( ):

  • (, ) - , , -, - , ( ).
  • () - , , , API - ( )
  • - API/ , , .
  • - , , . (, 1).
  • , .
0

Source: https://habr.com/ru/post/1742507/


All Articles