I'll be the first to admit that the code for /reader (and most of (b)log-In) is actually quite a mess
Some people 'talk to think' – they open their mouths and form their opinions as they talk through things, finally arriving at an answer.
That's what I'm like coding something. I won't have a plan as such, just a starting point and a rough direction. As I start to code the ideas about what to do next begin to manifest based on what I'm doing. I go from A to B to C without knowing that C was ever an option, it just becomes one as things develop.
Each feature and function leads the way to the next, and the next – because of this, that can/should/must happen. And because of this the code, is a mess as each piece is added, tacked on with the digital equivalent of sticky tape and bubblegum.
Some people 'talk to think' – they open their mouths and form their opinions as they talk through things, finally arriving at an answer.
That's what I'm like coding something. I won't have a plan as such, just a starting point and a rough direction. As I start to code the ideas about what to do next begin to manifest based on what I'm doing. I go from A to B to C without knowing that C was ever an option, it just becomes one as things develop.
That's how I develop as well. 😄 First I have a rough idea of how to implement something and while I'm programming or afterwards, I think of a better way and rewrite quite a bit. The plan I had in the beginning is rarely what it looks like in the end. And sometimes something doesn't work, so you try all kinds of things until it does work.
Leave a reply
2022/04/10#p4
"The fluidity of the mind is of the same family as the fluidity of being. Sometimes they coincide sharply. We call that a revelation." – Etel Adnan.
