{"id":70,"date":"2026-10-12T16:40:00","date_gmt":"2026-10-12T16:40:00","guid":{"rendered":"https:\/\/www.masters-tool.com\/blog\/?p=70"},"modified":"2026-10-08T03:04:42","modified_gmt":"2026-10-08T03:04:42","slug":"keeping-a-personal-shortlist-of-tools","status":"publish","type":"post","link":"https:\/\/www.masters-tool.com\/blog\/keeping-a-personal-shortlist-of-tools\/","title":{"rendered":"Keeping a Personal Shortlist of Tools"},"content":{"rendered":"

TL;DR:<\/strong> Keep a personal shortlist of about eight Masters Tool pages you can explain from memory. Each line needs the job, the input the page requires, and one limitation. Everything else stays on the homepage until it earns a line.<\/p>\n

A shortlist is not a second copy of the hub<\/h2>\n

The homepage already organizes reference tables, code tools, color, encoding, passwords, webmaster helpers, calculators, unit conversion, and health lookups. Copying that entire map into a note does not make you faster. It gives you two maps to maintain. A shortlist is the set of pages you can reopen without rereading the menu because the jobs are genuinely yours. For most people that set is smaller than ten. If your list passes fifteen, it has become a junk drawer and you will browse it the same way you browse the site, only with worse labels.<\/p>\n

Write the list where you will actually see it: a pinned note, a small bookmark folder, or the top of a work log. A list inside a folder you never open is a wish. Review it when a project ends and again when a new role starts. The pages a student needs and the pages a maintainer needs are not the same eight.<\/p>\n

What each line must say<\/h2>\n

A line that only names the tool is a bookmark with extra steps. Use three parts. The job, in your words: \u201cescape a string for HTML.\u201d The required input: \u201cplain text, not a whole document with a head.\u201d The limitation you have already hit: \u201cdoes not fetch a URL\u201d or \u201ccomma decimals are not accepted\u201d or \u201cone image at a time.\u201d Those three parts are why the list saves time. They stop you opening a page, discovering the limitation again, and feeling that the site changed.<\/p>\n

Add the date you last used it if the list lives in a note. A line untouched for six months is a candidate to remove. You can always find the page from the homepage later. Removal is not a loss of access. It is a refusal to pretend you remember a tool you do not use.<\/p>\n

How a page earns a line<\/h2>\n
    \n
  1. You used it on real work<\/strong> at least twice, not once during a tour.<\/li>\n
  2. You can say the limitation<\/strong> without opening the page.<\/li>\n
  3. The job is still yours.<\/strong> A class that ended does not get a permanent row.<\/li>\n
  4. You know a sample<\/strong> that should succeed, so a future failure is informative.<\/li>\n<\/ol>\n

    Pages fail this test when they were interesting rather than useful. A polynomial fitter, a hash demo, or a health index might be worth knowing and still not worth a slot. Leave them on the Masters Tool homepage<\/a>. Curiosity is served by the map. The shortlist is served by repetition.<\/p>\n

    Group the eight by the week, not by the site\u2019s menu<\/h2>\n

    You do not need one tool from each menu. You might need three encoders and no health lookup, or two unit pages and a MIME table. Group your lines by the situation that triggers them: \u201cbefore I paste into HTML,\u201d \u201cwhen a file\u2019s characters look wrong,\u201d \u201cwhen a ticket asks for a hex color.\u201d Situation labels beat category labels copied from the site, because you approach the list with a situation, not with a taxonomy.<\/p>\n

    Keep a single line that points at the homepage for everything else, explicitly: \u201cUnlisted jobs: start at the hub, do not guess a cousin.\u201d That line is what prevents the shortlist from making you narrow-minded. The list is a cache. The hub is the source. Caches that ignore the source become wrong.<\/p>\n

    Sharing a shortlist<\/h2>\n

    A team can share a shortlist if the lines include limitations and owners. \u201cWe use this entity encoder for the marketing site\u201d is actionable. \u201cUseful tools!!!\u201d with twelve links is not. Do not paste internal samples into the shared list. The list holds how to get to the tool, not last week\u2019s customer string. If a tool\u2019s default is easy to misuse, the limitation clause is the part you insist on. New people will skip the page instructions. They will not skip a one-line warning sitting in the team note, if you put it in the same sentence as the link.<\/p>\n

    Revisit the shared list when the site\u2019s page changes or when the consumer of the output changes. A shortlist that encodes last year\u2019s CSS convention will keep producing last year\u2019s prefix. Someone should own the review. A list without an owner decays into folklore.<\/p>\n

    Build it this week, not in theory<\/h2>\n

    Look at your history for the hub. Write down the pages you actually returned to. Add the input and the limitation while you still remember the last mistake. Stop at eight even if you feel the itch to add a ninth \u201cjust in case.\u201d The ninth can live on the homepage until it has earned its place the same way.<\/p>\n

    When a job is not on the list, open the Masters Tool<\/a> home view and choose by the verb, the way you did before the list existed. The shortlist is an accelerator for familiar work. It is not a replacement for reading the page you have never used.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Eight lines, each with the job, the required input, and a limitation. Leave everything else on the homepage.<\/p>\n","protected":false},"author":1,"featured_media":39,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-70","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tool-tutorials","entry","has-media"],"_links":{"self":[{"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/posts\/70","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/comments?post=70"}],"version-history":[{"count":1,"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/posts\/70\/revisions"}],"predecessor-version":[{"id":71,"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/posts\/70\/revisions\/71"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/media\/39"}],"wp:attachment":[{"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/media?parent=70"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/categories?post=70"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.masters-tool.com\/blog\/wp-json\/wp\/v2\/tags?post=70"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}