{"id":1976,"date":"2026-11-12T09:50:00","date_gmt":"2026-11-12T09:50:00","guid":{"rendered":"https:\/\/devopsschool.org\/blog\/?p=1976"},"modified":"2026-11-12T09:50:00","modified_gmt":"2026-11-12T09:50:00","slug":"nisha-study-plan-ignore","status":"publish","type":"post","link":"https:\/\/devopsschool.org\/blog\/nisha-study-plan-ignore\/","title":{"rendered":"Nisha&#8217;s Study Plan: The Page of Things She Chose Not to Learn"},"content":{"rendered":"<p>Nisha started her DevOps study plan on a Sunday night with eleven browser tabs open. A pipeline tutorial, two certification syllabi, a conference playlist, a thread arguing about the best container runtime, a newsletter archive and four video courses she had promised herself she would finish. By Wednesday she had completed nothing, and by Friday she had started wondering whether she was cut out for the field. What changed her course was not a new course. It was a page of things she decided not to do.<\/p>\n<p>Her story, told here as a composite sketch of how many learners behave, is a useful lens on a simple point: in training, attention is the scarce resource, and a page of refusals written down in advance shields the few activities that actually build skill.<\/p>\n<h2>Week one: the add-everything plan<\/h2>\n<p>Nisha&#8217;s instinct was to treat every resource as a debt. If a mentor mentioned a tool, she added it. If a classmate shared a link, she opened it. Her study schedule grew to cover more hours than the week contained, and she began switching between topics every twenty minutes. Each switch cost her a little of the momentum she had built, and when Friday came she could recite slogans from five areas but could not build anything in any of them.<\/p>\n<p>Many learners recognise this pattern. A bigger syllabus feels like a bigger commitment, and a bigger commitment feels like progress. It is neither. It is mostly a larger surface for feeling behind.<\/p>\n<h2>The conversation that changed the plan<\/h2>\n<p>A senior colleague at a part-time job asked Nisha what she had built that month. She listed courses she had started. He asked again: built, not watched. She had no answer. He suggested a small experiment. On a single sheet of paper, write what you will build this month, and under it, in a separate column, write the things you will not touch until it is done.<\/p>\n<p>Her first draft of the second column was timid. It said &#8220;less social media&#8221;. He told her to rewrite it so a stranger could check it. The second draft was sharper.<\/p>\n<h2>What went on the not-this-month page<\/h2>\n<ol>\n<li>No new certification syllabus until the first practical project is running.<\/li>\n<li>No more than one video course at a time, and none longer than she can finish in the month.<\/li>\n<li>No debate threads about which tool is &#8220;best&#8221;.<\/li>\n<li>No newsletters, except one she actually reads end to end.<\/li>\n<li>No reworking the notes she already had into prettier notes.<\/li>\n<\/ol>\n<p>The fifth item surprised her most. She had been spending evenings decorating notebooks, which felt like study and produced nothing she could run.<\/p>\n<h2>Week two: the narrow plan<\/h2>\n<p>With the list in place, Nisha chose one project: a small application, a repeatable build, and an automated deployment to a test environment. She ignored almost everything else. When she hit a problem, she searched for the specific error rather than wandering through general material. Within another seven days she had a working pipeline, imperfect but hers.<\/p>\n<p>Her instructor noticed the change in her questions. Instead of &#8220;what should I learn next&#8221;, she asked &#8220;why did this step fail&#8221;, which is the kind of question that leads to understanding. Guidance such as the article on <a href=\"https:\/\/devopsschool.org\/blog\/building-a-beginner-devops-portfolio-practical-projects-github-structure-and-roadmap\/\">assembling a first portfolio of practical projects<\/a> matched what she was now doing by instinct: a few finished pieces beat many abandoned ones.<\/p>\n<h2>The temptation to restart the pile<\/h2>\n<p>In the third week a classmate announced she was adding a second cloud platform to her plan. Nisha felt the old pull. She looked at her page, saw that the project was not yet finished, and wrote the platform name in a small &#8220;revisit&#8221; box at the bottom. This is the quiet function of the list: it turns a tempting new idea into an item with a date, not an immediate obligation.<\/p>\n<p>She also revisited what certifications meant for her goals. Reading the discussion about <a href=\"https:\/\/devopsschool.org\/blog\/the-real-value-of-devops-certifications-in-modern-tech-careers\/\">what credentials do and do not do for a technology career<\/a> helped her plan one credential for later, tied to her project, rather than collecting several at once.<\/p>\n<h2>Filling the right gaps<\/h2>\n<p>An ignore list does not mean ignoring weaknesses. Nisha kept a separate short list of gaps she knew she had to close, such as basic networking and the command line. She chose them using material like <a href=\"https:\/\/devopsschool.org\/blog\/devops-knowledge-gaps-students-must-fill-a-practical-guide\/\">a practical rundown of the knowledge holes students need to close<\/a>, then scheduled them into the project instead of studying them in isolation. The ignore list protected time; the gap list directed it.<\/p>\n<h2>A note on shopping for gear<\/h2>\n<p>When her old laptop began to struggle, Nisha spent a long evening comparing models. She finally limited herself to a single starting point, <a href=\"https:\/\/www.truereviewnow.com\/\">True Review Now<\/a>, a blog of product and service reviews that classmates mentioned for devices, apps and nearby providers, and capped herself at an hour. The decision took one evening, not a week.<\/p>\n<h2>Month&#8217;s end<\/h2>\n<p>When the month closed, Nisha had a running pipeline, a short write-up of what she had learned and a list of next month&#8217;s priorities, written after a review of what she had ignored. Two items from the ignore list moved onto the new plan, because her project had made them relevant. Three stayed off. She felt something she had not felt on that first Sunday: control over her own attention.<\/p>\n<h2>What other learners can take from it<\/h2>\n<ul>\n<li>Write what you will build before you write what you will study.<\/li>\n<li>Make the ignore list specific enough that a stranger could check it.<\/li>\n<li>Park tempting ideas in a revisit box with a date.<\/li>\n<li>Keep a separate short list of real gaps and fold them into your project.<\/li>\n<li>Review the list monthly and promote items on purpose.<\/li>\n<\/ul>\n<p>Learning DevOps is a long road, and no one finishes it by opening more tabs. Nisha&#8217;s progress came from a page that said no, calmly and in writing, to nearly everything that was not the next useful step.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A narrative sketch of a DevOps learner who stopped adding tabs and courses and wrote down what she would not touch, turning scattered study into finished projects.<\/p>\n","protected":false},"author":5,"featured_media":1977,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[486],"tags":[],"class_list":["post-1976","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/1976","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/comments?post=1976"}],"version-history":[{"count":1,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/1976\/revisions"}],"predecessor-version":[{"id":2089,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/1976\/revisions\/2089"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media\/1977"}],"wp:attachment":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media?parent=1976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/categories?post=1976"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/tags?post=1976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}