Slicing: No. Cut the project into appropriate-sized slices. Cut big slices into sub-slices. Hierarchy is your friend.
One thing at a time: Yes.
Make it run, make it right, make it fast: Yes.
Easy changes: No good changes are hard once you own the result. If a change feels hard it's probably not good yet.
Concentration: That's one of two approaches. IMO either rearrange the code so you only need to change in one place, or rearrange your change so that the code only has to change trivially in any place.
Isolation: Depends.
Baseline: Yes.
Call your shot: Yes, but only because it means "know what you think will happen" which means "understand the codebase". If you're working on someone else's codebase, discard this and replace it with "try things and learn from them."
Multiple scales: Yes.
Symmetry: You mean 'factoring'. But yes.
Aesthetics: We define beauty as solving problems efficiency. If it's ugly but it's the best answer, we'll learn to think it's beautiful.
Rhythm: Yep. A time for all things.
Tradeoffs: Yes. You can't make a call til you understand the context.
Fun list: I guess that works.
Feed ideas: Never be afraid to ask what-if.
80/15/5 rule: Situational. If current low risk work is gravy spend 100% on that. If not, dig into R&D.
Slicing: No. Cut the project into appropriate-sized slices. Cut big slices into sub-slices. Hierarchy is your friend.
One thing at a time: Yes.
Make it run, make it right, make it fast: Yes.
Easy changes: No good changes are hard once you own the result. If a change feels hard it's probably not good yet.
Concentration: That's one of two approaches. IMO either rearrange the code so you only need to change in one place, or rearrange your change so that the code only has to change trivially in any place.
Isolation: Depends.
Baseline: Yes.
Call your shot: Yes, but only because it means "know what you think will happen" which means "understand the codebase". If you're working on someone else's codebase, discard this and replace it with "try things and learn from them."
Multiple scales: Yes.
Symmetry: You mean 'factoring'. But yes.
Aesthetics: We define beauty as solving problems efficiency. If it's ugly but it's the best answer, we'll learn to think it's beautiful.
Rhythm: Yep. A time for all things.
Tradeoffs: Yes. You can't make a call til you understand the context.
Fun list: I guess that works.
Feed ideas: Never be afraid to ask what-if.
80/15/5 rule: Situational. If current low risk work is gravy spend 100% on that. If not, dig into R&D.