Originally Posted by Bass Thumper
my early FORTRAN punch-cards college days by not spending adequate front-end time to design the overall layout of my programs. Later on in my career, I learned from those early mistakes. The pro-programmers I worked with had a term for such poor quality; they called it "spaghetti code". Once, again, I am not linking this to BiaB in any way, but rather speaking generically.
Fortran is a powerful language for many tasks, but it isn't the easiest language in which to write neatly structured code.

Keeping designs and code neat, elegant, consistent, readable and digestible takes a lot more planning than people often realise, but it usually pays back plenty. In a typical compiler white space and meaningful cost nothing in the final executable. Meaningful names cost when one first writes them but normally pay back when revisiting. Design the the user interface and data first.

I'll try to watch the video tomorrow.

Edit: For user interfaces I often used to make movie-type storyboards, sketched out by hand for people to consider, critique, draw and write over.

Last edited by Gordon Scott; 06/02/24 03:13 PM.
Jazz relative beginner, starting at a much older age than was helpful.
AVL:MXE Linux; Windows 11
BIAB2025 Audiophile, a bunch of other software.
Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts
.