- Thoughts
Standing on the shoulders of giants
Faced with a choice I don't understand, I ask about the scenery I missed. It is the act of learning not just the conclusion, but the experience and perspective that led to it.
I believe that standing on the shoulders of giants is not merely about seeing further by utilizing someone else's knowledge. It is also about climbing to the place where those who went before us reached, so that I too can see the scenery they saw.
As we live, challenge ourselves, fail, make choices, and take responsibility, there are times when sentences we heard long ago sound different. The sentence itself hasn't changed. What has changed is where I am standing.
That is why these days, I often ask myself this question:
“What is the person who has climbed higher than I have seeing?”
Even when looking at the same thing, what is seen differs
When I first learned development, whether the code worked was what mattered. After a while, the structure of the code began to appear. Further on, I could see how far the impact would reach when something was changed. And as I built software used by many people over a long period, things outside the code began to slowly come into view.
Who will maintain this code, whether it can be understood years from now, whether the cause can be found when a problem occurs, and how many exceptions today's convenient choice will create in the future.
The act of writing code remains the same, but what has changed is the perspective of the person looking at it.
When I don't understand, I change the question
In my work, I occasionally encounter choices that I don't understand. “Why did they go out of their way to do it this way?” “Couldn't it be done more simply?” “Why check to this extent?” At first, it is easy to judge based only on what is visible.
However, imagine a person I deeply respect has made a decision I don't understand. If I have experienced their judgment many times, seen them discover problems I had missed, and watched for a long time the standards by which they work, it becomes difficult to simply think, “That is a wrong choice.”
Instead, the question changes. “What is it that I am not seeing?” This doesn't mean I think the other person is always right. Even the most brilliant person can be wrong.
It is simply that I do not immediately conclude the other person's judgment is wrong just because I do not understand it.
I consider whether the information I have is everything, whether there were constraints the other person faced that I am unaware of, whether they experienced a similar problem in the past, or whether I am looking at the present while they are looking ahead to what comes next.
Respect, perhaps, is not an attitude of unconditionally accepting another's judgment, but rather an attitude of leaving open the possibility that there is something I have not yet seen.
I want to see the process of reaching the destination rather than the result
This thought has also influenced the way I learn things. In the past, when I discovered a good principle, I tried to learn the conclusion. Now, I am curious about something slightly different. “What did they experience to lead them to say this?”
The same applies to the Agile principle that says, 'Working software is valued more than comprehensive documentation.' If you only take the conclusion, it's simple: “I just need to reduce the documentation.”
But in reality, reducing documentation requires many other things.
The code itself must be easy to understand, the names and structure must convey the intent, changes must be small and traceable, and there must be sufficient communication among team members. Necessary knowledge must be able to be delivered and maintained in forms other than documentation.
If you follow only the result without that experience and environment, it becomes something entirely different even if the appearance is similar. That is why now, when I see a principle left by someone, I am curious not about the sentence itself, but what that person had seen and experienced before arriving at those words.
What failures did they repeat, what was the problem, what did they try, and what among those did they discard. And after experiencing such things one by one myself, there are times when a sentence I read long ago reads completely differently. The sentence is the same. I have simply climbed a bit higher to where that sentence resides.
Working together may be the act of borrowing each other's perspectives
Even when looking at the same problem, what is seen differs depending on the role and experience. A developer might be seeing the difficulty of implementation. A tester might be seeing the difficulty of verification. An operator might be seeing the cost after a problem occurs.
A user might be seeing the small, repeating inconveniences of every day. A manager might be seeing the impact a single decision now will have on many people and future schedules.
Therefore, I believe that to work together, rather than thinking the same as the other person, one must first be able to see what the other person is seeing.
Even after climbing to that point and looking at the same thing, opinions may differ. That is fine. In fact, that is when the real discussion can begin. Because we can then talk about what each of us knows and doesn't know, and what we see the same way but judge differently.
Again, the shoulders of giants
The 'high level' I speak of does not refer to a human hierarchy. It is not about who is more superior or who is lacking. It means expanding the scope of experience and understanding to a place where one can see things that are invisible from one's current position.
Once you climb there, you may realize why a choice that was initially incomprehensible was necessary. Conversely, even after fully understanding, you may judge that the choice was wrong. Both are fine. The important thing is not to reach a conclusion too quickly while still in a state of not seeing.
So, when the actions of someone I respect are incomprehensible, I try to change my question. Instead of “Why did they do that?”, I ask, “What was visible to that person?” And someday, when I have climbed to where that person was looking, I want to ask the same question once more.
If our thoughts are still different then, only then will we be able to look at the same scenery and speak of our different thoughts.
Standing on the shoulders of giants may, perhaps, be the process of becoming a person who can see the scenery that those who climbed there first once saw.
A Trip to Suncheon and Yeosu, Day 3
The last day, ending with some studying and a run.

A Trip to Suncheon and Yeosu, Day 2
The second day of the trip, from a clear morning by the sea to sunset and dusk on Baekyado Island.

A Trip to Suncheon and Yeosu
A trip to Suncheon and Yeosu.


Comments 0
Share your thoughts on this article.
Loading comments…