I work top down, all about clean, readable code.
Start with main skeleton; creating empty functions that return fixed answers; then filling them in, creating new functions where it makes readability better.
In final stages I start search/replace variable and function names to make it better readable.
If the code is really big (>10k lines) I start pushing blocks to include-files, but then I really miss the old QBX overview of all modules/include under F2
Performance/Efficiency is plenty for 99% of code. Only where it counts (animation, huge I/O), I refactor the code purely towards performance, but even then, only for the smallest parts where it matters.
Oh, and yes, I use Inkey$ a lot (old habits never die)
Start with main skeleton; creating empty functions that return fixed answers; then filling them in, creating new functions where it makes readability better.
In final stages I start search/replace variable and function names to make it better readable.
If the code is really big (>10k lines) I start pushing blocks to include-files, but then I really miss the old QBX overview of all modules/include under F2
Performance/Efficiency is plenty for 99% of code. Only where it counts (animation, huge I/O), I refactor the code purely towards performance, but even then, only for the smallest parts where it matters.
Oh, and yes, I use Inkey$ a lot (old habits never die)
45y and 2M lines of MBASIC>BASICA>QBASIC>QBX>QB64 experience