fix the md file rewriting them ?

Author: shadil-rayyan

CONTRIBUTING.md

@@ -1,5 +1,3 @@
-
-
 ## **CONTRIBUTING.md**
 
 ````markdown

docs/cheatsheet.md

@@ -1,24 +1,126 @@
+A hackathon is one of those things that sounds simple on paper but quietly reshapes how people learn, build, and even get hired.
 
+At its core, a hackathon is a time-boxed building sprint—usually 24, 36, or 48 hours—where people come together to create something from scratch. That “something” could be a mobile app, a web platform, an AI tool, a hardware prototype, or even just a sharp prototype that solves one specific problem well. What matters is not perfection, but speed of thinking, clarity of execution, and the ability to turn an idea into something that actually runs.
 
-# Hackathons : Why You Should Join
+But that definition is too clean. In reality, a hackathon is closer to a compressed version of real life in tech: unclear problems, limited time, random teammates, shifting ideas, tired brains at 3 AM, and sudden breakthroughs that feel bigger than they should.
 
-When you first hear the word **hackathon**, you might think it’s about hacking into systems. But actually, hackathons are events where students, developers, and innovators come together to **build projects in a short time**—usually 24 to 48 hours.
+---
 
-### 🌟 Why Join a Hackathon?
+### What actually makes hackathons valuable
 
-1. **Learn by Doing** – In class you study theory, but hackathons let you turn ideas into real projects. You gain hands-on skills faster than normal.
-2. **Teamwork** – You’ll work with friends or new people, just like in real companies. This helps improve communication and collaboration.
-3. **Speed & Focus** – A project that normally takes weeks is built in days because hackathons push you to focus and avoid procrastination.
-4. **Networking** – Many tech companies and mentors attend hackathons. Some even secretly watch participants and invite them for **internships or interviews**.
-5. **Placements & Offers** – Today, many companies hire directly through hackathons. If you build something creative, it can open the door to **job offers and PPOs (Pre-Placement Offers)**.
+Most people assume hackathons are about coding. That’s only partially true. The real value sits somewhere else.
 
-### 🚩 Myths About Hackathons
+A hackathon forces you into a situation where you cannot rely on “someday I’ll learn this properly.” You are forced to learn it *right now*. If you don’t know how APIs work, you figure it out. If your frontend breaks, you debug under pressure. If your idea is too big, you cut it down brutally until it becomes buildable.
 
-* **“They are only for experts.”** – Wrong! Beginners learn the most.
-* **“It’s only coding.”** – No, design, ideas, and teamwork matter too.
-* **“It won’t help in future.”** – In reality, hackathons are becoming a **key path for placements** in tech companies.
+That pressure creates a different kind of learning curve—one that is steep but memorable. People often forget tutorials they watched for hours, but they remember the one night they struggled to make authentication work and finally got it running five minutes before submission.
 
-### 🔮 Why Hackathons Are the Future
+There’s also something deeper happening: you start thinking in systems instead of assignments. Instead of “what is the correct answer,” you start asking “what is the simplest version that works?”
 
-Companies love students who can **think, build, and deliver under pressure**. That’s exactly what hackathons test. For CSE students, joining hackathons means learning faster, building a strong portfolio, and standing out in placements.
+That shift alone is a big reason why hackathons matter.
 
+---
+
+### Why people say hackathons change careers
+
+Hackathons sit at a strange intersection of learning and visibility. In normal academic paths, your work is mostly private: exams, assignments, internal marks. In hackathons, your work becomes public and judged.
+
+This matters more than it seems.
+
+When recruiters or mentors walk around during a hackathon, they are not just looking for the “best” project. They are observing how you think:
+
+* Do you stay calm when something breaks?
+* Do you communicate or isolate yourself?
+* Do you take initiative or wait?
+* Do you understand the problem or just copy solutions?
+
+These are signals that don’t show up on a resume.
+
+There are many real cases where people get internships or job offers directly from hackathons—not because their project was the most advanced, but because they showed strong problem-solving instincts. Sometimes a simple but well-executed idea beats a complex unfinished one.
+
+In competitive environments, companies often value *execution under constraints* more than raw knowledge.
+
+---
+
+### The networking layer nobody talks about properly
+
+Networking in hackathons is not like formal networking events where people exchange LinkedIn profiles and leave.
+
+It happens in a more organic way.
+
+You meet people while struggling with the same bug at 2 AM. You borrow ideas from another team’s demo. You ask a mentor a small question and end up having a 20-minute conversation about career paths. You collaborate with teammates you didn’t know a day ago and somehow build something together.
+
+These interactions feel small in the moment, but they compound.
+
+The important part is that hackathons remove social friction. Everyone is there for the same reason: to build. That shared urgency makes conversations more natural and less forced.
+
+Over time, these connections turn into:
+
+* referrals for internships
+* shared startup ideas
+* open-source collaborations
+* long-term professional relationships
+
+And in tech, these informal networks often matter as much as formal applications.
+
+---
+
+### How networking actually leads to opportunities
+
+Most opportunities in tech don’t come from applying cold. They come from being remembered.
+
+Hackathons help with that because they give people a context to remember you in. Instead of “random applicant,” you become:
+
+* “the person who built that unusual idea in 36 hours”
+* “the team that fixed deployment at the last minute”
+* “the one who explained the architecture clearly during demo”
+
+That context sticks.
+
+When someone later sees your name on a resume or LinkedIn, it is no longer empty data. It triggers memory.
+
+That’s the hidden mechanism behind most hackathon-driven opportunities. It’s not just skill exposure—it’s *memorability under shared experience*.
+
+---
+
+### The benefits that actually matter in the long run
+
+Beyond jobs and networking, hackathons build a few deeper traits that are hard to teach anywhere else.
+
+One is comfort with uncertainty. Most academic systems reward correctness. Hackathons reward adaptability. You learn how to move forward even when you don’t fully understand everything yet.
+
+Another is decision-making under time pressure. You quickly learn that choosing a “good enough” approach and shipping it is better than chasing perfection and finishing nothing.
+
+There’s also exposure to collaboration styles. Some people think out loud, some quietly build, some lead naturally. You start understanding how different minds contribute differently to the same goal.
+
+And over time, this builds something subtle but important: confidence in building things without needing permission.
+
+---
+
+### The downsides people don’t talk about enough
+
+Hackathons are not universally positive, and pretending they are can be misleading.
+
+One major issue is burnout. Staying awake for long hours, working under pressure, and constantly switching context can drain people physically and mentally.
+
+Another issue is superficiality. Because time is limited, projects often become prototypes rather than fully functional systems. Some participants mistakenly confuse “hackathon-ready demo” with real-world readiness, which are very different things.
+
+There’s also inequality of experience. People with prior exposure to frameworks or teams often have an advantage, which can make beginners feel left out if the environment isn’t supportive.
+
+And sometimes, the focus on winning or placing can overshadow learning. People start optimizing for judges instead of solving meaningful problems.
+
+If not approached carefully, hackathons can become performative rather than educational.
+
+---
+
+
+### The real takeaway
+
+A hackathon is not just an event. It is a compressed simulation of building under real-world constraints—time, ambiguity, teamwork, and pressure.
+
+For some people, it becomes a stepping stone to internships or jobs. For others, it becomes a turning point in how they think about building things. For many, it is simply the first time they realize they can actually turn ideas into working systems without waiting for permission or perfect conditions.
+
+The real value is not in winning or losing. It is in what changes in how you approach problems afterward.
+
+Because once you’ve built something in 48 hours that actually works—even imperfectly—you stop thinking of ideas as abstract things.
+
+You start thinking of them as things you can build.

docs/college/hackathon.md

@@ -40,16 +40,7 @@ Placements usually happen in two main ways:
 * **Top Companies May Not Visit:** FAANG and other global giants often don’t conduct campus drives everywhere.
 * **If You’re Not in the Top Ranks:** The “top performers” usually get the majority of good offers.
 
----
-
-## Why Top Companies Sometimes Don’t Come to Your Campus
 
-* They prefer candidates from specific colleges or those who apply directly online.
-* They often look for specialized skills, internships, or proven project experience.
-* They rely on online assessments, referrals, or hackathons to find talent globally.
-* Campus drives may not scale well for their hiring volumes.
-
----
 
 ## How to Get Placed (Campus or Off-Campus)
 

docs/college/placement.md

@@ -30,5 +30,3 @@ Unfortunately, most colleges don’t cover these in detail. That means if you wa
 
 ---
 
-👉 **In short:** College gives you the base, but **your future in CSE depends on how much you learn on your own**. Don’t just wait for the syllabus—explore, build, and grow.
-

docs/college/reality_check.md

@@ -24,14 +24,7 @@ Financial aid is designed to help students who may not have the resources to pay
 * Early scholarship recipients often get additional benefits like mentorship and leadership training.
 * Performing well in the first year can open doors to more scholarships later.
 
----
-
-## Why Are Most Scholarships Available to First-Year Students?
 
-* Colleges and companies want to **invest in students at the start** of their educational journey.
-* It’s easier to evaluate students based on high school performance during admission.
-* Scholarships encourage **students to enroll and commit** to their programs.
-* Once enrolled, students can often apply for departmental or merit-based scholarships later.
 
 ---