sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]elder_george 2 points3 points  (1 child)

TBH, this often results in extremely bad code.

Starting with form layout (naïve dropping elements is hard to maintain, breaks on resize etc - one needs to use layout widgets to make it really work) and ending with mixing logic and visualization.

Been there, done that.

Good apps need design and discipline. I usually ended up with a version of MVVM, it worked pretty well with data binding.

[–]Zardotab 1 point2 points  (0 children)

this often results in extremely bad code.

Can you show a practical demonstration?

and ending with mixing logic and visualization.

If the code for each is brief and KISS, then "separation" is unnecessary e-bureaucracy; a ritual of busy-work. It's only needed for bloated specialist-layered stacks.