Bamboo is a grass, it doesn't layer bark. It's one and done. The internode distance is pretty much fixed once it hardens. The bamboo cells inflate and harden. So the graphs make a reasonable amount of sense.
The wall thickness is a function of time to harden, and time to add extra stuff to the wall. Segments close to the ground have simply longer time, and likely hardening begets hardening.
The internode distance is interesting in that there is a natural point at which the bamboo stops elongating and begins to start shortening (again in a negative exponential). My understanding is that bamboo does start to keep "leaves" that sprout from the nodes, to gather light and energy. I wonder if that is the point that the leaves start, and hence it is a mixture of both time (less time = shorter) and investment in energy (effort to grow sun-catching leaves).
Some interesting followups would be in the natural habitat, where does the typical canopy start?
> in the natural habitat, where does the typical canopy start
Doesn’t have to be driven by “natural habitat”, just the current environment. You are right though, the stalk wants to grow tall quickly (but not any taller than necessary, hence the successively increasing node distance in its “search”) until there is sufficient light, then it begins to disfavor further height growth in favor of increased density of leaves (nodes, where the leaves come from)
That happened to me. AMD stock certificate from 2006 received at about $10. They accepted it, were willing to transfer it into my account. Unfortunately, I had moved country and the annual meeting messages were returned to Computershare as RTS. They declared me (and my stock certificates lost) and hence eschewed them to the state of Delaware. Where they were dutifully sold and state lost property had the results of the sale. The eschewment happened in 2015 when the stock was about $5.
When I realized I had them, and tried to deposit them in etrade, it all went well, except the certificates were returned "no longer valid eschewed to the state of delaware".
The bummer is that the stock was running at about $80 then, and is running at around $150 now.
sigh.
So they will be valid, but there will paths that will "expire them".
To me, it isn't about the code itself, it's about communication, it's about a relationship with others through code, systems and architecture.
Using the relationship analogy, when you can hear something small from your partner and know what they are thinking, understand what they may do next it feels effortless.
When you look at some code, can you trust what the function name implies is done, without concern?
When something is complex in a relationship we pause to take time to communicate and come to a common understanding, we write notes to each other.
When we have something complex in code do we write down information to help the other engineers work through it?
In a lot of ways the way we relate to our peers through code is possibly a reflection of how we relate to others in life.
It doesn't diminish, the knowledge is like a fractal. You can zoom out, in, etc.
I created a prompt that asks me a set of questions on a topic. It then scores my understanding, gives me deeper insight into the topics, broadens my understanding with some extra information, and then provides a mind-map of related topics, and a mind-map of adjacent topics.
To bootstrap an area of understanding, I ask it for a mind-map of a topic. Like a fractal, you can choose a line item and go deeper.
Prompt 1: Give me a small mind map on the amygdala
Based on that, prompt 2: give me a mind map on the role of the basolateral nuclei of the amygdala in the creation of phobias
My background theory is around schematization. Our knowledge is a complex web of inter-related concepts. Some factual, some abstract.
For audiobooks/read books, I look for 2 or 3 key "aha moments" that stick with me. For Thinking Fast it was "two ways of thinking", "loss aversion". From there other related concepts are just below the surface.
For Thinking in Systems it's "stocks + outflows + inflow", and "all systems reach an equilibrium".
As you read more, you get lots of different ideas cross pollinate, and from there you gain your own insights.
As others have said, pondering or applying the ideas in real life is really important.
Your brain takes shortcuts, you can think you understand what is going on, it's only when you need to communicate it you realize how many shortcuts in hallucinations of understanding there are in your head.
So for those with imgur accounts... I have a challenge for you.
Most people will know how to ride a bike, will know a bike when they see it.
But can you communicate what a bike looks like (in a diagram)? 90% of you won't be able to.
Grab a piece of paper, and draw a bike. Post it to imgur, and post a link to it below (please don't be a troll).
I know folks that control for this by writing a fail fast implementation. I do it by talking it through. There’s a lot of modalities in the human experience and different people are adapted to different modalities. Building a strong complete team involves covering all the modalities and letting them work the way they work best, and as a team. A team that can write, speak, draw, produce functional demos, etc, is better than the one that can write.
Based on what I saw on that website, only a handful of people couldn't draw a bike well enough to get the point across. A few more than that posted designs which can't function (fixed front wheel), but are easily recognizable as a bike. Most are fine. Certainly not supporting that 90% of people won't be able to do so. A diagram isn't a spec. It's designed to convey higher level ideas of which most of these bike illustrations are fine for.
I’m not sure I understand your point with the bikes. Communication , in writing or speaking, is really just sharing ideas. I saw a lot of drawings of bikes in your link. Are you just saying that people lose the details which ultimately don’t matter? I don’t think of “chainstays” when picturing a bicycle.
they may not even be hallucinations, just short circuit paths that have embedded in your conceptualization of stuff that they've become unspoken deeply furrowed premises long trusted and never thought to be questioned. Surfacing unspoken and unwritten premises is something I find exciting, really invites getting at the root of stuff.
I feel I've got something similar. Memory encoding/recall via emotions I struggle with. I can understand emotions, but it seems to be more cognitive. So I struggle to share the same "emotional space".
Bamboo is a grass, it doesn't layer bark. It's one and done. The internode distance is pretty much fixed once it hardens. The bamboo cells inflate and harden. So the graphs make a reasonable amount of sense.
The wall thickness is a function of time to harden, and time to add extra stuff to the wall. Segments close to the ground have simply longer time, and likely hardening begets hardening.
The internode distance is interesting in that there is a natural point at which the bamboo stops elongating and begins to start shortening (again in a negative exponential). My understanding is that bamboo does start to keep "leaves" that sprout from the nodes, to gather light and energy. I wonder if that is the point that the leaves start, and hence it is a mixture of both time (less time = shorter) and investment in energy (effort to grow sun-catching leaves).
Some interesting followups would be in the natural habitat, where does the typical canopy start?