The brain fails to understand design patterns for real-time application development

Question

I set myself the task of realizing a MIDI application. Like all other software that I have written to date, I started with coding. I used a tiny GUI application (GTK2) that can control the transport state of the Jack Audio Connection Kit and its clients.

I had never written a real-time application before and had never written one multi-threaded program. Together, both of these details make this a significant problem for me, since all the software that I have written to date does not require me to develop it in the first place. I only occasionally needed a pen and paper for work.

This project, however, will not allow me to continue coding. But I know almost nothing about software development, I teach myself (discounting a 2-year course in computer research in the mid-1990s). I always worked in stages, worked something, and then built on it.

During my research, I came across the Model View Controller, but it is very difficult for me not to think about the details, and I can not find the basis for leaning without finding the problems that bring all this.

I need advice to get past this block. I need to stop finding distractions that are losing my brain. This is one of the distractions. How to get past this block?

Answer 1

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

. , , : .

: , . , , , .

, ( ) , , , / . " "

, , , . "- ".

, , , , .

, / . , , , , .

. CRC-.

Answer 2

, , , : .

, , , , . , , .

" , ", - , , , .

, . / OS/ , , . , . (: - , ! , , !)

, :

while( program_running )
{
  // This period needs to be long enough for you to do your work
  //  but short enough that your user doesn't think your program
  //  is choppy. Anything better than 50 Hz is usually good enough
  //  for an application with a human interface.
  wait_for_short_period() 
  check_interfaces_for_new_data()
  update_model() // or state machine
  update_outbound_interface() // the speaker, monitor, whatever
}

( ), .

Answer 3

-, designpattern . .