VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS75.62%
Net Worth
0.115USD
STEEM
0.000STEEM
SBD
0.209SBD
Effective Power
5.008SP
├── Own SP
0.629SP
└── Incoming DelegationsDeleg
+4.379SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.629SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.379SP | SP |
| Effective Power | 5.008SP | SP |
| Reward SP (pending) | 0.055SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.209SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1022.709986 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7120.949820 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.209 SBD",
"conversions": []
}Account Info
| name | erajasekar |
| id | 731301 |
| rank | 1,294,905 |
| reputation | 1213450141 |
| created | 2018-02-06T19:39:54 |
| recovery_account | steem |
| proxy | None |
| post_count | 1 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-02-06T19:59:36 |
| last_root_post | 2018-02-06T19:59:36 |
| last_vote_time | 2018-02-07T16:29:54 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1022.709986 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7120.949820 VESTS |
| reward_vesting_balance | 112.457925 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2018-02-06T19:54:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 731301,
"name": "erajasekar",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5mgbdwz54PYeoVhZ3X1ZCu9oK7MU2AJDXHX5Pd1RDnZ9LsuykQ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8VLCD3NZ7moW2KGtRRMwGPN56eJs3tstxGWFfPzaxyJHQL3Dbv",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8JizWoFKaeb6hYJDbfrtgngr7o1a5ntsZtf4jkkakDyrchjA7M",
1
]
]
},
"memo_key": "STM8Umi4BoGz6xqLshcLrwYhhA2gY6nowKUyQvdPLEDytsFcseHDT",
"json_metadata": "{\"profile\":{\"profile_image\":\"http://erajasekar.com/assets/images/profile_small.jpg\",\"name\":\"Raja\",\"about\":\"Software Engineer\",\"location\":\"Tampa, FL, USA\",\"website\":\"https://erajasekar.com\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"http://erajasekar.com/assets/images/profile_small.jpg\",\"name\":\"Raja\",\"about\":\"Software Engineer\",\"location\":\"Tampa, FL, USA\",\"website\":\"https://erajasekar.com\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2018-02-06T19:54:00",
"created": "2018-02-06T19:39:54",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 1,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779062511
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779062511
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.209 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "112.457925 VESTS",
"reward_vesting_steem": "0.055 STEEM",
"vesting_shares": "1022.709986 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7120.949820 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 109,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-02-06T19:59:36",
"last_root_post": "2018-02-06T19:59:36",
"last_vote_time": "2018-02-07T16:29:54",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 1213450141,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1294905
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.379 SP to @erajasekar2026/05/18 00:01:51
steemdelegated 4.379 SP to @erajasekar
2026/05/18 00:01:51
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 7120.949820 VESTS |
| Transaction Info | Block #106143183/Trx 594db184bc446e6d02187cc00f6210bc0b4ee4df |
View Raw JSON Data
{
"trx_id": "594db184bc446e6d02187cc00f6210bc0b4ee4df",
"block": 106143183,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T00:01:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "7120.949820 VESTS"
}
]
}steemdelegated 2.711 SP to @erajasekar2026/05/12 02:55:54
steemdelegated 2.711 SP to @erajasekar
2026/05/12 02:55:54
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 4408.739415 VESTS |
| Transaction Info | Block #105974621/Trx 857e3a76583573f8689f9db9d4b7f1521f55bb16 |
View Raw JSON Data
{
"trx_id": "857e3a76583573f8689f9db9d4b7f1521f55bb16",
"block": 105974621,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-12T02:55:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "4408.739415 VESTS"
}
]
}steemdelegated 4.387 SP to @erajasekar2026/04/25 23:23:06
steemdelegated 4.387 SP to @erajasekar
2026/04/25 23:23:06
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 7133.465576 VESTS |
| Transaction Info | Block #105510840/Trx b6b2cbe29d2b816d66ffa3d233f4cb09c4f04ffa |
View Raw JSON Data
{
"trx_id": "b6b2cbe29d2b816d66ffa3d233f4cb09c4f04ffa",
"block": 105510840,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-25T23:23:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "7133.465576 VESTS"
}
]
}steemdelegated 2.737 SP to @erajasekar2026/01/23 07:11:42
steemdelegated 2.737 SP to @erajasekar
2026/01/23 07:11:42
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 4450.286234 VESTS |
| Transaction Info | Block #102851082/Trx cf43f577b4731d7dfdca48d076e669cbb95f2002 |
View Raw JSON Data
{
"trx_id": "cf43f577b4731d7dfdca48d076e669cbb95f2002",
"block": 102851082,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T07:11:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "4450.286234 VESTS"
}
]
}steemdelegated 2.838 SP to @erajasekar2024/12/17 02:31:21
steemdelegated 2.838 SP to @erajasekar
2024/12/17 02:31:21
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 4614.505431 VESTS |
| Transaction Info | Block #91297503/Trx df32572c3ed791737cc941d61e3ba86ea9ef843b |
View Raw JSON Data
{
"trx_id": "df32572c3ed791737cc941d61e3ba86ea9ef843b",
"block": 91297503,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T02:31:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "4614.505431 VESTS"
}
]
}steemdelegated 2.942 SP to @erajasekar2023/11/13 18:13:57
steemdelegated 2.942 SP to @erajasekar
2023/11/13 18:13:57
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 4783.638963 VESTS |
| Transaction Info | Block #79851702/Trx a9c1dff3b8d038fe24548cae880077057a161aa7 |
View Raw JSON Data
{
"trx_id": "a9c1dff3b8d038fe24548cae880077057a161aa7",
"block": 79851702,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T18:13:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "4783.638963 VESTS"
}
]
}steemdelegated 4.748 SP to @erajasekar2023/09/21 21:33:48
steemdelegated 4.748 SP to @erajasekar
2023/09/21 21:33:48
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 7720.917749 VESTS |
| Transaction Info | Block #78347508/Trx 7680feedbe0e815a6c86decb1c7365ab0494072e |
View Raw JSON Data
{
"trx_id": "7680feedbe0e815a6c86decb1c7365ab0494072e",
"block": 78347508,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T21:33:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "7720.917749 VESTS"
}
]
}steemdelegated 4.884 SP to @erajasekar2022/11/03 11:23:54
steemdelegated 4.884 SP to @erajasekar
2022/11/03 11:23:54
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 7942.599187 VESTS |
| Transaction Info | Block #69112897/Trx 955b2d84a5932341b8eab845fcf50a32beda9ac6 |
View Raw JSON Data
{
"trx_id": "955b2d84a5932341b8eab845fcf50a32beda9ac6",
"block": 69112897,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T11:23:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "7942.599187 VESTS"
}
]
}steemdelegated 5.020 SP to @erajasekar2022/01/17 10:41:12
steemdelegated 5.020 SP to @erajasekar
2022/01/17 10:41:12
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 8163.132418 VESTS |
| Transaction Info | Block #60809090/Trx e232ad44f6b4af18f5c8fd63b9758fced7bc0c0a |
View Raw JSON Data
{
"trx_id": "e232ad44f6b4af18f5c8fd63b9758fced7bc0c0a",
"block": 60809090,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T10:41:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "8163.132418 VESTS"
}
]
}steemdelegated 5.133 SP to @erajasekar2021/06/14 00:37:06
steemdelegated 5.133 SP to @erajasekar
2021/06/14 00:37:06
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 8346.901076 VESTS |
| Transaction Info | Block #54607491/Trx 1a5203e701ab4d0b89e3d11d2f92acc3dd1af979 |
View Raw JSON Data
{
"trx_id": "1a5203e701ab4d0b89e3d11d2f92acc3dd1af979",
"block": 54607491,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T00:37:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "8346.901076 VESTS"
}
]
}steemdelegated 5.248 SP to @erajasekar2020/12/11 10:56:21
steemdelegated 5.248 SP to @erajasekar
2020/12/11 10:56:21
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 8534.323050 VESTS |
| Transaction Info | Block #49354960/Trx a0bcdcff8663227c8e09b191c901cdc7f8f194f8 |
View Raw JSON Data
{
"trx_id": "a0bcdcff8663227c8e09b191c901cdc7f8f194f8",
"block": 49354960,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T10:56:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "8534.323050 VESTS"
}
]
}steemdelegated 1.176 SP to @erajasekar2020/12/06 04:33:36
steemdelegated 1.176 SP to @erajasekar
2020/12/06 04:33:36
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49206525/Trx c724dec662a882469055d4477d9332633169c650 |
View Raw JSON Data
{
"trx_id": "c724dec662a882469055d4477d9332633169c650",
"block": 49206525,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T04:33:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "1912.543513 VESTS"
}
]
}steemdelegated 5.252 SP to @erajasekar2020/12/05 14:34:33
steemdelegated 5.252 SP to @erajasekar
2020/12/05 14:34:33
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 8540.530904 VESTS |
| Transaction Info | Block #49190059/Trx 0d3c71839cf6f80f1779ff913ba951b77b384b2e |
View Raw JSON Data
{
"trx_id": "0d3c71839cf6f80f1779ff913ba951b77b384b2e",
"block": 49190059,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T14:34:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "8540.530904 VESTS"
}
]
}steemdelegated 1.181 SP to @erajasekar2020/11/02 15:10:45
steemdelegated 1.181 SP to @erajasekar
2020/11/02 15:10:45
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48257257/Trx 35e86a4997f03f50a241fe404545af43e18be3b3 |
View Raw JSON Data
{
"trx_id": "35e86a4997f03f50a241fe404545af43e18be3b3",
"block": 48257257,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-02T15:10:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "1920.017158 VESTS"
}
]
}steemdelegated 5.377 SP to @erajasekar2020/05/09 05:30:42
steemdelegated 5.377 SP to @erajasekar
2020/05/09 05:30:42
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 8743.336263 VESTS |
| Transaction Info | Block #43216769/Trx a6a512f823965cddf085d70f0458210438f2f1af |
View Raw JSON Data
{
"trx_id": "a6a512f823965cddf085d70f0458210438f2f1af",
"block": 43216769,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T05:30:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "8743.336263 VESTS"
}
]
}steemdelegated 1.201 SP to @erajasekar2020/05/08 09:04:51
steemdelegated 1.201 SP to @erajasekar
2020/05/08 09:04:51
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43192828/Trx c792af659351b8d22aa92e46d63b6b4fac8de2b7 |
View Raw JSON Data
{
"trx_id": "c792af659351b8d22aa92e46d63b6b4fac8de2b7",
"block": 43192828,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T09:04:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "1953.311140 VESTS"
}
]
}steemdelegated 5.385 SP to @erajasekar2020/04/15 21:28:42
steemdelegated 5.385 SP to @erajasekar
2020/04/15 21:28:42
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 8756.313682 VESTS |
| Transaction Info | Block #42562400/Trx 46f7930c8782b115085a96ed90ae6e2cc4ba3f00 |
View Raw JSON Data
{
"trx_id": "46f7930c8782b115085a96ed90ae6e2cc4ba3f00",
"block": 42562400,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-15T21:28:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "8756.313682 VESTS"
}
]
}2020/02/06 20:48:51
2020/02/06 20:48:51
| parent author | erajasekar |
| parent permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| author | steemitboard |
| permlink | steemitboard-notify-erajasekar-20200206t204851000z |
| title | |
| body | Congratulations @erajasekar! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@erajasekar/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@erajasekar) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=erajasekar)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator">SteemitBoard Ranking update - A better rich list comparator</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #40592001/Trx 0c7e49b1a9fd267143c7c965fd87932fd9bdab96 |
View Raw JSON Data
{
"trx_id": "0c7e49b1a9fd267143c7c965fd87932fd9bdab96",
"block": 40592001,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-02-06T20:48:51",
"op": [
"comment",
{
"parent_author": "erajasekar",
"parent_permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"author": "steemitboard",
"permlink": "steemitboard-notify-erajasekar-20200206t204851000z",
"title": "",
"body": "Congratulations @erajasekar! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@erajasekar/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@erajasekar) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=erajasekar)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-a-better-rich-list-comparator\">SteemitBoard Ranking update - A better rich list comparator</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.505 SP to @erajasekar2019/05/12 14:43:36
steemdelegated 5.505 SP to @erajasekar
2019/05/12 14:43:36
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 8951.936487 VESTS |
| Transaction Info | Block #32845275/Trx 11e1eadef50eccc09e90c6b0f0f2f759d15f767c |
View Raw JSON Data
{
"trx_id": "11e1eadef50eccc09e90c6b0f0f2f759d15f767c",
"block": 32845275,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-05-12T14:43:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "8951.936487 VESTS"
}
]
}2019/02/06 20:02:15
2019/02/06 20:02:15
| parent author | erajasekar |
| parent permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| author | steemitboard |
| permlink | steemitboard-notify-erajasekar-20190206t200215000z |
| title | |
| body | Congratulations @erajasekar! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@erajasekar/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_[Click here to view your Board](https://steemitboard.com/@erajasekar)_</sub> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #30118977/Trx dc7822f45882ccb02ef8ff9b194ad9282fcef013 |
View Raw JSON Data
{
"trx_id": "dc7822f45882ccb02ef8ff9b194ad9282fcef013",
"block": 30118977,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-02-06T20:02:15",
"op": [
"comment",
{
"parent_author": "erajasekar",
"parent_permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"author": "steemitboard",
"permlink": "steemitboard-notify-erajasekar-20190206t200215000z",
"title": "",
"body": "Congratulations @erajasekar! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@erajasekar/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@erajasekar)_</sub>\n\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.628 SP to @erajasekar2018/05/16 20:16:15
steemdelegated 5.628 SP to @erajasekar
2018/05/16 20:16:15
| delegator | steem |
| delegatee | erajasekar |
| vesting shares | 9151.488922 VESTS |
| Transaction Info | Block #22489826/Trx 1f5fdeee6c4c4e2c68643d51e0e16f14e8a02d13 |
View Raw JSON Data
{
"trx_id": "1f5fdeee6c4c4e2c68643d51e0e16f14e8a02d13",
"block": 22489826,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-16T20:16:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "erajasekar",
"vesting_shares": "9151.488922 VESTS"
}
]
}erajasekarreceived 0.209 SBD, 0.069 SP author reward for @erajasekar / how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive2018/02/13 19:59:36
erajasekarreceived 0.209 SBD, 0.069 SP author reward for @erajasekar / how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive
2018/02/13 19:59:36
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| sbd payout | 0.209 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 112.457925 VESTS |
| Transaction Info | Block #19842562/Virtual Operation #5 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 19842562,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 5,
"timestamp": "2018-02-13T19:59:36",
"op": [
"author_reward",
{
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"sbd_payout": "0.209 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "112.457925 VESTS"
}
]
}erajasekarupvoted (100.00%) @steemitboard / steemitboard-notify-erajasekar-20180207t055650000z2018/02/07 16:29:54
erajasekarupvoted (100.00%) @steemitboard / steemitboard-notify-erajasekar-20180207t055650000z
2018/02/07 16:29:54
| voter | erajasekar |
| author | steemitboard |
| permlink | steemitboard-notify-erajasekar-20180207t055650000z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19665899/Trx 0f8beacdaa6f3a07184ebc5902764b68237b79a0 |
View Raw JSON Data
{
"trx_id": "0f8beacdaa6f3a07184ebc5902764b68237b79a0",
"block": 19665899,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-07T16:29:54",
"op": [
"vote",
{
"voter": "erajasekar",
"author": "steemitboard",
"permlink": "steemitboard-notify-erajasekar-20180207t055650000z",
"weight": 10000
}
]
}2018/02/07 06:33:12
2018/02/07 06:33:12
| voter | sakelazon |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19653982/Trx d2bd0a6ef173403bf88180291e76dd63d5a5abac |
View Raw JSON Data
{
"trx_id": "d2bd0a6ef173403bf88180291e76dd63d5a5abac",
"block": 19653982,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-07T06:33:12",
"op": [
"vote",
{
"voter": "sakelazon",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"weight": 10000
}
]
}2018/02/07 06:33:09
2018/02/07 06:33:09
| voter | alinazajcev |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19653981/Trx 5b12c9a20ea90e9f5c252e31b94621a1eaddac35 |
View Raw JSON Data
{
"trx_id": "5b12c9a20ea90e9f5c252e31b94621a1eaddac35",
"block": 19653981,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-07T06:33:09",
"op": [
"vote",
{
"voter": "alinazajcev",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"weight": 10000
}
]
}2018/02/07 05:56:48
2018/02/07 05:56:48
| parent author | erajasekar |
| parent permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| author | steemitboard |
| permlink | steemitboard-notify-erajasekar-20180207t055650000z |
| title | |
| body | Congratulations @erajasekar! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@erajasekar) You published your First Post [](http://steemitboard.com/@erajasekar) You made your First Vote [](http://steemitboard.com/@erajasekar) You got a First Vote Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #19653256/Trx 70bd8b4262d28658ff58adf048b44c51bb44d90b |
View Raw JSON Data
{
"trx_id": "70bd8b4262d28658ff58adf048b44c51bb44d90b",
"block": 19653256,
"trx_in_block": 49,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-07T05:56:48",
"op": [
"comment",
{
"parent_author": "erajasekar",
"parent_permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"author": "steemitboard",
"permlink": "steemitboard-notify-erajasekar-20180207t055650000z",
"title": "",
"body": "Congratulations @erajasekar! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@erajasekar) You published your First Post\n[](http://steemitboard.com/@erajasekar) You made your First Vote\n[](http://steemitboard.com/@erajasekar) You got a First Vote\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}2018/02/06 20:57:39
2018/02/06 20:57:39
| voter | bue |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19642486/Trx 119ad6ec1437206e8916f9b5e24852b009efa3d8 |
View Raw JSON Data
{
"trx_id": "119ad6ec1437206e8916f9b5e24852b009efa3d8",
"block": 19642486,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:57:39",
"op": [
"vote",
{
"voter": "bue",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"weight": 10000
}
]
}2018/02/06 20:31:51
2018/02/06 20:31:51
| voter | hr1 |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| weight | 63 (0.63%) |
| Transaction Info | Block #19641970/Trx 0739863806b58389d85b7b869951c4e3f71a5dc2 |
View Raw JSON Data
{
"trx_id": "0739863806b58389d85b7b869951c4e3f71a5dc2",
"block": 19641970,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:31:51",
"op": [
"vote",
{
"voter": "hr1",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"weight": 63
}
]
}erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive2018/02/06 20:28:30
erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive
2018/02/06 20:28:30
| parent author | |
| parent permlink | computer-science |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| title | How knowing computer scheduling algorithms can help us to be productive? |
| body | @@ -10474,118 +10474,8 @@ ze.%3C -img src=%22https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md%22/%3E%3C /p%3E%0A |
| json metadata | {"tags":["computer-science","algorithms","productivity","education","teaching"],"image":["https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png"],"links":["http://amzn.to/2CFOsxe","https://en.wikipedia.org/wiki/Priority_inversion","https://en.wikipedia.org/wiki/Preemption_%28computing%29","https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29","https://en.wikipedia.org/wiki/Timeboxing","https://en.wikipedia.org/wiki/Pomodoro_Technique","https://en.wikipedia.org/wiki/Interrupt_coalescing","http://amzn.to/2F1ZyLy"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #19641905/Trx 6a0cba7fd03cdc0d56967d69b09aa25a564d7ef2 |
View Raw JSON Data
{
"trx_id": "6a0cba7fd03cdc0d56967d69b09aa25a564d7ef2",
"block": 19641905,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:28:30",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "computer-science",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"title": "How knowing computer scheduling algorithms can help us to be productive?",
"body": "@@ -10474,118 +10474,8 @@\n ze.%3C\n-img src=%22https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md%22/%3E%3C\n /p%3E%0A\n",
"json_metadata": "{\"tags\":[\"computer-science\",\"algorithms\",\"productivity\",\"education\",\"teaching\"],\"image\":[\"https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png\"],\"links\":[\"http://amzn.to/2CFOsxe\",\"https://en.wikipedia.org/wiki/Priority_inversion\",\"https://en.wikipedia.org/wiki/Preemption_%28computing%29\",\"https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29\",\"https://en.wikipedia.org/wiki/Timeboxing\",\"https://en.wikipedia.org/wiki/Pomodoro_Technique\",\"https://en.wikipedia.org/wiki/Interrupt_coalescing\",\"http://amzn.to/2F1ZyLy\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive2018/02/06 20:27:36
erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive
2018/02/06 20:27:36
| parent author | |
| parent permlink | computer-science |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| title | How knowing computer scheduling algorithms can help us to be productive? |
| body | @@ -685,16 +685,22 @@ kquote%3E%3C +code%3E%3C em%3EYou s @@ -782,24 +782,31 @@ last%3C/em%3E%3C/ +code%3E%3C/ blockquote%3E%0A @@ -3015,26 +3015,33 @@ rithm:%3C/p%3E%0A%3C -pr +blockquot e%3E%3Ccode%3E%3Cem%3E @@ -3206,26 +3206,33 @@ em%3E%3C/code%3E%3C/ -pr +blockquot e%3E%0A%3Cp%3E%3Cem%3EFo @@ -4370,26 +4370,33 @@ hat is%3C/p%3E%0A%3C -pr +blockquot e%3E%3Ccode%3E%3Cem%3E @@ -4503,26 +4503,33 @@ em%3E%3C/code%3E%3C/ -pr +blockquot e%3E%0A%3Ch3%3EHow t @@ -5137,26 +5137,33 @@ ing as%3C/p%3E%0A%3C -pr +blockquot e%3E%3Ccode%3E%3Cem%3E @@ -5409,26 +5409,33 @@ em%3E%3C/code%3E%3C/ -pr +blockquot e%3E%0A%3Cp%3EBut pr @@ -8434,18 +8434,25 @@ t:%3C/p%3E%0A%3C -pr +blockquot e%3E%3Ccode%3E @@ -8699,18 +8699,25 @@ /code%3E%3C/ -pr +blockquot e%3E%0A%3Cp%3ETh |
| json metadata | {"tags":["computer-science","algorithms","productivity","education","teaching"],"image":["https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md","https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png"],"links":["http://amzn.to/2CFOsxe","https://en.wikipedia.org/wiki/Priority_inversion","https://en.wikipedia.org/wiki/Preemption_%28computing%29","https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29","https://en.wikipedia.org/wiki/Timeboxing","https://en.wikipedia.org/wiki/Pomodoro_Technique","https://en.wikipedia.org/wiki/Interrupt_coalescing","http://amzn.to/2F1ZyLy"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #19641887/Trx 1e3b2755e8ee2c4ac8818a89178fdf23c63e6b13 |
View Raw JSON Data
{
"trx_id": "1e3b2755e8ee2c4ac8818a89178fdf23c63e6b13",
"block": 19641887,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:27:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "computer-science",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"title": "How knowing computer scheduling algorithms can help us to be productive?",
"body": "@@ -685,16 +685,22 @@\n kquote%3E%3C\n+code%3E%3C\n em%3EYou s\n@@ -782,24 +782,31 @@\n last%3C/em%3E%3C/\n+code%3E%3C/\n blockquote%3E%0A\n@@ -3015,26 +3015,33 @@\n rithm:%3C/p%3E%0A%3C\n-pr\n+blockquot\n e%3E%3Ccode%3E%3Cem%3E\n@@ -3206,26 +3206,33 @@\n em%3E%3C/code%3E%3C/\n-pr\n+blockquot\n e%3E%0A%3Cp%3E%3Cem%3EFo\n@@ -4370,26 +4370,33 @@\n hat is%3C/p%3E%0A%3C\n-pr\n+blockquot\n e%3E%3Ccode%3E%3Cem%3E\n@@ -4503,26 +4503,33 @@\n em%3E%3C/code%3E%3C/\n-pr\n+blockquot\n e%3E%0A%3Ch3%3EHow t\n@@ -5137,26 +5137,33 @@\n ing as%3C/p%3E%0A%3C\n-pr\n+blockquot\n e%3E%3Ccode%3E%3Cem%3E\n@@ -5409,26 +5409,33 @@\n em%3E%3C/code%3E%3C/\n-pr\n+blockquot\n e%3E%0A%3Cp%3EBut pr\n@@ -8434,18 +8434,25 @@\n t:%3C/p%3E%0A%3C\n-pr\n+blockquot\n e%3E%3Ccode%3E\n@@ -8699,18 +8699,25 @@\n /code%3E%3C/\n-pr\n+blockquot\n e%3E%0A%3Cp%3ETh\n",
"json_metadata": "{\"tags\":[\"computer-science\",\"algorithms\",\"productivity\",\"education\",\"teaching\"],\"image\":[\"https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md\",\"https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png\"],\"links\":[\"http://amzn.to/2CFOsxe\",\"https://en.wikipedia.org/wiki/Priority_inversion\",\"https://en.wikipedia.org/wiki/Preemption_%28computing%29\",\"https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29\",\"https://en.wikipedia.org/wiki/Timeboxing\",\"https://en.wikipedia.org/wiki/Pomodoro_Technique\",\"https://en.wikipedia.org/wiki/Interrupt_coalescing\",\"http://amzn.to/2F1ZyLy\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive2018/02/06 20:26:09
erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive
2018/02/06 20:26:09
| parent author | |
| parent permlink | computer-science |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| title | How knowing computer scheduling algorithms can help us to be productive? |
| body | @@ -677,19 +677,23 @@ p%3E%0A%3C -p%3E%3Cem%3E> +blockquote%3E%3Cem%3E You @@ -780,17 +780,26 @@ t%3C/em%3E%3C/ -p +blockquote %3E%0A%3Cp%3EThi @@ -1478,26 +1478,33 @@ says,%3C/p%3E%0A%3C -pr +blockquot e%3E%3Ccode%3E%3Cem%3E @@ -1686,26 +1686,33 @@ em%3E%3C/code%3E%3C/ -pr +blockquot e%3E%0A%3Cp%3EIt%E2%80%99s l |
| json metadata | {"tags":["computer-science","algorithms","productivity","education","teaching"],"image":["https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md","https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png"],"links":["http://amzn.to/2CFOsxe","https://en.wikipedia.org/wiki/Priority_inversion","https://en.wikipedia.org/wiki/Preemption_%28computing%29","https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29","https://en.wikipedia.org/wiki/Timeboxing","https://en.wikipedia.org/wiki/Pomodoro_Technique","https://en.wikipedia.org/wiki/Interrupt_coalescing","http://amzn.to/2F1ZyLy"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #19641858/Trx cab2970434f5e39b1a1b593a1f4707de56ef8686 |
View Raw JSON Data
{
"trx_id": "cab2970434f5e39b1a1b593a1f4707de56ef8686",
"block": 19641858,
"trx_in_block": 56,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:26:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "computer-science",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"title": "How knowing computer scheduling algorithms can help us to be productive?",
"body": "@@ -677,19 +677,23 @@\n p%3E%0A%3C\n-p%3E%3Cem%3E> \n+blockquote%3E%3Cem%3E\n You \n@@ -780,17 +780,26 @@\n t%3C/em%3E%3C/\n-p\n+blockquote\n %3E%0A%3Cp%3EThi\n@@ -1478,26 +1478,33 @@\n says,%3C/p%3E%0A%3C\n-pr\n+blockquot\n e%3E%3Ccode%3E%3Cem%3E\n@@ -1686,26 +1686,33 @@\n em%3E%3C/code%3E%3C/\n-pr\n+blockquot\n e%3E%0A%3Cp%3EIt%E2%80%99s l\n",
"json_metadata": "{\"tags\":[\"computer-science\",\"algorithms\",\"productivity\",\"education\",\"teaching\"],\"image\":[\"https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md\",\"https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png\"],\"links\":[\"http://amzn.to/2CFOsxe\",\"https://en.wikipedia.org/wiki/Priority_inversion\",\"https://en.wikipedia.org/wiki/Preemption_%28computing%29\",\"https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29\",\"https://en.wikipedia.org/wiki/Timeboxing\",\"https://en.wikipedia.org/wiki/Pomodoro_Technique\",\"https://en.wikipedia.org/wiki/Interrupt_coalescing\",\"http://amzn.to/2F1ZyLy\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive2018/02/06 20:25:15
erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive
2018/02/06 20:25:15
| parent author | |
| parent permlink | computer-science |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| title | How knowing computer scheduling algorithms can help us to be productive? |
| body | @@ -674,29 +674,26 @@ :%3C/p%3E%0A%3Cp -re%3E%3Ccode %3E%3Cem%3E +> You shou @@ -772,34 +772,25 @@ last%3C/em%3E%3C/ -code%3E%3C/pre +p %3E%0A%3Cp%3EThis st |
| json metadata | {"tags":["computer-science","algorithms","productivity","education","teaching"],"image":["https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md","https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png"],"links":["http://amzn.to/2CFOsxe","https://en.wikipedia.org/wiki/Priority_inversion","https://en.wikipedia.org/wiki/Preemption_%28computing%29","https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29","https://en.wikipedia.org/wiki/Timeboxing","https://en.wikipedia.org/wiki/Pomodoro_Technique","https://en.wikipedia.org/wiki/Interrupt_coalescing","http://amzn.to/2F1ZyLy"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #19641840/Trx 468c5d5fe2b91f462a3e1c175ee37b462a81d3d2 |
View Raw JSON Data
{
"trx_id": "468c5d5fe2b91f462a3e1c175ee37b462a81d3d2",
"block": 19641840,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:25:15",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "computer-science",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"title": "How knowing computer scheduling algorithms can help us to be productive?",
"body": "@@ -674,29 +674,26 @@\n :%3C/p%3E%0A%3Cp\n-re%3E%3Ccode\n %3E%3Cem%3E\n+> \n You shou\n@@ -772,34 +772,25 @@\n last%3C/em%3E%3C/\n-code%3E%3C/pre\n+p\n %3E%0A%3Cp%3EThis st\n",
"json_metadata": "{\"tags\":[\"computer-science\",\"algorithms\",\"productivity\",\"education\",\"teaching\"],\"image\":[\"https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md\",\"https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png\"],\"links\":[\"http://amzn.to/2CFOsxe\",\"https://en.wikipedia.org/wiki/Priority_inversion\",\"https://en.wikipedia.org/wiki/Preemption_%28computing%29\",\"https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29\",\"https://en.wikipedia.org/wiki/Timeboxing\",\"https://en.wikipedia.org/wiki/Pomodoro_Technique\",\"https://en.wikipedia.org/wiki/Interrupt_coalescing\",\"http://amzn.to/2F1ZyLy\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}erajasekarupvoted (100.00%) @steemstem / steemstem-distilled-222018/02/06 20:04:42
erajasekarupvoted (100.00%) @steemstem / steemstem-distilled-22
2018/02/06 20:04:42
| voter | erajasekar |
| author | steemstem |
| permlink | steemstem-distilled-22 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19641429/Trx 34c3474cdf47a2925bb087ac2674e6714b4269c4 |
View Raw JSON Data
{
"trx_id": "34c3474cdf47a2925bb087ac2674e6714b4269c4",
"block": 19641429,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:04:42",
"op": [
"vote",
{
"voter": "erajasekar",
"author": "steemstem",
"permlink": "steemstem-distilled-22",
"weight": 10000
}
]
}erajasekarfollowed @steemstem2018/02/06 20:04:06
erajasekarfollowed @steemstem
2018/02/06 20:04:06
| required auths | [] |
| required posting auths | ["erajasekar"] |
| id | follow |
| json | ["follow",{"follower":"erajasekar","following":"steemstem","what":["blog"]}] |
| Transaction Info | Block #19641417/Trx 942335a3abaea6ee9b73e6773e84a2a399bb96dc |
View Raw JSON Data
{
"trx_id": "942335a3abaea6ee9b73e6773e84a2a399bb96dc",
"block": 19641417,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:04:06",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"erajasekar"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"erajasekar\",\"following\":\"steemstem\",\"what\":[\"blog\"]}]"
}
]
}2018/02/06 20:02:21
2018/02/06 20:02:21
| parent author | erajasekar |
| parent permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| author | brandomoon |
| permlink | re-erajasekar-how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive-20180206t200222874z |
| title | |
| body | I enjoyed this unique, computer logic approach to productivity. Particularly the part about choosing which task is first based on the relative weight of that task divided by how long it will take! |
| json metadata | {"tags":["computer-science"],"app":"steemit/0.1"} |
| Transaction Info | Block #19641382/Trx 589eed5c2811c93fbd39cc00fff6d4e45331a116 |
View Raw JSON Data
{
"trx_id": "589eed5c2811c93fbd39cc00fff6d4e45331a116",
"block": 19641382,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:02:21",
"op": [
"comment",
{
"parent_author": "erajasekar",
"parent_permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"author": "brandomoon",
"permlink": "re-erajasekar-how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive-20180206t200222874z",
"title": "",
"body": "I enjoyed this unique, computer logic approach to productivity. Particularly the part about choosing which task is first based on the relative weight of that task divided by how long it will take!",
"json_metadata": "{\"tags\":[\"computer-science\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/02/06 20:01:33
2018/02/06 20:01:33
| voter | brandomoon |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19641366/Trx 3beb7f8fd5fcde7664aa23040508bdb5f0d86117 |
View Raw JSON Data
{
"trx_id": "3beb7f8fd5fcde7664aa23040508bdb5f0d86117",
"block": 19641366,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T20:01:33",
"op": [
"vote",
{
"voter": "brandomoon",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"weight": 10000
}
]
}erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive2018/02/06 19:59:36
erajasekarpublished a new post: how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive
2018/02/06 19:59:36
| parent author | |
| parent permlink | computer-science |
| author | erajasekar |
| permlink | how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive |
| title | How knowing computer scheduling algorithms can help us to be productive? |
| body | <html> <p>We all want to get more things done efficiently and quickly. Computers are best at it. So Let’s try to understand some computer scheduling algorithms to see how we can apply them to our daily lives to become more productive at our tasks.First things first! You don’t want to be late.</p> <h3>How to finish before the deadlines?</h3> <p>If you’re servicing customers, you would want to serve each customer as quick as possible. Assuming servicing each customer takes almost equal amount of time, then you can help them in order they arrived. The ideal commitment or due time for a customer is as soon as they walk into your door.Applying the same strategy to tasks:</p> <pre><code><em>You should start with the task due soonest and work your way toward the task due last</em></code></pre> <p>This strategy, known as <strong>Earliest Due Date.</strong> which works best for minimizing lateness. But, we have a problem if each tasks takes varying amount of time to complete.</p> <h3>How to reduce pending task list?</h3> <p>Going back to cutomer servicing example, if serving each customer takes varying amounts of time, then you would want to service most number of customers. Let’s say we can split customers by type of service and we know typical completion time for each type of service. Then, the best approach would be to pick customer who needs type of service with quickest completion time.This strategy is based on <strong>Moore’s Algorithm</strong> which says,</p> <pre><code><em>We start out just like with Earliest Due Date — by scheduling tasks as they arrive, but when deciding which task to do next, choose the quickest one and repeat this process.</em></code></pre> <p>It’s like focusing above all on reducing the length of your to-do list. Also, each piece of unfinished task could be like a carrying a mental burden. Flying through the easiest items will bring some measure of relief.It’s not suprising that this approach is compatible with the recommendation in <a href="http://amzn.to/2CFOsxe">Getting Things Done</a> Book to immediately perform any task that takes less than two minutes.This is great way to get more things done, But all work can’t be equally important.</p> <h3>How get most valuables work done?</h3> <p>Putting out an actual fire in the kitchen should probably be done before “putting out a fire” with a quick email to a client, even if the former takes a bit longer.In scheduling, this difference of importance is captured in a variable known as <code>weight</code>. When you’re going through your to-do list, this weight might feel literal — the burden you get off your shoulders by finishing each task. A task’s completion time shows how long you carry that burden, so minimizing the sum of weighted completion times (that is, each task’s duration multiplied by its weight) means minimizing your total oppression as you work through your entire agenda.The optimal strategy for this goal is a simple modification of Moore’s algorithm:</p> <pre><code><em>Divide the weight of each task by how long it will take to finish, and then work in order from the highest resulting importance-per-unit-time to the lowest.</em></code></pre> <p><em>For eg: If you’re a consultant, weight can be inferred from money you get. So simply divide each project’s fee by its size, and work your way from the hightest hourly rate to the lowest.</em>It might be hard to assign a degree of importance to each one of your tasks, but there is a quick rule of thumb:</p> <blockquote><em>Only prioritize a task that takes twice as long if it’s twice as important.</em></blockquote> <p>But if tasks are dependent on other tasks, this will bring us new problems.</p> <h3>How to get unstuck?</h3> <p>We might get stuck sometimes because an important task can’t be done until another less important task is finished. In computer science this problem is called <a href="https://en.wikipedia.org/wiki/Priority_inversion">priority inversion.</a></p> <blockquote><em><strong>Priority inversion</strong></em> <em>is a problematic scenario in scheduling in which a high priority task is indirectly preempted by a lower priority task effectively “inverting” the relative priorities of the two tasks.</em></blockquote> <p>The practical solution to this problem is <strong>Priority Inheritance</strong>. That is</p> <pre><code><em>To get unstuck is to treat the unimportant things as being as important as whatever it’s blocking.</em></code></pre> <h3>How to work through continuous incoming tasks?</h3> <p>Life could be easy, if we have finite list of tasks. In reality, it isn’t. If assignments get tossed on you at unpredictable moments. The efficient approach is to switch tasks which is known as <a href="https://en.wikipedia.org/wiki/Preemption_%28computing%29">preemption</a> in computer science.</p> <blockquote><em><strong>Preemption</strong></em> <em>is the act of temporarily interrupting a task being carried out by a computer system with the intention of resuming the task at a later time.</em></blockquote> <p>It can be used in job scheduling as</p> <pre><code><em>Each time a new piece of work comes in, divide its importance by the amount of time it will take to complete. If the figure is higher than for the task you’re currently doing, switch to the new one; otherwise stick with the current task.</em></code></pre> <p>But preemption isn’t free. It comes at the cost of context switch.</p> <h3>How Job burnout happens?</h3> <p>Every time you switch tasks, you pay a price, known in computer science as a context switch. When a computer processor shifts its attention away from a given program, there’s always a certain amount of necessary overhead. It needs to effectively bookmark its place and put aside all of its information related to that program. Then it needs to figure out which program to run next. Finally it must haul out all the relevant information for that program, find its place in the code, and get in gear. The repeated rapid context swiching would cause the performace of the computer to degrade or collapse. This phenomenon called as <a href="https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29">thrashing</a>.<em>You can think of as being like juggling a set of balls. If the juggler takes one more ball than he can handle, he doesn’t drop</em> <em><strong>that</strong></em> <em>ball; he drops</em> <em><strong>everything</strong></em><em>.</em>Thrashing is a very recognizable human state. If you’ve ever had a moment where you wanted to stop doing everything just to have the chance to write down everything you were supposed to be doing, but couldn’t spare the time, you’ve thrashed. You are accomplishing nothing at all. You feel exhausted and burned out.</p> <h3>How to reduce burden of multitasking?</h3> <p>Some tips to reduce burden of context switching.</p> <h4>Don’t keep your plates full.</h4> <p>The best strategy for getting things done might be, paradoxically, to slow down. One way to avert thrashing before it starts is to learn the art of saying NO.</p> <h4>Sometimes random order is better than perfect schedule</h4> <p>One of the biggest sources of metawork in switching contexts is the very act of choosing what to do next. So even doing tasks in the wrong order is better than doing nothing at all in thrashed state.Thinking along the same lines, the Linux core team, several years ago, replaced their scheduler with one that was less “smart” about calculating process priorities but more than made up for it by taking less time to calculate them.<em>For eg: Instead of answering the most important emails first — which requires an assessment of the whole picture that may take longer than the work itself — maybe you should just answer them in random order, or in whatever order they happen to appear on-screen.</em></p> <h4>Commit doing single task for minimum amount of time</h4> <p>Computer Operating system schedulers typically define a “period” in which every program is guaranteed to run at least a little bit, with the system giving a “slice” of that period to each program.To utilize this strategy, you should learn to balance between two principles <em><strong>responsiveness</strong></em> and <em><strong>throughput</strong></em>: how quickly you can respond to things, and how much you can get done overall.The general idea is that:</p> <pre><code><em>Stay on a single task as long as possible without decreasing your responsiveness below the minimum acceptable limit. Decide how responsive you need to be — and then, if you want to get things done, be no more responsive than that.</em></code></pre> <p>The method to achieve this is <a href="https://en.wikipedia.org/wiki/Timeboxing">Timeboxing</a> i.e allocate a a fixed time period, called a <strong>time box</strong>, to each planned activity.Another very useful technique is the <a href="https://en.wikipedia.org/wiki/Pomodoro_Technique">Pomorado</a> that uses a timer to break down work into intervals, traditionally 25 minutes in length, separated by short breaks.</p> <h4>Batch process similar tasks</h4> <p>If you find yourself doing a lot of context switching, you can also employ another idea from computer science: <a href="https://en.wikipedia.org/wiki/Interrupt_coalescing">interrupt coalescing</a>. Computers do this by waiting until some fixed interval and check everything, instead of context-switching to handle separate, uncoordinated interrupts from their various subcomponents.<em>For eg: If you have five credit card bills, don’t pay them as they arrive; take care of them all in one go when the fifth bill comes.Another example is — to avoid distraction caused by checking emails often, check it every 4 hours or so.</em>In workplace, holding office hours is a way of coalescing interruptions from co-workers. Regularly scheduled meetings are one of our best defenses against the spontaneous interruption and the unplanned context switch.</p> <h3>Summary</h3> <p>In addition to kind of scheduling problem you want to solve, you also need to choose right metric to optimize. Because the metric we pick will directly affect which scheduling approaches fare best.</p> <blockquote><em>In computer science: before you can have a plan, you must first choose a metric.</em></blockquote> <p>Here is the quick guide that summarizes when to choose each strategy based on metrics to optimize.<img src="https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md"/></p> <p><img src="https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png" width="927" height="453"/></p> <h3>Credits</h3> <p>This article is inspired from the wonderful book <a href="http://amzn.to/2F1ZyLy">Algorithms to live by</a>. If you enjoyed this article, consider reading the <a href="http://amzn.to/2F1ZyLy">book</a> which provides similar strategies for</p> <ul> <li>Optimal stopping — When to stop looking?</li> <li>Explore new things vs exploit what worked best.</li> <li>Sorting</li> <li>Caching</li> <li>Bayers’s Rule — Predicting the future.</li> <li>Overfitting — When to think less.</li> <li>Relaxation — Let it slide.</li> <li>Randomness — When to leave it to chance.</li> <li>Networking — How we connect.</li> <li>Game theory — The minds of others.</li> </ul> </html> |
| json metadata | {"tags":["computer-science","algorithms","productivity","education","teaching"],"image":["https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md","https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png"],"links":["http://amzn.to/2CFOsxe","https://en.wikipedia.org/wiki/Priority_inversion","https://en.wikipedia.org/wiki/Preemption_%28computing%29","https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29","https://en.wikipedia.org/wiki/Timeboxing","https://en.wikipedia.org/wiki/Pomodoro_Technique","https://en.wikipedia.org/wiki/Interrupt_coalescing","http://amzn.to/2F1ZyLy"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #19641327/Trx ae02f4ada58798dc57e7c4f6ef73d3a738fcb1a5 |
View Raw JSON Data
{
"trx_id": "ae02f4ada58798dc57e7c4f6ef73d3a738fcb1a5",
"block": 19641327,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T19:59:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "computer-science",
"author": "erajasekar",
"permlink": "how-knowing-computer-scheduling-algorithms-can-help-us-to-be-productive",
"title": "How knowing computer scheduling algorithms can help us to be productive?",
"body": "<html>\n<p>We all want to get more things done efficiently and quickly. Computers are best at it. So Let’s try to understand some computer scheduling algorithms to see how we can apply them to our daily lives to become more productive at our tasks.First things first! You don’t want to be late.</p>\n<h3>How to finish before the deadlines?</h3>\n<p>If you’re servicing customers, you would want to serve each customer as quick as possible. Assuming servicing each customer takes almost equal amount of time, then you can help them in order they arrived. The ideal commitment or due time for a customer is as soon as they walk into your door.Applying the same strategy to tasks:</p>\n<pre><code><em>You should start with the task due soonest and work your way toward the task due last</em></code></pre>\n<p>This strategy, known as <strong>Earliest Due Date.</strong> which works best for minimizing lateness. But, we have a problem if each tasks takes varying amount of time to complete.</p>\n<h3>How to reduce pending task list?</h3>\n<p>Going back to cutomer servicing example, if serving each customer takes varying amounts of time, then you would want to service most number of customers. Let’s say we can split customers by type of service and we know typical completion time for each type of service. Then, the best approach would be to pick customer who needs type of service with quickest completion time.This strategy is based on <strong>Moore’s Algorithm</strong> which says,</p>\n<pre><code><em>We start out just like with Earliest Due Date — by scheduling tasks as they arrive, but when deciding which task to do next, choose the quickest one and repeat this process.</em></code></pre>\n<p>It’s like focusing above all on reducing the length of your to-do list. Also, each piece of unfinished task could be like a carrying a mental burden. Flying through the easiest items will bring some measure of relief.It’s not suprising that this approach is compatible with the recommendation in <a href=\"http://amzn.to/2CFOsxe\">Getting Things Done</a> Book to immediately perform any task that takes less than two minutes.This is great way to get more things done, But all work can’t be equally important.</p>\n<h3>How get most valuables work done?</h3>\n<p>Putting out an actual fire in the kitchen should probably be done before “putting out a fire” with a quick email to a client, even if the former takes a bit longer.In scheduling, this difference of importance is captured in a variable known as <code>weight</code>. When you’re going through your to-do list, this weight might feel literal — the burden you get off your shoulders by finishing each task. A task’s completion time shows how long you carry that burden, so minimizing the sum of weighted completion times (that is, each task’s duration multiplied by its weight) means minimizing your total oppression as you work through your entire agenda.The optimal strategy for this goal is a simple modification of Moore’s algorithm:</p>\n<pre><code><em>Divide the weight of each task by how long it will take to finish, and then work in order from the highest resulting importance-per-unit-time to the lowest.</em></code></pre>\n<p><em>For eg: If you’re a consultant, weight can be inferred from money you get. So simply divide each project’s fee by its size, and work your way from the hightest hourly rate to the lowest.</em>It might be hard to assign a degree of importance to each one of your tasks, but there is a quick rule of thumb:</p>\n<blockquote><em>Only prioritize a task that takes twice as long if it’s twice as important.</em></blockquote>\n<p>But if tasks are dependent on other tasks, this will bring us new problems.</p>\n<h3>How to get unstuck?</h3>\n<p>We might get stuck sometimes because an important task can’t be done until another less important task is finished. In computer science this problem is called <a href=\"https://en.wikipedia.org/wiki/Priority_inversion\">priority inversion.</a></p>\n<blockquote><em><strong>Priority inversion</strong></em> <em>is a problematic scenario in scheduling in which a high priority task is indirectly preempted by a lower priority task effectively “inverting” the relative priorities of the two tasks.</em></blockquote>\n<p>The practical solution to this problem is <strong>Priority Inheritance</strong>. That is</p>\n<pre><code><em>To get unstuck is to treat the unimportant things as being as important as whatever it’s blocking.</em></code></pre>\n<h3>How to work through continuous incoming tasks?</h3>\n<p>Life could be easy, if we have finite list of tasks. In reality, it isn’t. If assignments get tossed on you at unpredictable moments. The efficient approach is to switch tasks which is known as <a href=\"https://en.wikipedia.org/wiki/Preemption_%28computing%29\">preemption</a> in computer science.</p>\n<blockquote><em><strong>Preemption</strong></em> <em>is the act of temporarily interrupting a task being carried out by a computer system with the intention of resuming the task at a later time.</em></blockquote>\n<p>It can be used in job scheduling as</p>\n<pre><code><em>Each time a new piece of work comes in, divide its importance by the amount of time it will take to complete. If the figure is higher than for the task you’re currently doing, switch to the new one; otherwise stick with the current task.</em></code></pre>\n<p>But preemption isn’t free. It comes at the cost of context switch.</p>\n<h3>How Job burnout happens?</h3>\n<p>Every time you switch tasks, you pay a price, known in computer science as a context switch. When a computer processor shifts its attention away from a given program, there’s always a certain amount of necessary overhead. It needs to effectively bookmark its place and put aside all of its information related to that program. Then it needs to figure out which program to run next. Finally it must haul out all the relevant information for that program, find its place in the code, and get in gear. The repeated rapid context swiching would cause the performace of the computer to degrade or collapse. This phenomenon called as <a href=\"https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29\">thrashing</a>.<em>You can think of as being like juggling a set of balls. If the juggler takes one more ball than he can handle, he doesn’t drop</em> <em><strong>that</strong></em> <em>ball; he drops</em> <em><strong>everything</strong></em><em>.</em>Thrashing is a very recognizable human state. If you’ve ever had a moment where you wanted to stop doing everything just to have the chance to write down everything you were supposed to be doing, but couldn’t spare the time, you’ve thrashed. You are accomplishing nothing at all. You feel exhausted and burned out.</p>\n<h3>How to reduce burden of multitasking?</h3>\n<p>Some tips to reduce burden of context switching.</p>\n<h4>Don’t keep your plates full.</h4>\n<p>The best strategy for getting things done might be, paradoxically, to slow down. One way to avert thrashing before it starts is to learn the art of saying NO.</p>\n<h4>Sometimes random order is better than perfect schedule</h4>\n<p>One of the biggest sources of metawork in switching contexts is the very act of choosing what to do next. So even doing tasks in the wrong order is better than doing nothing at all in thrashed state.Thinking along the same lines, the Linux core team, several years ago, replaced their scheduler with one that was less “smart” about calculating process priorities but more than made up for it by taking less time to calculate them.<em>For eg: Instead of answering the most important emails first — which requires an assessment of the whole picture that may take longer than the work itself — maybe you should just answer them in random order, or in whatever order they happen to appear on-screen.</em></p>\n<h4>Commit doing single task for minimum amount of time</h4>\n<p>Computer Operating system schedulers typically define a “period” in which every program is guaranteed to run at least a little bit, with the system giving a “slice” of that period to each program.To utilize this strategy, you should learn to balance between two principles <em><strong>responsiveness</strong></em> and <em><strong>throughput</strong></em>: how quickly you can respond to things, and how much you can get done overall.The general idea is that:</p>\n<pre><code><em>Stay on a single task as long as possible without decreasing your responsiveness below the minimum acceptable limit. Decide how responsive you need to be — and then, if you want to get things done, be no more responsive than that.</em></code></pre>\n<p>The method to achieve this is <a href=\"https://en.wikipedia.org/wiki/Timeboxing\">Timeboxing</a> i.e allocate a a fixed time period, called a <strong>time box</strong>, to each planned activity.Another very useful technique is the <a href=\"https://en.wikipedia.org/wiki/Pomodoro_Technique\">Pomorado</a> that uses a timer to break down work into intervals, traditionally 25 minutes in length, separated by short breaks.</p>\n<h4>Batch process similar tasks</h4>\n<p>If you find yourself doing a lot of context switching, you can also employ another idea from computer science: <a href=\"https://en.wikipedia.org/wiki/Interrupt_coalescing\">interrupt coalescing</a>. Computers do this by waiting until some fixed interval and check everything, instead of context-switching to handle separate, uncoordinated interrupts from their various subcomponents.<em>For eg: If you have five credit card bills, don’t pay them as they arrive; take care of them all in one go when the fifth bill comes.Another example is — to avoid distraction caused by checking emails often, check it every 4 hours or so.</em>In workplace, holding office hours is a way of coalescing interruptions from co-workers. Regularly scheduled meetings are one of our best defenses against the spontaneous interruption and the unplanned context switch.</p>\n<h3>Summary</h3>\n<p>In addition to kind of scheduling problem you want to solve, you also need to choose right metric to optimize. Because the metric we pick will directly affect which scheduling approaches fare best.</p>\n<blockquote><em>In computer science: before you can have a plan, you must first choose a metric.</em></blockquote>\n<p>Here is the quick guide that summarizes when to choose each strategy based on metrics to optimize.<img src=\"https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md\"/></p>\n<p><img src=\"https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png\" width=\"927\" height=\"453\"/></p>\n<h3>Credits</h3>\n<p>This article is inspired from the wonderful book <a href=\"http://amzn.to/2F1ZyLy\">Algorithms to live by</a>. If you enjoyed this article, consider reading the <a href=\"http://amzn.to/2F1ZyLy\">book</a> which provides similar strategies for</p>\n<ul>\n <li>Optimal stopping — When to stop looking?</li>\n <li>Explore new things vs exploit what worked best.</li>\n <li>Sorting</li>\n <li>Caching</li>\n <li>Bayers’s Rule — Predicting the future.</li>\n <li>Overfitting — When to think less.</li>\n <li>Relaxation — Let it slide.</li>\n <li>Randomness — When to leave it to chance.</li>\n <li>Networking — How we connect.</li>\n <li>Game theory — The minds of others.</li>\n</ul>\n</html>",
"json_metadata": "{\"tags\":[\"computer-science\",\"algorithms\",\"productivity\",\"education\",\"teaching\"],\"image\":[\"https://gist.github.com/erajasekar/59ec56ce2c8f29a4a4e59bd6f4d5570b#file-scheduling-strategies-md\",\"https://raw.githubusercontent.com/erajasekar/blog-jekyll/master/assets/images/knowing-algorithms/summary.png\"],\"links\":[\"http://amzn.to/2CFOsxe\",\"https://en.wikipedia.org/wiki/Priority_inversion\",\"https://en.wikipedia.org/wiki/Preemption_%28computing%29\",\"https://en.wikipedia.org/wiki/Thrashing_%28computer_science%29\",\"https://en.wikipedia.org/wiki/Timeboxing\",\"https://en.wikipedia.org/wiki/Pomodoro_Technique\",\"https://en.wikipedia.org/wiki/Interrupt_coalescing\",\"http://amzn.to/2F1ZyLy\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}erajasekarupdated their account properties2018/02/06 19:54:00
erajasekarupdated their account properties
2018/02/06 19:54:00
| account | erajasekar |
| memo key | STM8Umi4BoGz6xqLshcLrwYhhA2gY6nowKUyQvdPLEDytsFcseHDT |
| json metadata | {"profile":{"profile_image":"http://erajasekar.com/assets/images/profile_small.jpg","name":"Raja","about":"Software Engineer","location":"Tampa, FL, USA","website":"https://erajasekar.com"}} |
| Transaction Info | Block #19641215/Trx 7e7c4395c4e227484eb3ca67b8b2297253c1d630 |
View Raw JSON Data
{
"trx_id": "7e7c4395c4e227484eb3ca67b8b2297253c1d630",
"block": 19641215,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T19:54:00",
"op": [
"account_update",
{
"account": "erajasekar",
"memo_key": "STM8Umi4BoGz6xqLshcLrwYhhA2gY6nowKUyQvdPLEDytsFcseHDT",
"json_metadata": "{\"profile\":{\"profile_image\":\"http://erajasekar.com/assets/images/profile_small.jpg\",\"name\":\"Raja\",\"about\":\"Software Engineer\",\"location\":\"Tampa, FL, USA\",\"website\":\"https://erajasekar.com\"}}"
}
]
}steemcreated a new account: @erajasekar2018/02/06 19:39:54
steemcreated a new account: @erajasekar
2018/02/06 19:39:54
| fee | 0.500 STEEM |
| delegation | 29700.000000 VESTS |
| creator | steem |
| new account name | erajasekar |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5mgbdwz54PYeoVhZ3X1ZCu9oK7MU2AJDXHX5Pd1RDnZ9LsuykQ",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM8VLCD3NZ7moW2KGtRRMwGPN56eJs3tstxGWFfPzaxyJHQL3Dbv",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM8JizWoFKaeb6hYJDbfrtgngr7o1a5ntsZtf4jkkakDyrchjA7M",1]]} |
| memo key | STM8Umi4BoGz6xqLshcLrwYhhA2gY6nowKUyQvdPLEDytsFcseHDT |
| json metadata | |
| extensions | [] |
| Transaction Info | Block #19640933/Trx a7d371ca1811e6114954e8c7dc4293b0cc4a7e35 |
View Raw JSON Data
{
"trx_id": "a7d371ca1811e6114954e8c7dc4293b0cc4a7e35",
"block": 19640933,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-06T19:39:54",
"op": [
"account_create_with_delegation",
{
"fee": "0.500 STEEM",
"delegation": "29700.000000 VESTS",
"creator": "steem",
"new_account_name": "erajasekar",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5mgbdwz54PYeoVhZ3X1ZCu9oK7MU2AJDXHX5Pd1RDnZ9LsuykQ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8VLCD3NZ7moW2KGtRRMwGPN56eJs3tstxGWFfPzaxyJHQL3Dbv",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8JizWoFKaeb6hYJDbfrtgngr7o1a5ntsZtf4jkkakDyrchjA7M",
1
]
]
},
"memo_key": "STM8Umi4BoGz6xqLshcLrwYhhA2gY6nowKUyQvdPLEDytsFcseHDT",
"json_metadata": "",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress75.62%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779062511
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779062511
},
"rc_account": {
"account": "erajasekar",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779062511
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"http://erajasekar.com/assets/images/profile_small.jpg","name":"Raja","about":"Software Engineer","location":"Tampa, FL, USA","website":"https://erajasekar.com"} |
| JSON METADATA | |
| profile | {"profile_image":"http://erajasekar.com/assets/images/profile_small.jpg","name":"Raja","about":"Software Engineer","location":"Tampa, FL, USA","website":"https://erajasekar.com"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "http://erajasekar.com/assets/images/profile_small.jpg",
"name": "Raja",
"about": "Software Engineer",
"location": "Tampa, FL, USA",
"website": "https://erajasekar.com"
}
},
"json_metadata": {
"profile": {
"profile_image": "http://erajasekar.com/assets/images/profile_small.jpg",
"name": "Raja",
"about": "Software Engineer",
"location": "Tampa, FL, USA",
"website": "https://erajasekar.com"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM5mgbdwz54PYeoVhZ3X1ZCu9oK7MU2AJDXHX5Pd1RDnZ9LsuykQ1/1
Active
Single Signature
Public Keys
STM8VLCD3NZ7moW2KGtRRMwGPN56eJs3tstxGWFfPzaxyJHQL3Dbv1/1
Posting
Single Signature
Public Keys
STM8JizWoFKaeb6hYJDbfrtgngr7o1a5ntsZtf4jkkakDyrchjA7M1/1
Memo
STM8Umi4BoGz6xqLshcLrwYhhA2gY6nowKUyQvdPLEDytsFcseHDT
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5mgbdwz54PYeoVhZ3X1ZCu9oK7MU2AJDXHX5Pd1RDnZ9LsuykQ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8VLCD3NZ7moW2KGtRRMwGPN56eJs3tstxGWFfPzaxyJHQL3Dbv",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8JizWoFKaeb6hYJDbfrtgngr7o1a5ntsZtf4jkkakDyrchjA7M",
1
]
]
},
"memo": "STM8Umi4BoGz6xqLshcLrwYhhA2gY6nowKUyQvdPLEDytsFcseHDT"
}Witness Votes
0 / 30
No active witness votes.
[]