Tome.gg Protocols
Ask or search…
K
Links

Situational Literacy

Author
Start date
Implementation issue
Deleted
06/05/2023
06/05/2023

Summary

The dimension of Situational Literacy is the skill of contextualization. It is the ability to read situations effectively, to perform and assess decision making, and to recognize the pros and cons of different approaches or methods across a variety of situations.

Motivation

Why are we doing this? What use cases does it support? What is the expected outcome?
Please focus on explaining the motivation so that if this RFC is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.

Detailed Design

Nightmare scenarios

Case 1: Overwhelmed students

Scenario: Getting insecure about other's mastery, or fearing to make mistakes, or disappointing others

Case 2: Feeling pressured to be passionate

Scenario: The student does not love what they do, and feels the pressure to be as passionate as their peers in the field

Case 3: Reactive, non-planning mindset

Scenario: They don't use their writings to focus their attention, thus resulting to just being reactive to their circumstances and situation.

Case 4: Lack of or denial of one's goal

Scenario: Due to scarcity, fear, or ignorance, a student does not dream of what mountain to accomplish.

Exceptions

Balance: Inhale, and exhale

Part of doing focused work is also learning to accept the down-time, or resting.

Balance: Holistic health

Practice focus in being responsible for yourself, your physical, mental, social, emotional, and spiritual wellbeing. Be responsible for yourself, your family, your friends, your work. Learn to shift in and out of these different dimensions of your life.
Pausing your attention on work does not mean that you are unfocused. You may remain focused even as you switch between the different aspects of your life.

Drawbacks

Why should we not do this? Please consider:
  • implementation cost, both in term of size and complexity
  • whether the proposed feature can be implemented in user space
  • integration of this feature with other existing and planned features
  • cost of migrating (is it a breaking change?)
There are tradeoffs to choosing any path. Attempt to identify them here.

Alternatives

What other designs have been considered? What is the impact of not doing this?

Unresolved questions

  • What parts of the design do you expect to resolve through the RFC process before this gets merged?
  • What parts of the design do you expect to resolve through the implementation of this feature before stabilization?
  • What related issues do you consider out of scope for this RFC that could be addressed in the future independently of the solution that comes out of this RFC?

Future possibilities

Think about what the natural extension and evolution of your proposal would be and how it would affect the project as a whole in a holistic way. Try to use this section as a tool to more fully consider all possible interactions with the project in your proposal. Also consider how this all fits into the roadmap for the project and of the relevant team.
This is also a good place to "dump ideas", if they are out of scope for the RFC you are writing but otherwise related.
If you have tried and cannot think of any future possibilities, you may simply state that you cannot think of anything.
Note that having something written down in the future-possibilities section is not a reason to accept the current or a future RFC; such notes should be in the section on motivation or rationale in this or subsequent RFCs. The section merely provides additional information.
Finishing drafting the RFC? Do not merge the change request, but submit it for review.