<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Meer Hashaam khan on Medium]]></title>
        <description><![CDATA[Stories by Meer Hashaam khan on Medium]]></description>
        <link>https://medium.com/@hashaamkhan975?source=rss-533c3fc324bc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oPsd7X_Gks37C4Eeuw6TCw@2x.jpeg</url>
            <title>Stories by Meer Hashaam khan on Medium</title>
            <link>https://medium.com/@hashaamkhan975?source=rss-533c3fc324bc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:02:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hashaamkhan975/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Unforgivable Betrayal: Mohsin Naqvi’s Two-Year Reign of Shame, Stagnation and Total Failure]]></title>
            <link>https://medium.com/@hashaamkhan975/the-unforgivable-betrayal-mohsin-naqvis-two-year-reign-of-shame-stagnation-and-total-failure-6d429d3b6266?source=rss-533c3fc324bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d429d3b6266</guid>
            <category><![CDATA[pakistan-cricket]]></category>
            <category><![CDATA[pakistan-cricket-board]]></category>
            <category><![CDATA[pcb-chairman-mohsin-naqvi]]></category>
            <dc:creator><![CDATA[Meer Hashaam khan]]></dc:creator>
            <pubDate>Sat, 28 Feb 2026 23:12:34 GMT</pubDate>
            <atom:updated>2026-02-28T23:12:34.128Z</atom:updated>
            <content:encoded><![CDATA[<p>I am writing this with burning rage and absolute disappointment as a Pakistani who loves this game more than anything. On 22 January 2024, caretaker Prime Minister Anwaar-ul-Haq Kakar appointed Mohsin Raza Naqvi to the PCB governing board. Just two weeks later, on 6 February 2024, he was elected unopposed as the 37th Chairman. In his acceptance speech he said:<strong> “I am deeply honoured and humbled to have been unanimously elected as Chairman of the Pakistan Cricket Board. I am fully committed to upgrading the standard of the game in the country and bringing professionalism in the administration of cricket in Pakistan.”</strong> Since that day, Pakistan cricket has suffered two years of catastrophic stagnation, zero accountability, and national humiliation. Four tournaments. Four shameful exits. And the man responsible? Still sitting on his throne like nothing happened.</p><p>This is not leadership. This is a disgraceful protection racket at the highest level of Pakistani cricket.</p><p><strong>Part 1: The Brutal Contrast — Accountability Died on 22 January 2024</strong></p><p>Before Naqvi, failure had consequences. Look at the actual record. Ijaz Butt took charge in August 2008 and in 2009 Pakistan won the T20 World Cup at Lord’s, beating South Africa in the semis and Sri Lanka in the final. A genuine high point. But results dipped, pressure built, and by October 2011 Ijaz Butt was gone. Zaka Ashraf came in and under his tenure Pakistan won the Asia Cup in 2012. But then came the match-fixing investigations, the IHC suspended him in May 2013, Najam Sethi stepped in briefly, Zaka Ashraf was reinstated by court order in January 2014 and then removed again within weeks. Najam Sethi back again by February 2014 but only until May 2014. The system was turbulent but it was still moving. Shaharyar Khan then took over in May 2014 and held the role all the way to August 2017, the longest stable tenure in this period. Under his watch Pakistan climbed to number one in Test cricket in 2016. Then Najam Sethi returned in August 2017 and in that exact window Pakistan won the 2017 Champions Trophy, beating India by 180 runs in the final. When that cycle ended Ehsan Mani came in August 2018 and served until August 2021. Then Ramiz Raja took charge in September 2021 and Pakistan beat India in a T20 World Cup for the first time ever, reached the semi-finals in 2021, and made the final in 2022 coming within touching distance of the title. Ramiz was removed in December 2022 after a disappointing Asia Cup and T20 World Cup exit. Najam Sethi returned briefly, then Zaka Ashraf took the management committee role from July 2023 until January 2024. Twelve changes across roughly fifteen years. Every single one of them triggered by results or controversy. The system demanded accountability and kept enforcing it. Then on 22 January 2024 Mohsin Naqvi arrived and the era of consequences died.</p><p>2024 T20 World Cup: Group stage disaster. Lost to co-hosts USA in a Super Over and then beaten by India by six runs in New York. Pakistan eliminated before the Super 8. After this humiliation, Naqvi himself told reporters: <strong>“It seemed that a minor surgery would work but after this bad performance, I am now sure that a major surgery is required. The nation will soon see a major overhaul.”</strong> That overhaul never came.</p><p>2025 Champions Trophy hosted in Pakistan: Pakistan, as both hosts and defending champions, were eliminated in the group stage. India went on to win the title. Pakistan were knocked out without any fight in front of their own crowds.</p><p>2025 Asia Cup: Pakistan reached the final but were beaten by India in all three of their encounters including the group stage, Super Fours, and the final in Dubai where India chased 147 with five wickets in hand. The post-match ceremony became a global embarrassment when the Indian team refused to accept the winners’ trophy from Naqvi, who by that point was also serving as ACC President.</p><p>2026 T20 World Cup: Pakistan qualified for the Super 8 but failed to reach the semi-finals. They suffered a rain washout against New Zealand, lost to England by two wickets after Harry Brook’s century, and then beat Sri Lanka by five runs in their final game. But they needed to restrict Sri Lanka to 147 or fewer to qualify on net run rate. Sri Lanka recovered from 94 for 4 to post 207 for 6 and Pakistan were knocked out. Captain Salman Agha said after the exit: <strong>“It could have been a different story had we won the toss. Dew was a factor. We couldn’t execute plans.” </strong>Another tournament. Another exit. Another excuse.</p><p>Four tournaments. Not a single semi-final or final reached. And let me be absolutely clear about something. This is not about one bad toss. This is not about a dropped catch in the deep or a wide at the death. This is not about Babar’s form or Rizwan’s strike rate or Shaheen’s fitness or a selection committee picking the wrong eleven. Those are symptoms. The disease runs much deeper. This is a total system failure. A failure of cricket culture, of long-term planning, of domestic structure, of player development pathways, of coaching philosophy, of data and analytics, of everything that sits beneath the visible surface of a cricket team. When your system is broken, it does not matter who you pick, who you captain or who you coach. You will keep losing in the same ways, in the same moments, against the same opponents. And the man responsible for that system, the man who controls it, who appoints people into it, who promised to fix it and then admitted it was a mess, who has sat at the top of it for two full years without a single ICC knockout-stage appearance to show for it, is Mohsin Raza Naqvi. Not the players. Not the captain. Not the selectors. The system. And the system starts at the top.</p><p><strong>Part 2: “Player Development” — The Most Vicious Lie Ever Told</strong></p><p>Naqvi keeps bragging about giving chances to new talent. Since January 2024, Pakistan have handed out a staggering number of T20I debuts including Abbas Afridi, Zaman Khan, Sufyan Muqeem, Faisal Akram, Kamran Ghulam, Omair Yousuf, Usama Mir and dozens more. Where are they today? Nowhere. Zaman Khan vanished into domestic cricket. Sufyan Muqeem dropped. Faisal Akram back to PSL auctions. Abbas Afridi ignored for the 2026 World Cup.</p><p>And after months of promising a new era, Naqvi himself admitted in late 2024: <strong>“The problem is the selection committee has no pool to turn to from which to select players. The whole system was a mess.” </strong>So which is it? Are you developing talent or have you inherited a mess you cannot fix? You cannot claim credit for debuts while admitting you have no player pool. That is not development. That is criminal recycling with a fresh coat of paint.</p><p>Instead the same tired faces keep returning: Babar Azam, Shadab Khan, Shaheen Shah Afridi, Mohammad Rizwan, and Haris Rauf. You debut player after player and still go back to the same six from 2019 to 2022. The system has zero plan, zero vision and zero courage to drop the sacred cows.</p><p><strong>Part 3: The Captaincy Catastrophe That Destroyed Team Spirit Forever</strong></p><p>Naqvi’s very first major crime was reinstating Babar Azam as captain and stripping the leadership from Shaheen Shah Afridi who had been appointed before Naqvi arrived. With that one decision he did not just change a captain, he split Pakistani cricket straight down the middle. Two groups formed overnight in the dressing room, two raging fanbases on social media, two opposing camps on every cricket channel from Geo Super to ARY Sports with former players forced to pick a side every single night. Babar supporters against Shaheen supporters, drawing room arguments, Twitter wars, primetime debates, all of it traceable back to one man’s decision on day one. Team spirit was not just damaged. It was deliberately detonated.</p><p>And if you want to talk about what this circus did to Babar Azam specifically, that is a tragedy of its own. Here was a man who owned ODI cricket. A classically correct batsman, one of the cleanest timers of a cricket ball this country has ever produced, a player who had reached number one in ODIs and built his entire identity around that format. The sensible, obvious decision was simple. Remove him from T20 cricket where his style was always a misfit and let him own the ODI and Test arena. That was the surgery that was needed. Instead what did Naqvi do? Dragged him back into T20 captaincy, threw him into the middle of a political dressing room, made him the face of every failure, and then discarded him. Three years of that environment and Babar is a diminished player across all three formats. His technique has changed, his confidence has changed, his numbers have changed. A generational ODI batsman who should have been protected and built around has been chewed up and spat out by mismanagement. Naqvi did not just fail the team. He finished a player.</p><p>Then the circus began. Babar removed after the 2024 failure. Rizwan tried and failed. Salman Agha made T20I captain in 2025 with big promises of fearless cricket. And now after the 2026 World Cup humiliation, even Salman is under fire. Four captains in less than three years. No stability. No culture. Just endless experiments on a broken team. This single decision alone deserves Naqvi’s immediate removal.</p><p><strong>Part 4: The Era of Headlines — When the Team Failed, a New Stunt Was Always Ready</strong></p><p>This is the pattern. Study it carefully. Every time Pakistan were humiliated on the field, a brand new headline appeared within days to change the conversation. Team crashes out of the 2024 T20 World Cup? Do not worry, here is a grand announcement about renovating Gaddafi Stadium in 117 days. Team loses to Bangladesh at home for the first time in history? Here is a flashy jersey reveal on the ground with lights and cameras. Pakistan embarrassed at the 2025 Champions Trophy as hosts? Here is Naqvi accepting the ACC Presidency. Team knocked out of the 2025 Asia Cup final after losing to India three times in one tournament? Here comes the India drama. Will we play them? Will we not? Boycott on the table. Statements flying. Naqvi taking a hard public stance. And then the 2026 T20 World Cup arrives and Pakistan stick to their word and do not play India. A decision was made and it was kept. But even that became more about the political noise surrounding it than about fixing the actual cricket. The headlines around that one decision consumed more airtime than two years of cricket planning ever did.</p><p>Stadiums do not score runs. Jersey launches do not take wickets. ACC titles do not win World Cups. What Naqvi mastered was not cricket management. It was the art of making sure there was always something shinier to look at whenever the team failed. Two years of stunts. Two years of headlines. Two years of nothing real. And the cricket burned quietly underneath all of it.</p><p><strong>Part 5: Why Is the Man at the Top Never Questioned? The Political Shield That Protects Him</strong>.</p><p>After every single tournament the blame game is identical. Players are slaughtered for their form, their bowling or batting, their fielding. The coach is attacked. The captaincy is ripped apart. The selection committee is destroyed. Everyone below him burns. But the one constant failure sitting at the very top for two full years? Never touched. Not once. Four disasters. Zero consequences.</p><p>We can bash the batsman for not scoring. We can bash the bowler for leaking runs in the death overs. We can bash the fielder for dropping that catch. We can bash the coach for his tactics and his press conferences. We can bash the selectors for picking the wrong eleven and dropping the right one. We do all of this every single tournament without fail and nobody stops us. It is practically a national sport at this point. But the moment someone points a finger at Mohsin Naqvi, suddenly it becomes too political, too sensitive, too complicated. Suddenly we need more context and more time and more patience. Why? Give me one reason why the batsman who scores 14 runs deserves more scrutiny than the man who has presided over four consecutive ICC exits. Give me one reason why the selector who drops a player answers to the public but the chairman who built the entire broken selection system answers to nobody. You cannot have it both ways. Either everyone is accountable or nobody is.</p><p>And the reason nobody touches him is not complicated. It is just something nobody on television will say out loud. Mohsin Raza Naqvi is not a career cricket administrator. He is a media entrepreneur who founded City Media Group, a former caretaker Chief Minister of Punjab, and the sitting Federal Interior Minister. His position is backed by powerful establishment connections and a senior political figure reportedly described him as Rawalpindi’s man rather than the candidate of any single party. Cricket merit means nothing if you have the right people behind you. Is establishment affiliation now the criteria for running this board? Because by any cricket measure this man should have been gone after the first tournament. His continued tenure at PCB, despite calls for resignation from both the National Assembly and Senate after Pakistan’s cricket disasters, reflects how deeply political patronage has penetrated our game. Previous chairmen were removed for far less. Naqvi survives because cricket has been hijacked by politics and the fans are paying the price. The fact that he is still here tells you everything about who is really in charge of Pakistani cricket and it is not the fans, not the players, and not the game itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nk268AtvVLXsom3fedc7HA.png" /></figure><p><strong>Final Verdict: This Is Treason Against Pakistani Cricket</strong></p><p>Two years since 22 January 2024. Two years of broken promises, recycled failures, empty stunts and zero accountability. Two years of the darkest, most shameful period in our cricket history. Mohsin Raza Naqvi has not just failed Pakistan cricket, he has betrayed every single person who bleeds green. He stood at that podium and promised major surgery. He got four chances to prove it and delivered nothing. He admitted the system is a mess and then went and collected another title while the mess grew worse. He renovated stadiums for selfies while the team was being humiliated on the world stage. He turned the PCB chairmanship, the ACC presidency and the Interior Ministry into one big personal portfolio while our cricket was reduced to a global joke. Pakistan does not need a politician who collects positions. It does not need jersey launches and stadium inaugurations and press conference promises. It needs someone who actually understands cricket, who is accountable to results, and who can be removed when those results do not come. That is what real leadership looks like. We had glimpses of it before. We can have it again. But not under this man. Not under this regime of shame. Fire Mohsin Naqvi now. The rot starts at the top and the top must fall.</p><p>One last thing. Everything written here is limited to four senior men’s tournaments. This does not even scratch the surface of what has happened to our Under-19 cricket, our emerging players setup, our women’s cricket, and our bilateral series performances under this regime. Those are separate disasters that deserve their own accountability. But even if you judge Naqvi solely on four tournaments with the senior men’s team, the case is already overwhelming. Four chances. Four exits. No semi-finals. No excuses left. The full picture is even darker than what is written here.</p><p>#MajorSurgeryNeverCame #4TournamentsNoExcuse #ProtectedFailure #EstablishmentCricket #PCBAccountability #NaqviQuitNow</p><ol><li>Naqvi elected PCB Chairman (February 6, 2024) <a href="https://www.espncricinfo.com/story/mohsin-naqvi-elected-pcb-full-time-chairman-for-three-years-1420039">https://www.espncricinfo.com/story/mohsin-naqvi-elected-pcb-full-time-chairman-for-three-years-1420039</a></li><li>Naqvi admits “no player pool” after Bangladesh Test defeat (August 2024) <a href="https://www.espncricinfo.com/story/pcb-chairman-mohsin-naqvi-questions-depth-of-pakistan-s-talent-pool-1448803">https://www.espncricinfo.com/story/pcb-chairman-mohsin-naqvi-questions-depth-of-pakistan-s-talent-pool-1448803</a></li><li>Naqvi appointed Federal Interior Minister while keeping PCB chair (March 2024) <a href="https://www.espncricinfo.com/story/pcb-chairman-mohsin-naqvi-appointed-pakistans-interior-minister-1424636">https://www.espncricinfo.com/story/pcb-chairman-mohsin-naqvi-appointed-pakistans-interior-minister-1424636</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d429d3b6266" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spec-Driven Development with Spec Kit]]></title>
            <link>https://medium.com/@hashaamkhan975/spec-driven-development-with-spec-kit-34c443e3eaf6?source=rss-533c3fc324bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/34c443e3eaf6</guid>
            <dc:creator><![CDATA[Meer Hashaam khan]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 12:10:04 GMT</pubDate>
            <atom:updated>2025-10-02T19:51:26.498Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a Web App Step by Step</h3><h3>Step 1: Setup &amp; Installation</h3><p>Before we start building our podcast app, we need to set up <strong>Spec Kit</strong> on our machine. Spec Kit is a CLI tool that integrates with your AI agent (like Copilot Chat or Claude in VS Code).</p><p>There are <strong>two ways</strong> to install or run Spec Kit:</p><h3>Option A — Persistent Installation (Recommended)</h3><p>This makes the specify command available globally, so you can use it across all projects.</p><p>Open your VS Code terminal and run:</p><p><strong>uv tool install specify-cli — from git+https://github.com/github/spec-kit.git</strong></p><p>✔ Use this if you plan to work on multiple projects or in a team.</p><h3>Option B — One-Time Execution (Quick Test)</h3><p>If you just want to try it out without installing:</p><p><strong>uvx — from git+https://github.com/github/spec-kit.git specify init podcast-site</strong></p><p>This will fetch Spec Kit and run it directly without adding it to your PATH.<br> ✔ Use this if you’re experimenting or running a demo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gyvSHmAoDCzz38DBSwONHg.png" /></figure><p>From here, we will select the model we want to use. I will continue with Copilot.</p><p>And then we will use the script type, I will go with the power shell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u17jbUnEuOiX0PHQvPZaCg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*00BIKgbpO3nHCLrqmdikQA.png" /></figure><p>So far, we’ve completed the initialization phase. Now we’ll move on to the development stage. For this example, I’ll be building a static podcast application that displays a list of podcasts.</p><p><strong>Constitution File (/constitution)</strong></p><p>When you initialize a project, Spec Kit generates a file like:</p><p><strong>/specify/constitution.md</strong></p><p><strong>/constitution = “The rules of the game”</strong></p><p>This file is your <strong>project rulebook</strong>.</p><h3>What goes inside?</h3><p>You’ll want to define:</p><ol><li><strong>Principles</strong></li></ol><ul><li>Accessibility requirements</li><li>Security rules</li><li>Performance standards</li></ul><ol><li><strong>Stack decisions</strong></li></ol><ul><li>Frontend (framework, styling)</li><li>Backend (API, DB)</li><li>Deployment target</li></ul><ol><li><strong>Team rules</strong></li></ol><ul><li>Code review policies</li><li>Testing requirements</li><li>Commit conventions</li></ul><ol><li><strong>Style guidelines</strong></li></ol><ul><li>ESLint/Prettier rules</li><li>Naming conventions</li></ul><p>Default Constitution</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mz2_52B0PQWM6a6ex1tzcg.png" /></figure><p>Now this is a default constitution file, but we need a constitution for our website, so I’ll give a command to my agent mode.</p><p>Now, first we will change the constitution file by giving this command to the agent mode.</p><p><strong><em>Fill the constitution with the bare minimum requirements for the static web app as per the requirements.</em></strong></p><p>So now we have our new constitution file ready</p><p>New file:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ta9Z6pT7P2uevmWnjpFd3A.png" /></figure><p>Okay, now the next main part is the spec: task, plan, and implement — and before implementation comes planning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*Ot0xFACRujubaLh6v3-nlw.png" /></figure><p><strong>/spec — What and Why?</strong></p><p>Now we will move forward with this.</p><p><strong><em>/specify I am building a modern podcast website, I want it to look sleek, something that would stand out. Should have a landing page with one featured episode. There should be an episode page an about page and FAQ page. should have 20 episodes and the data is mocked. Dont need to pull anything from any real feed.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMkGo0LenIyOE8BWNdU1VA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jr8xTD-6DCoiM394X4QdQw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N4bZYpZR4_2ji-ub5ZTxiQ.png" /></figure><p>At this stage, we can see that certain parts of our spec.md needs clarification. To address this, we will run the relevant commands.</p><p><strong><em>For things that needs clarification, use the best guess you think is reasonable. Update acceptance checklist after.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JRn5GRCn9HYJpCV5h39WVw.png" /></figure><p>Clarification is added; now we can move on to the Plan phase.</p><p><strong>/plan → How (Blueprint)</strong></p><p><strong><em>/plan I am going to use Next.js with static site configuration, no databases — data is embedded in the content for the mock episodes. Site is responsive and ready for mobile.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cisPABWK_oBhEJUQ9UC5lQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TITzrFfeoAM1sCPEsGVTWg.png" /></figure><p><strong>Plan Command Output: Complete Design Package</strong></p><h3>What /plan gives you</h3><ul><li>Not just <strong>one file</strong>, but a <strong>complete design package</strong>.</li><li>Multiple interconnected files → together form a <strong>blueprint for implementation</strong>.</li></ul><h3>Central File</h3><ul><li><strong>plan.md</strong></li><li>Main orchestrator.</li><li>Tracks progress.</li><li>Connects all other files.</li></ul><h3>Supporting Files</h3><ul><li><strong>research.md</strong></li><li>Tech decisions (e.g., Next.js, Tailwind, TypeScript).</li><li>Performance strategies.</li><li>Deployment approaches.</li><li>Explains the <strong>“why”</strong> behind choices.</li><li><strong>data-model.md</strong></li><li>Full data architecture.</li><li>TypeScript interfaces.</li><li>Entity relationships.</li><li>Validation rules.</li><li>JSON structure examples.</li><li><strong>data-contracts.md</strong></li><li>Defines <strong>data flow</strong> in the app.</li><li>JSON → React component loading.</li><li>Error handling strategies.</li><li>Ensures consistency in data handling.</li><li><strong>quickstart.md</strong></li><li>Actionable setup steps.</li><li>Working code examples.</li><li>Validation tests.</li><li>Troubleshooting guidance.</li></ul><p><strong>Why is this powerful?</strong></p><ul><li><strong>Single command → full package</strong>.</li><li>Not just high-level planning → <strong>ready-to-use code + structures</strong>.</li><li>Each file solves a specific gap:</li><li>Research = Why this stack.</li><li>Data-model = What data looks like.</li><li>Data-contracts = How data moves.</li><li>Quickstart = How to start coding.</li><li>Eliminates ambiguity.</li><li>Makes transition from planning → coding <strong>seamless</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xKia6BD7JbZQY349u_9qog.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DRqCK0ZyRkmiAOviczSLPg.png" /></figure><p>Now comes the task</p><h3>🛠️ What /tasks does</h3><p>When you already have a <strong>/plan</strong>, it’s usually too high-level for implementation. A plan might say:</p><p><em>“Use Next.js + Tailwind to build a podcast website with an episodes list, a contact form, and Supabase backend.”</em></p><p>…but that’s still too vague for a developer or AI to code directly.</p><p>That’s where <strong>/tasks</strong> comes in:</p><ul><li>It takes the <strong>plan</strong> (the blueprint).</li><li>Splits it into <strong>atomic, testable units of work</strong>.</li><li>Make each unit small enough that /implement can handle it cleanly.</li></ul><p>Now our agent mode will run this command.</p><p><strong>/tasks now break down this into tasks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4h78bcHdJdLi6H40pJOFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vkYvLlKvI3XKVnBIboEs8Q.png" /></figure><p>Before jumping into task implementation, it’s a good idea to verify that everything is consistent. We can do this by running /analyze, which checks whether our constitution, spec, plan, and tasks are properly aligned.</p><p><strong>So we will run /analyze</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GSGx8OD2Lpyi3clwE8R3cg.png" /></figure><p><strong>And now, before implementation whole analysis is done.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bmSidozQ0egzpar6U9t2rg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2S7vghbcYFs_d-roYQeklw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QCdmeFPy_IvJSUmMmoRZfQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Ml441Zf4lYBWk-EKcN5sA.png" /></figure><p><strong>And now, finally, we will run.</strong></p><p><strong>/implement</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oOzHmFiP5lZgvE4vJ9cJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f7G3M6gncRyzN0yO0tsGDw.png" /></figure><p><strong>Final web app</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGrVys3MKij9n95-EP0-VQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TtynH5CHTC23vt4f8KUWNw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnj1zdYs5TkFg4P0N6wtYg.png" /></figure><p>Now, moving on to the next scenario: when we already have a project and need to introduce <strong>Spec Kit development from the middle of it</strong>, here’s what we will do.</p><p><strong>Spec-Kit: Mid-Project Developer Guide</strong></p><p>Okay, I’ll show you how we can configure Spec Kit if we’re starting from the middle of a project or making revisions. For Example, we will take this Project as an example where I have set up my portfolio. Now we need to be careful with merging and decide whether to rely fully on the Spec Kit or proceed step by step.</p><p><strong>Current Progress:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WDYlV8N6-0DnjQWGyEsnXg.png" /></figure><p>Now I will initialize the spec kit here. Open Command Prompt or use VS Code terminal, go to the project directory, and run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hpDHX0l6cWR3PhVXQdrO5Q.png" /></figure><p>Further installation, as we previously did. Now we can see the spec kit in our project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QqAAwZW7m8G2v8V3UDpBwA.png" /></figure><p><strong>Now time to repeat the process of the first prompt</strong></p><p><strong>/constitution<br>Create a constitution for a simple frontend portfolio built in React.<br>The constitution should define:<br>- Tech stack: React + TailwindCSS<br>- Rules: responsive design, accessibility (WCAG AA), clean code, reusable components<br>- Structure: Home, About, Projects, Contact pages</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yerrFkbQdpD0GAwn542JUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TFrOPBkOD13iJiEfkvTBpw.png" /></figure><p><strong>Now /specify<br>Update the specification for the existing React portfolio app.</strong></p><ul><li><strong>Keep the current structure but refine it.</strong></li><li><strong>Add clear purpose: Showcase personal portfolio and projects.</strong></li><li><strong>Features should include: Home page, About section, Project listing, Contact form.</strong></li><li><strong>Update UI requirement: Minimal, responsive, modern design with TailwindCSS.</strong></li><li><strong>Ensure data for projects (title, description, tech stack, links) comes from a JSON file.</strong></li><li><strong>Behavior should include: Navigation via React Router, smooth scrolling, form validation for contact page.</strong></li><li><strong>The spec should replace the old portfolio spec with this updated version instead of creating a new file.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_9cemyA5Z7HiA7ffpD7vdg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yo-uudYn6wkBxo-2QmRAxw.png" /></figure><p><strong>Now Next Command</strong></p><p><strong><em>Okay now i want pages to be little bit dark and modern</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bWgarfbtm3lRBq4HrSG1Fg.png" /></figure><p>Now we will run:</p><p><strong>/clarify</strong></p><p>This will review the specification we just created for the portfolio app, highlight any ambiguities or risks, and suggest clarifications so that the spec is complete and ready for the next step (/plan).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ThX2A-L3Ut6t1BBbFncgQw.png" /></figure><p><strong>Follow instructions in plan.prompt.md.</strong></p><p><strong>consult the readme for details but we have a framework and we are adding a new temp. we dont want tests too</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-FUqgLXnyo5MyW50gteXw.png" /></figure><p>Now run <strong>/tasks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3sId9vBILASY3UbKAYyYg.png" /></figure><p>Now run <strong>/analyze</strong> command</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvbVjvq2IhgLNzaQ9GKlNQ.png" /></figure><p>And finally <strong>/implement</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*22dWtDRgaQmQN3LRMm1Lzg.png" /></figure><p><strong>Spec-Kit Workflow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*swVvm0WtYzMl2vVSgKSV9w.jpeg" /></figure><p><strong>Rules to Follow</strong></p><ol><li>Always start with /constitution.</li></ol><p>Define your project’s principles and rules before creating specifications. This ensures consistency throughout development.</p><p>2. Lock your /spec before planning.</p><p>Finalize <em>what</em> and <em>why</em> before moving to <em>how</em>. If specs change, regenerate your plan and tasks.</p><p>3. Use /clarify liberally</p><p>Never move forward on a vague spec. Run /clarify to de-risk and remove ambiguities before you waste time coding.</p><p>4. Break tasks into small tasks with /tasks.</p><p>Smaller, well-defined tasks are easier to implement, review, and test.</p><p>5. Run /analyze before /implement</p><p>This step ensures there are no mismatches between spec, plan, and tasks. It’s your safety check.</p><p>6. Review at every stage</p><p>AI can generate specs, plans, and code — but humans must validate. Treat Spec Kit as a co-pilot, not a replacement.</p><p>7. Keep /constitution up to date.</p><p>If your stack, principles, or rules evolve, update the constitution. This prevents AI drift and keeps your project aligned long-term.</p><p>8. Spec Kit won’t write your entire app for you.</p><p>What it <em>will</em> do is keep your project aligned, reduce miscommunication, and let you and your team focus on building correctly instead of correcting misunderstandings later.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34c443e3eaf6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Reached Duolingo’s Top League… But Was It Worth It?]]></title>
            <link>https://medium.com/@hashaamkhan975/i-reached-duolingos-top-league-but-was-it-worth-it-1a5df6bcf986?source=rss-533c3fc324bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a5df6bcf986</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[duolingo]]></category>
            <category><![CDATA[language]]></category>
            <dc:creator><![CDATA[Meer Hashaam khan]]></dc:creator>
            <pubDate>Sat, 09 Aug 2025 23:58:42 GMT</pubDate>
            <atom:updated>2025-08-09T23:58:42.149Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been on Duolingo for about a year, but for the past 7 weeks, I’ve been using it actively and consistently. Last week, I finally reached the Diamond League — the very top league in the app.</p><p>It feels great to see that shiny badge next to my name, but here’s the thing: it’s only truly worth it if you’re doing it for the right reason — <strong>learning</strong>, not just climbing the leaderboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KtsPqyv4vhy6_murKP0-4Q.jpeg" /></figure><h3>My Way of Learning</h3><p>From the beginning, I decided I wasn’t going to speed-run lessons just for XP. I go slow, making sure I actually understand the material. I read every phrase carefully, repeat it out loud, and try to work it into my everyday conversations — even if it means talking to myself in the kitchen.</p><p>For me, the goal is simple: <strong>learn and remember as many words and phrases as possible</strong>. If I can’t use a phrase in real life, it’s just a line of text on a screen.</p><h3>Climbing the Leagues</h3><p>The first leagues felt like a warm-up — Bronze, Silver, Gold — no big challenge. But once I hit Ruby League, the game changed. Suddenly, I was up against people from all over the world, many of whom seemed to spend hours every day on Duolingo.</p><p>At that level, if you skip a day, you drop fast. Staying near the top takes:</p><ul><li>Consistent daily practice — no excuses</li><li>Smart timing for challenges and double XP boosts</li><li>Patience to keep going even when you’re tired</li></ul><h3>Getting to Diamond</h3><p>Obsidian League was the real test. I knew if I wanted to make it to Diamond, I’d have to step up my routine. So I broke my practice into three sessions: one in the morning, one during lunch, and one before bed. That way, I kept adding points throughout the day instead of cramming at night.</p><p>By Sunday, I was in the top three. When the week ended, I got the notification: <strong>Welcome to the Diamond League!</strong> It was satisfying — like finishing a marathon. But it also made me realize something: the league is just a game feature, not the real prize.</p><h3>The Real Win</h3><p>The Diamond badge looks cool, but it doesn’t help you order food in another country or understand a movie without subtitles. The real win is being able to read, speak, and actually understand the language in real situations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OiMcmuAtTBTpgF-l95Nplg.png" /></figure><p>So for me, the rule stays the same:</p><p><strong>Learn first. Compete second. Keep it slow and steady. </strong>That’s how Duolingo stays fun, useful, and stress-free .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a5df6bcf986" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Replaced 2 Days of Work with 2 AI Tools.]]></title>
            <link>https://medium.com/@hashaamkhan975/how-i-replaced-2-days-of-work-with-2-ai-tools-ac07b0a1414d?source=rss-533c3fc324bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac07b0a1414d</guid>
            <category><![CDATA[stitches]]></category>
            <category><![CDATA[cursor]]></category>
            <dc:creator><![CDATA[Meer Hashaam khan]]></dc:creator>
            <pubDate>Mon, 30 Jun 2025 11:18:25 GMT</pubDate>
            <atom:updated>2025-06-30T11:32:55.500Z</atom:updated>
            <content:encoded><![CDATA[<p>When you’re under pressure to deliver and time is tight, thinking smart matters more than working hard. I recently faced a situation where I needed to quickly build a website for my project. There was no design in place, no mockups, and I had a limited window to get something functional up and running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tWVwQS06KqLeAtP5vdNo6A.jpeg" /></figure><p>Instead of following the traditional process of wireframing and designing from scratch, I turned to a more efficient approach — one that combined <strong>Google Stitch</strong> for idea structure and <strong>Cursor</strong> for rapid development.</p><h3>🧠 Step 1: Structuring with Google <strong>Stitch</strong></h3><p>I began by heading over to <a href="https://stitch.withgoogle.com/">Google Stitch</a> and describing my project in plain terms.</p><blockquote>“Generate five core sections for a web-based tool that includes features like dashboards, project review, classification, download center, and document storage.”</blockquote><p>Within minutes, Google Stitch generated a clean breakdown of the core components my website should have. It gave me a structured and visual layout of the sections — perfect for jumping straight into development without wasting hours on design ideation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bmg7F65RcLZY-mjvYehLfg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IZHaXPayBmoRQR6PJRFaYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D0Q-U5LoE0H430WUpfcDhw.png" /></figure><p>These visuals gave me exactly the clarity I needed to move forward confidently.</p><h3>⚡ Step 2: Building with Cursor</h3><p>Next, I moved to <a href="https://www.cursor.so/">Cursor</a>, an AI-powered code editor that has quickly become one of my favorite tools. It seamlessly blends code assistance with an intuitive development environment, making it ideal for quickly building real-world projects.</p><p>Here’s how Cursor helped:</p><ul><li><strong>Scaffolding</strong>: Generated the base structure using React.</li><li><strong>Component Creation</strong>: Built UI components for each section suggested by Google <strong>Stitch</strong>.</li><li><strong>Routing</strong>: Added navigation logic between different views.</li><li><strong>Styling</strong>: Used Tailwind CSS with AI-generated utility suggestions.</li></ul><p>It felt like pair programming with an experienced teammate who already understood what I wanted.</p><h3>⏱️ The Result: 2 Days’ Work Done in 2 Hours</h3><p>In less than two hours, I had a fully functional front-end prototype ready — something that normally takes me at least a couple of days when working solo.</p><p>This wasn’t a rushed solution. It was clean, maintainable, and most importantly, it met the project’s needs without compromising quality.</p><h3>💡 Final Thoughts</h3><p>This approach may not be ideal if you’re in the early stages of learning web development — tools like Cursor and Google <strong>Stitch </strong>can abstract away too much. But if you’re comfortable with code and need to move fast (e.g., tight deadlines, client demos, MVP validation), this workflow can save you <strong>a lot</strong> of time.</p><p>It’s about working smarter: letting AI handle the repetitive or structural tasks so you can focus on refining and shipping.</p><p><strong>Would I use this method again?</strong><br> Definitely — for side projects, internal tools, or anywhere speed and functionality matter more than pixel-perfection.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac07b0a1414d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Month of Learning, Failing, and Growing Through Outreachy]]></title>
            <link>https://medium.com/@hashaamkhan975/one-month-of-learning-failing-and-growing-through-outreachy-1860350b44a4?source=rss-533c3fc324bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1860350b44a4</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[nixos]]></category>
            <dc:creator><![CDATA[Meer Hashaam khan]]></dc:creator>
            <pubDate>Sat, 31 May 2025 21:15:47 GMT</pubDate>
            <atom:updated>2025-05-31T21:19:55.251Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Earlier this year, I decided to dive into the world of open source through the<a href="https://www.outreachy.org/"> Outreachy</a> program — an initiative that supports underrepresented groups in tech by offering remote internships with open source organizations.</p><p>As a newcomer, I was both excited and intimidated. I’d never contributed to a large-scale project before, and the idea of submitting real code, seen and reviewed by developers around the world, was overwhelming.</p><p>But what followed was a month of learning, failing, growing, and contributing in ways I never imagined.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fWsUTeqO_4BI9muPbIKdw.png" /></figure><h3>Getting Started with Open Source</h3><p>Before Outreachy, I had a basic understanding of what open source was. But during this journey, I learned how open source communities actually operate — from repositories and issues, to pull requests, forks, and contribution guidelines.</p><p>Once I got the hang of the basics, I began exploring how different open source projects work. Each project had its own community, structure, and contribution process. It was fascinating… and a bit confusing at first. Every organization had its own approach, rules, and application steps — and learning to navigate them was a lesson in itself.</p><h3>My Outreachy Application Experience</h3><p>I initially filled out my application with excitement, then waited — nervously — to hear back. When I found out I had passed the initial round and was eligible to contribute, I was thrilled.</p><p>The real work began during the contribution period. This phase lasted approximately a month, during which I contributed to several organizations, gained insight into their workflows, and established connections with mentors. I discovered amazing open source communities like:</p><ul><li>Bioconductor</li><li>Mozilla</li><li>OCaml</li><li>And eventually… <a href="https://github.com/ngi-nix">NixOS</a></li></ul><h3>Discovering NixOS and NGI Projects</h3><p>It was the NixOS community that truly resonated with me. Their documentation, mentors, and collaborative approach helped me get hands-on with their NGI projects (Next Generation Internet by the European Commission). I worked on more than 10 issues across different repositories, ranging from triaging to basic contributions.</p><p>Below are a few selected issues I contributed to:</p><h4>NGI Project: PeerTube</h4><p>I contributed by triaging the PeerTube package issue — helping evaluate the package, gathering relevant data, and identifying blockers.<br> Link:<a href="https://github.com/ngi-nix/ngipkgs/issues/821"> Issue #821 on GitHub</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*i8kc-UO2ugXIOWzvuw2VbQ.png" /></figure><h4>NGI Project: DMT (Data Management Tool)</h4><p>For this project, I assisted with organizing metadata and moving files as part of the initial triage process.<br> Link:<a href="https://github.com/ngi-nix/ngipkgs/issues/795"> Issue #795 on GitHub</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*5G6n-SbPVNXfE_dYkYP0MQ.png" /></figure><h4>NGI Project: Pretalx</h4><p>Pretalx is a conference planning tool. My role was to review the current packaging efforts, assess what was missing, and help summarize the findings for other contributors.<br> Link:<a href="https://github.com/ngi-nix/ngipkgs/issues/818"> Issue #818 on GitHub</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*gIwMZYgrm4_Mn0hi6zhJlw.png" /></figure><h3>Talking with Mentors and Navigating Complexity</h3><p>One of the best parts of the experience was talking directly with mentors and contributors. These conversations helped clarify expectations and introduced me to real-world development practices — far beyond what tutorials ever show.</p><p>However, each organization and project had different contribution workflows, timelines, and processes. Initially, this was confusing — learning how to adapt and follow multiple sets of guidelines at once was a skill I had to quickly develop.</p><p>But that’s what made the journey so valuable: it was pure learning, at every step.</p><h3>Final Thoughts: Not Selected, Still Worth It</h3><p>Although I wasn’t selected as a final Outreachy intern, the month-long grind was worth every minute. I stepped into a global developer community, contributed to impactful projects, and most importantly — I learned by doing.</p><p>This wasn’t just about getting an internship. It was about building confidence, getting out of my comfort zone, and growing as a developer.</p><p>If you’re even remotely interested in open source, take the leap. Apply to Outreachy, contribute to a project, ask questions, make mistakes, and improve. The community is more welcoming than you think, and the growth is real.</p><h3>Useful Links</h3><p><a href="https://www.outreachy.org/">Outreachy Website</a><br><a href="https://github.com/NixOS">NixOS GitHub</a><br>My GitHub Contributions:<strong> </strong><a href="https://github.com/hashaam-011"><strong>https://github.com/hashaam-011</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1860350b44a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create Serverless Apps Using Kubernetes and Knative: A Complete Guide]]></title>
            <link>https://medium.com/@hashaamkhan975/create-serverless-apps-using-kubernetes-and-knative-a-complete-guide-e00afa9afa11?source=rss-533c3fc324bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e00afa9afa11</guid>
            <dc:creator><![CDATA[Meer Hashaam khan]]></dc:creator>
            <pubDate>Sun, 13 Oct 2024 16:23:38 GMT</pubDate>
            <atom:updated>2024-10-13T16:32:56.209Z</atom:updated>
            <content:encoded><![CDATA[<p>Serverless computing allows developers to focus solely on writing code without worrying about the infrastructure. With <strong>Kubernetes</strong> and <strong>Knative</strong>, you can create serverless applications that scale automatically, reduce operational complexity, and run seamlessly across any environment — on-premises or in the cloud. In this guide, we’ll walk you through how to set up a serverless application using Kubernetes and Knative, from start to finish.</p><h3>Table of Contents</h3><ol><li>What is Serverless Computing?</li><li>Overview of Kubernetes and Knative</li><li>Prerequisites</li><li>Setting Up Kubernetes</li><li>Installing Knative</li><li>Deploying a Serverless Application</li><li>Scaling and Autoscaling with Knative</li><li>Managing Traffic with Knative Routing</li><li>Conclusion</li></ol><h3>1. What is Serverless Computing?</h3><p>Serverless computing allows you to run applications without provisioning or managing servers. In a serverless model, the infrastructure scales dynamically based on the demand for the app, and developers pay only for the resources consumed. Kubernetes with Knative takes serverless to the next level by providing flexibility, scalability, and a powerful ecosystem to manage serverless workloads.</p><h3>2. Overview of Kubernetes and Knative</h3><h3>Kubernetes:</h3><p>Kubernetes is a powerful open-source platform for automating the deployment, scaling, and operation of containerized applications. It offers robust orchestration, which makes it easier to manage large clusters of containers.</p><h3>Knative:</h3><p>Knative is an open-source extension to Kubernetes designed to support serverless workloads. It simplifies the process of deploying and managing serverless apps on Kubernetes. Knative consists of two main components:</p><ul><li><strong>Knative Serving</strong>: Manages the deployment of serverless containers and provides scaling, auto-scaling, and routing capabilities.</li><li><strong>Knative Eventing</strong>: This enables apps to consume and react to events in a loosely coupled manner.</li></ul><h3>3. Prerequisites</h3><p>Before getting started, ensure you have the following:</p><ul><li>A Kubernetes cluster (You can set this up locally using <strong>Minikube</strong> or use a managed Kubernetes service like <strong>GKE</strong>, <strong>AKS</strong>, or <strong>EKS</strong>)</li><li><strong>kubectl</strong> installed (Kubernetes command-line tool)</li><li>Docker installed for building container images</li><li>Helm (optional but recommended for easier installations)</li><li>Basic knowledge of Docker, Kubernetes, and YAML files</li></ul><h3>4. Setting Up Kubernetes</h3><p>First, you need a Kubernetes cluster running. You can set up Kubernetes locally using <strong>Minikube</strong> or use a cloud provider’s managed Kubernetes services like Google Kubernetes Engine (GKE), Amazon EKS, or Azure AKS.</p><h3>Step 1: Install Minikube (Optional)</h3><p>To run Kubernetes locally, install <strong>Minikube</strong>.</p><pre>bash</pre><pre># Install Minikube<br>curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64<br>sudo install minikube-linux-amd64 /usr/local/bin/minikube</pre><pre># Start Minikube<br>minikube start --driver=docker</pre><h3>Step 2: Verify Kubernetes Cluster</h3><p>Ensure your Kubernetes cluster is running by using the following command:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl get nodes</pre><p>You should see a list of nodes with the status Ready.</p><h3>5. Installing Knative</h3><p>Once your Kubernetes cluster is ready, the next step is to install Knative. We’ll install <strong>Knative Serving</strong> for managing serverless workloads.</p><h3>Step 1: Install Istio (for Networking)</h3><p>Knative uses Istio as the default ingress and service mesh provider. Install Istio by following these steps:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl apply -f https://github.com/knative/net-istio/releases/latest/download/release.yaml</pre><p>Check if the Istio pods are up and running:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl get pods -n istio-system</pre><h3>Step 2: Install Knative Serving</h3><p>Next, install <strong>Knative Serving</strong>:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl apply -f https://github.com/knative/serving/releases/latest/download/serving-crds.yaml<br>kubectl apply -f https://github.com/knative/serving/releases/latest/download/serving-core.yaml</pre><p>Verify that Knative Serving is running:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl get pods -n knative-serving</pre><p>You should see pods like controller, autoscaler, and webhook running.</p><h3>6. Deploying a Serverless Application</h3><p>Now that Knative is installed, let’s deploy a simple serverless application. We’ll deploy a containerized application that responds with “Hello, World!”</p><h3>Step 1: Create a Knative Service YAML File</h3><p>Create a file called service.yaml with the following content:</p><pre>yaml</pre><pre>Copy code</pre><pre>apiVersion: serving.knative.dev/v1<br>kind: Service<br>metadata:<br>  name: helloworld<br>spec:<br>  template:<br>    spec:<br>      containers:<br>        - image: gcr.io/knative-samples/helloworld-go<br>          env:<br>            - name: TARGET<br>              value: &quot;Hello, Knative!&quot;</pre><h3>Step 2: Apply the Service</h3><p>Deploy the Knative Service using kubectl:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl apply -f service.yaml</pre><p>Knative will automatically create the necessary Kubernetes resources, including a Pod and a Route, to manage your application.</p><h3>Step 3: Verify the Deployment</h3><p>Check if the service has been deployed successfully:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl get ksvc</pre><h3>7. Scaling and Autoscaling with Knative</h3><p>Knative automatically scales the application based on traffic. You can simulate traffic to observe autoscaling in action.</p><h3>Step 1: Send Requests to the Service</h3><p>Find the URL of the service by running:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl get ksvc</pre><p>Then, use curl to send requests to the application:</p><pre>bash</pre><pre>Copy code</pre><pre>curl http://&lt;your-service-url&gt;</pre><h3>Step 2: Autoscaling</h3><p>Knative scales down to zero when no requests are being processed. You can monitor the scaling behavior by checking the number of pods:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl get pods</pre><h3>8. Managing Traffic with Knative Routing</h3><p>Knative also supports traffic splitting between different versions of your application. This is useful for A/B testing or canary releases.</p><h3>Step 1: Deploy a New Revision</h3><p>Modify the service.yaml file and update the environment variable TARGET:</p><pre>yaml</pre><pre>Copy code</pre><pre>env:<br>  - name: TARGET<br>    value: &quot;Hello, Knative Version 2!&quot;</pre><p>Deploy the updated version:</p><pre>bash</pre><pre>Copy code</pre><pre>kubectl apply -f service.yaml</pre><h3>Step 2: Split Traffic</h3><p>To split traffic between two revisions, modify the traffic section of your YAML file:</p><pre>yaml</pre><pre>Copy code</pre><pre>spec:<br>  traffic:<br>    - revisionName: helloworld-00001<br>      percent: 50<br>    - revisionName: helloworld-00002<br>      percent: 50</pre><h3>9. Conclusion</h3><p>Congratulations! You’ve successfully set up a serverless application using Kubernetes and Knative. With this setup, you can deploy, scale, and manage serverless applications efficiently. Knative makes it easy to build modern, scalable applications on top of Kubernetes, combining the power of containers with the simplicity of serverless.</p><p>By leveraging Knative’s autoscaling and traffic management features, you can create robust applications that respond to demand while minimizing resource usage when idle.</p><h3>Additional Resources</h3><ul><li>Kubernetes Official Documentation</li><li>Knative Documentation</li><li>Minikube Setup Guide</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e00afa9afa11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous Integration (CI) and Continuous Delivery (CD): The Backbone of DevOps]]></title>
            <link>https://medium.com/@hashaamkhan975/continuous-integration-ci-and-continuous-delivery-cd-the-backbone-of-devops-95f0d12c71ea?source=rss-533c3fc324bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/95f0d12c71ea</guid>
            <dc:creator><![CDATA[Meer Hashaam khan]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 20:32:18 GMT</pubDate>
            <atom:updated>2024-09-09T20:32:18.061Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s fast-paced software development world, one of the key factors to success is delivering features quickly and reliably. This is where <strong>Continuous Integration (CI)</strong> and <strong>Continuous Delivery (CD)</strong> come in. They form the backbone of modern DevOps practices, enabling teams to develop, test, and deploy software at a faster pace without compromising quality.</p><p>In this blog, we’ll explore the importance of CI/CD pipelines, their benefits, and how you can get started with tools like Jenkins, CircleCI, and GitLab CI.</p><h3>What is CI/CD?</h3><p>At its core, <strong>Continuous Integration (CI)</strong> is the practice of frequently integrating code changes into a shared repository, where automated builds and tests are run. This ensures that new changes don’t break existing functionality. <strong>Continuous Delivery (CD)</strong> is an extension of CI that automates the deployment of those changes to a production-like environment, making sure your software is always ready to be released.</p><h3>Why is CI/CD Important?</h3><p>In traditional software development, teams often worked in silos, with developers handing over code to testers and operations teams for deployment. This process was time-consuming and prone to errors. CI/CD revolutionizes this by automating and streamlining the process, leading to:</p><ul><li><strong>Faster Releases</strong>: Developers can push changes more frequently and confidently, knowing that the automated pipeline will catch any issues early.</li><li><strong>Improved Code Quality</strong>: Automated tests ensure that only working code reaches production, reducing bugs and downtime.</li><li><strong>Enhanced Collaboration</strong>: CI/CD encourages teams to work together more effectively, as everyone can see the latest version of the software at any time.</li><li><strong>Reduced Risk</strong>: Deploying small, frequent updates reduces the risk of large, problematic releases.</li></ul><h3>How CI/CD Works</h3><ol><li><strong>Continuous Integration</strong>: Developers push code changes to a shared repository (like GitHub or GitLab). A CI tool like Jenkins or CircleCI detects the new commit and triggers automated builds and tests. If the tests pass, the code is deemed safe to move forward.</li><li><strong>Continuous Delivery</strong>: Once the code is integrated successfully, the CD process automates the deployment to a staging or production environment. The code can be deployed automatically or manually, depending on the pipeline configuration.</li><li><strong>Continuous Deployment</strong>: This is an extension of Continuous Delivery, where every change that passes through the CI/CD pipeline is deployed to production without human intervention. It’s the ultimate form of automation and is typically used by highly mature DevOps teams.</li></ol><h3>Popular CI/CD Tools</h3><p>Here’s a look at some of the most popular CI/CD tools:</p><h4>1. Jenkins</h4><p>Jenkins is one of the most widely used open-source automation servers. It has a vast plugin ecosystem and is highly customizable, making it a popular choice for building and deploying applications.</p><ul><li><strong>Pros</strong>: Open-source, huge community, highly customizable</li><li><strong>Cons</strong>: Can be complex to set up, requires maintenance</li></ul><h4>2. CircleCI</h4><p>CircleCI is a cloud-based CI/CD tool known for its speed and scalability. It integrates seamlessly with GitHub and Bitbucket, allowing teams to automate builds and tests quickly.</p><ul><li><strong>Pros</strong>: Easy to set up, fast execution</li><li><strong>Cons</strong>: Limited free tier, enterprise features are expensive</li></ul><h4>3. GitLab CI/CD</h4><p>GitLab CI/CD offers a complete solution for CI/CD within the GitLab platform. It supports automated testing, deployment, and monitoring out of the box.</p><ul><li><strong>Pros</strong>: Integrated with GitLab, easy to use, great for DevOps</li><li><strong>Cons</strong>: Advanced features can be complex</li></ul><h3>Setting Up a Basic CI/CD Pipeline with GitLab CI</h3><p>Let’s walk through a basic example of setting up a CI/CD pipeline using <strong>GitLab CI</strong>:</p><ol><li><strong>Create a .gitlab-ci.yml file</strong> in the root directory of your repository. This file defines the pipeline configuration.</li></ol><p>Here’s an example configuration:<br>yaml<br><br>stages:</p><p>- build</p><p>- test</p><p>- deploy</p><p>build_job:</p><p>stage: build</p><p>script:</p><p>- echo “Building the application…”</p><p>- # Your build commands here</p><p>test_job:</p><p>stage: test</p><p>script:</p><p>- echo “Running tests…”</p><p>- # Your test commands here</p><p>deploy_job:</p><p>stage: deploy</p><p>script:</p><p>- echo “Deploying the application…”</p><p>- # Your deployment commands here</p><ol><li>Commit the changes and push them to your repository. GitLab CI will automatically detect the .gitlab-ci.yml file and start running the pipeline based on the stages defined.</li></ol><h3>Best Practices for CI/CD Pipelines</h3><ol><li><strong>Automate Everything</strong>: Automate all processes from testing to deployment to reduce human error and ensure consistency.</li><li><strong>Fail Fast, Fix Fast</strong>: Configure your pipeline to catch errors early and stop the build if a test fails. This saves time and resources.</li><li><strong>Keep Pipelines Simple</strong>: Avoid overcomplicating your pipeline. Start with a basic configuration and build on it as necessary.</li><li><strong>Security First</strong>: Use secure practices like signing container images and scanning for vulnerabilities as part of your pipeline.</li><li><strong>Monitor and Optimize</strong>: Continuously monitor the performance of your pipeline and optimize it to ensure quick build times and deployments.</li></ol><h3>Conclusion</h3><p>CI/CD pipelines are a crucial part of modern software development, helping teams deliver quality code faster and more efficiently. By automating the build, test, and deployment process, CI/CD ensures that software is always ready to be released with minimal risk. Whether you’re using Jenkins, CircleCI, or GitLab CI, setting up a robust CI/CD pipeline will significantly improve your development workflow.</p><p><strong>CI/CD Pipeline Workflow Diagram:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2akRBxvhTDvFEBdX" /></figure><p><strong>GitLab CI Configuration File:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2irYJ-8bmtREHzVf" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95f0d12c71ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>