safibta
|
goals
Star this Commitment
Week 23 of 23
safibta commits to:
in the journal
22
1
No more reports due
|
My Commitment Journal
 safibta
December 22, 2019, 6:47 AM
|
|
|
For reference: - Checklist for creating/updating this journal entry: Update the start time Update the end time Select all and copy set alarms at t-1hr6min, t-1hr21min, and t-1hr51min titled stickk Upload the commitment to the journal --- Start time: 2019-12-22 1545 in KST End time: 2019-12-23 1900 in KST Task(s): - rules of DW apply until either the end of the interval of the commitment defined in the present journal entry or until I have finished doing the prompts 2, 4, and 5 of of 20192aht final exam Commitment: The commitment is to accomplish the tasks stated above in the present journal entry in the time duration from the start time stated above in the present journal entry to the end time stated above in the present journal entry, and if this task is not accomplished, the commitment is to tear a workable 5000 KRW currency note into at least three pieces before 2359 in KST on the date which occurs exactly 24 hours after the end time stated in the present journal entry. Notes applicable to the present journal entry: - the present journal entry overrides all the previous journal entries in the present Stickk commitment - Any update to the present Stickk commitment shall take 1 hour to take effect from the time that the said update is posted in the journal of the present Stickk commitment. In the said 1-hour window, the Stickk commitment shall stay as it was in the past instance. - note that even if the start time mentioned in the present journal entry has passed, the commitment shall hold true (e.g. say its 5 p.m. at the time of posting the journal entry and I want to have 2 hours logged between 4:30 p.m. and 6:30 p.m., the commitment shall be valid at the end time) - Deep Work Stint (abbreviated as DW) is defined here as it has been defined in the most recent Stickk commitment in my Stickk account containing the string “routine system” in the title with case not considered sensitive, whether that Stickk commitment is currently active, dismissed, or inactive. - Note on loopholes: I assume there are loopholes in all my Stickk commitments. When I exploit a loophole, in order for this loophole to be considered a valid reason for not incurring the penalty of the present Stickk commitment as defined in the present journal entry, I must state in digital or physical writing a satisfactory definition of the loophole that I have exploited in the considered instance. For this definition of the considered loophole to be considered valid, the following criteria must hold: --- I must end this definition with a period. --- I must write this definition of the considered loophole before exploiting the considered loophole. --- This definition of the loophole must not cite a bulleting error as a source of exploitation of the exploited loophole. --- I must put up a reminder in my PDA to prompt me to read the present journal entry in a near future SDEL (e.g. I can write: “SDEL: read infodiet commitment”) - Note on specificity of clauses: Since it is mostly impossible for any commitment to be specific enough for the person committing to it to not be able to exploit a loophole in this commitment, the level of generality of each commitment in the present journal entry shall be considered of the level that is same as present level of specificity of the respective commitment. - Relaxation clause: number of relaxation periods of any duration allowed for the present stick commitment is zero |
|
|
safibta
December 19, 2019, 9:34 AM
|
|
|
For reference: - Checklist for creating/updating this journal entry: Update the start time Update the end time Select all and copy set alarms at t-1hr6min, t-1hr21min, and t-1hr51min titled stickk Upload the commitment to the journal --- Start time: 2019-12-19 1830 in KST End time: 2019-12-20 1900 in KST Task(s): - rules of DW apply until either the end of the interval of the commitment defined in the present journal entry or until I have submitted my remaining 20192em1 assignments to Professor Byeon Commitment: The commitment is to accomplish the tasks stated above in the present journal entry in the time duration from the start time stated above in the present journal entry to the end time stated above in the present journal entry, and if this task is not accomplished, the commitment is to tear a workable 5000 KRW currency note into at least three pieces before 2359 in KST on the date which occurs exactly 24 hours after the end time stated in the present journal entry. Notes applicable to the present journal entry: - the present journal entry overrides all the previous journal entries in the present Stickk commitment - Any update to the present Stickk commitment shall take 1 hour to take effect from the time that the said update is posted in the journal of the present Stickk commitment. In the said 1-hour window, the Stickk commitment shall stay as it was in the past instance. - note that even if the start time mentioned in the present journal entry has passed, the commitment shall hold true (e.g. say its 5 p.m. at the time of posting the journal entry and I want to have 2 hours logged between 4:30 p.m. and 6:30 p.m., the commitment shall be valid at the end time) - Deep Work Stint (abbreviated as DW) is defined here as it has been defined in the most recent Stickk commitment in my Stickk account containing the string “routine system” in the title with case not considered sensitive, whether that Stickk commitment is currently active, dismissed, or inactive. - Note on loopholes: I assume there are loopholes in all my Stickk commitments. When I exploit a loophole, in order for this loophole to be considered a valid reason for not incurring the penalty of the present Stickk commitment as defined in the present journal entry, I must state in digital or physical writing a satisfactory definition of the loophole that I have exploited in the considered instance. For this definition of the considered loophole to be considered valid, the following criteria must hold: --- I must end this definition with a period. --- I must write this definition of the considered loophole before exploiting the considered loophole. --- This definition of the loophole must not cite a bulleting error as a source of exploitation of the exploited loophole. --- I must put up a reminder in my PDA to prompt me to read the present journal entry in a near future SDEL (e.g. I can write: “SDEL: read infodiet commitment”) - Note on specificity of clauses: Since it is mostly impossible for any commitment to be specific enough for the person committing to it to not be able to exploit a loophole in this commitment, the level of generality of each commitment in the present journal entry shall be considered of the level that is same as present level of specificity of the respective commitment. - Relaxation clause: number of relaxation periods of any duration allowed for the present stick commitment is zero |
|
|
safibta
November 17, 2019, 7:07 PM
|
|
|
For reference: - Checklist for creating/updating this journal entry: Update the start time Update the end time Select all and copy set alarms at t-1hr6min, t-1hr21min, and t-1hr51min titled stickk Upload the commitment to the journal --- Start time: 2019-11-18 0406 in KST End time: 2019-11-18 1245 in KST Task(s): - spend x21 working on 20192aem1 presentation - rules of DW apply in the interval of the commitment defined in the present journal entry Commitment: The commitment is to accomplish the tasks stated above in the present journal entry in the time duration from the start time stated above in the present journal entry to the end time stated above in the present journal entry, and if this task is not accomplished, the commitment is to tear a workable 5000 KRW currency note into at least three pieces before 2359 in KST on the date which occurs exactly 24 hours after the end time stated in the present journal entry. Notes applicable to the present journal entry: - the present journal entry overrides all the previous journal entries in the present Stickk commitment - Any update to the present Stickk commitment shall take 1 hour to take effect from the time that the said update is posted in the journal of the present Stickk commitment. In the said 1-hour window, the Stickk commitment shall stay as it was in the past instance. - note that even if the start time mentioned in the present journal entry has passed, the commitment shall hold true (e.g. say its 5 p.m. at the time of posting the journal entry and I want to have 2 hours logged between 4:30 p.m. and 6:30 p.m., the commitment shall be valid at the end time) - Deep Work Stint (abbreviated as DW) is defined here as it has been defined in the most recent Stickk commitment in my Stickk account containing the string “routine system” in the title with case not considered sensitive, whether that Stickk commitment is currently active, dismissed, or inactive. - Note on loopholes: I assume there are loopholes in all my Stickk commitments. When I exploit a loophole, in order for this loophole to be considered a valid reason for not incurring the penalty of the present Stickk commitment as defined in the present journal entry, I must state in digital or physical writing a satisfactory definition of the loophole that I have exploited in the considered instance. For this definition of the considered loophole to be considered valid, the following criteria must hold: --- I must end this definition with a period. --- I must write this definition of the considered loophole before exploiting the considered loophole. --- This definition of the loophole must not cite a bulleting error as a source of exploitation of the exploited loophole. --- I must put up a reminder in my PDA to prompt me to read the present journal entry in a near future SDEL (e.g. I can write: “SDEL: read infodiet commitment”) - Note on specificity of clauses: Since it is mostly impossible for any commitment to be specific enough for the person committing to it to not be able to exploit a loophole in this commitment, the level of generality of each commitment in the present journal entry shall be considered of the level that is same as present level of specificity of the respective commitment. - Relaxation clause: number of relaxation periods of any duration allowed for the present stick commitment is zero |
|
|
safibta
November 16, 2019, 11:49 AM
|
|
|
For reference: - Checklist for creating/updating this journal entry: Update the start time Update the end time Select all and copy set alarms at t-1hr6min, t-1hr21min, and t-1hr51min titled stickk Upload the commitment to the journal --- Start time: 2019-11-16 (sat) 2044 in KST End time: 2019-11-17 (sun) 0545 in KST Task(s): - spend x21 working on 20192aem1 presentation - rules of DW apply in the interval of the commitment defined in the present journal entry Commitment: The commitment is to accomplish the tasks stated above in the present journal entry in the time duration from the start time stated above in the present journal entry to the end time stated above in the present journal entry, and if this task is not accomplished, the commitment is to tear a workable 5000 KRW currency note into at least three pieces before 2359 in KST on the date which occurs exactly 24 hours after the end time stated in the present journal entry. Notes applicable to the present journal entry: - the present journal entry overrides all the previous journal entries in the present Stickk commitment - Any update to the present Stickk commitment shall take 1 hour to take effect from the time that the said update is posted in the journal of the present Stickk commitment. In the said 1-hour window, the Stickk commitment shall stay as it was in the past instance. - note that even if the start time mentioned in the present journal entry has passed, the commitment shall hold true (e.g. say its 5 p.m. at the time of posting the journal entry and I want to have 2 hours logged between 4:30 p.m. and 6:30 p.m., the commitment shall be valid at the end time) - Deep Work Stint (abbreviated as DW) is defined here as it has been defined in the most recent Stickk commitment in my Stickk account containing the string “routine system” in the title with case not considered sensitive, whether that Stickk commitment is currently active, dismissed, or inactive. - Note on loopholes: I assume there are loopholes in all my Stickk commitments. When I exploit a loophole, in order for this loophole to be considered a valid reason for not incurring the penalty of the present Stickk commitment as defined in the present journal entry, I must state in digital or physical writing a satisfactory definition of the loophole that I have exploited in the considered instance. For this definition of the considered loophole to be considered valid, the following criteria must hold: --- I must end this definition with a period. --- I must write this definition of the considered loophole before exploiting the considered loophole. --- This definition of the loophole must not cite a bulleting error as a source of exploitation of the exploited loophole. --- I must put up a reminder in my PDA to prompt me to read the present journal entry in a near future SDEL (e.g. I can write: “SDEL: read infodiet commitment”) - Note on specificity of clauses: Since it is mostly impossible for any commitment to be specific enough for the person committing to it to not be able to exploit a loophole in this commitment, the level of generality of each commitment in the present journal entry shall be considered of the level that is same as present level of specificity of the respective commitment. - Relaxation clause: number of relaxation periods of any duration allowed for the present stick commitment is zero |
|
This Commitment has no photos.
Displaying 1-4 of 23 results.
December 23 to December 30
Successful (referee feedback expired)
Success
No report submitted
December 16 to December 23
Successful (referee feedback expired)
Success
No report submitted
December 9 to December 16
Successful (referee feedback expired)
Success
No report submitted
December 2 to December 9
Successful (referee feedback expired)
Success
No report submitted
.
