On cities

 First, we came together and again with increasing numbers until we were a city. What makes the city is a time and place.  A city is not just a place because in time a city processes the past places into the ruins, good and bad that make it a city. 

From the quarry of one ruin we can mine for blocks to build another future. From the quarry of another ruin we can see the outline of time cut deep into the cellar door.

From the quarry of my present city I ponder prodding processes, as my roof gently weeps. 

On maps

 First, maps can differ in the correspondence they have to a territory. Put another way, some maps are better than other maps. The correspondence a map has is a function of a reader's ability  to receive its  representation of the territory. (Note to self: Let's make a point of increasing out ability to receive representational forms, even the ones that we don't feel very comfortable with.)

Some maps are better for me, and others are better for you. We in our different lives living according to different maps sorting the information received. We rub alone one another in civil ways we appreciate inside and outside our communities.

Some maps are not good for anything more than a message to us that these thoughts were so wrong they ended in ruinous whorls of pain, sorted into concerns and worries after the fact.  Seeing those ruins can take a generation or more to settle out into the maps we keep in our hearts and minds to save us the pain we know they can cause any of us.

Some maps are better, still. The representation of memory accesses in C is not one of them, at least from what I've read. To be frank, C as a language I have a lot of unexplored-ness about. Well, the compiler too.  Just what does the compiler know, apparently more than it should some times as it aggressively does predictive branching, sigh.

Some maps are better, as one can see comparing the efficiency of operations between Roman numerals and Arabic numerals. In the land of ciphering, the Adding to Subtracting: The operations with Arabic numerals are mapped more efficiently from first operands to the last.  It is not the case that one works and the other does not, only one is far more efficient than the other in processing  quantitative narratives. And so the correspondence may initially be the same and result in the same end, but the journey via one representational system compared to another is different.

Pilgrim’s Progress

 First, please know mistakes were made.  Of course that is the origin of many a story, especially those meant to impart knowledge. The thing is that we didn’t know they were ruinous until much later.  And this is a common cause too in many a tale to the traveler. A pilgrim estimate’s of what a trip will involve and the real cost can be much different. 

First, the process is meant to impart some experience for the pilgrim to receive.  And the path is composed of more than just the pilgrim and the land. There are territories and maps, and never is a map the same as territory and yet the path exists still for the pilgrim’s progress.  To understand the mistakes made remember this traveler.

On first

 First is a state of mind that proposes a relation between elements in a universe of elements where some element or set of elements precedes others.

Being first does not necessarily mean it is “better” than non-first elements 

There are states of mind where an understanding of the  the universe is systematically linear. However, imparting understand to others can be better done is a different order.

 First, as to learning, the student that suffers the mistakes they made is best.

Rust

 First, a hug u ginormously (HUG) to the Rust documentation that mentions the compiler as your guide not your adversary to writing safe and smart code.

From https://doc.rust-lang.org/book/ch03-01-variables-and-mutability.html#variables-and-mutability

This example shows how the compiler helps you find errors in your programs. Even though compiler errors can be frustrating, they only mean your program isn’t safely doing what you want it to do yet; they do not mean that you’re not a good programmer! Experienced Rustaceans still get compiler errors.

First, I made a list, then I did something not on the list.

First, I made a list, then I did something not on the list. Typical me.

The next day, I did some exploratory research for some item on the list. I did some measurements, some looking over the situation, some what do I need to think about in regard to this task.  Thinking is such a big part of what novices have to do, and experts appear not to do. Experts just know. But they had to think about it at some point. At least I hope they did!

Next, I realized I may need a template for dealing with the items on the list. Each item on the list has its own unique requirements, but many items on the list share some commonalities.

For example, items have requirements like brushes to clean the item that needs some attention. Let's call these physical requirements of the task item. These physical requirements can have store purchasing requirements.  I can be more effective if I make one trip to the store to get required physical items. Or if I'm doing one task, like organizing an area, I can use the requirements list to pull items needed for tasks.

If a task is of a repeating type, that also has the side-benefit of assisting in creating a better organization structure. Consider your kitchen, and how you have it organized. You have a place for commonly used items, such as everyday plates and a place for less commonly used items, such as turkey fryer. And I thought, I should make sure I organize for the items on my list in the same way.

Then i thought about other meta aspects of items on the list. I call them  meta just because I can't think of a better name. Meta aspects are exploratory, doing, checking, continuing, and task time planning [expected time to complete the task, time tracking, best time to do task, worst time to do task]. Of course a lot of these meta aspects are interrelated at some level that can make me dizzy.  This is especially the case for initial attempts at completing an item on the list.  But I just think of that as learning to learning, which is so much fun.

So, yes I may be over thinking this list and related meta aspects. On the other hand, I rather not underthink something. And so I make a list of items. And that has a meta aspects, again, one of which is time planning aspects. Time is limited and decisions have to be made about what is done on the list. And so maybe I should stop writing about this and get some data from exploring, doing, checking, continuing and tracking time on this. Now, what order do I want to do these in...