Forem: Manas Moon

My Views on ChatGPT Atlas

Manas Moon — Thu, 23 Oct 2025 09:12:13 +0000

When OpenAI launched ChatGPT Atlas, I had the same reaction I once had in the stock market:
“This changes everything.”

Back then, I jumped into trades with my heart, not my head. FOMO, PR hype, empty wallet, bad decisions.

And last week, I saw the same pattern repeat across the internet.

People called Atlas a Google killer.

“A new era of browsing”.
The next big thing we must chase.

But when the dust settled, it was clear:

Atlas is basically Google Chrome just with ChatGPT built inside.

No new universe.
No magical browser.
Just the same internet, layered with AI.

And it hit me like that old trading lesson I paid for in losses:

• FOMO makes you rush emotions.
• Emotional decisions makes you blind.
• Blindness makes you numb, dumb and broke.

Here’s the real takeaway I wish I had learned earlier:

“New tools change your fate.” is a MYTH.

Chasing shiny objects instead of sharpening skills is a MISTAKE.

AI won’t save you from bad habits. It exposes them faster is the LESSON.

AI won’t replace you.
The person using it & your emotional decisions will.

So now I ask myself before jumping on any trend:
Is this a strategic move or just another emotional trade dressed as “innovation”?

Your turn—be honest:
Are you chasing hype again or actually upgrading the human behind the screen?

If you’re done chasing hype and want real, practical AI guidance, subscribe to Codexai here: https://codexai.substack.com/

Join in and stay ahead of the noise.

How To Get Your Next Interview Calls In Next 7 Days (USING AI)

Manas Moon — Thu, 18 Sep 2025 10:46:58 +0000

What if you could learn new programming skills faster, build projects with ease, and ace job interviews—all with a smart assistant by your side 24/7. This is not science fiction; it’s the reality unfolding in today’s tech world.

In fact, 84% of developers are now using or planning to use AI tools in their development process.

Why such a surge?

Because those who embrace AI are reaping big rewards. A recent study by Microsoft found that AI helps developers complete tasks about 55% faster on average. That means what used to take a week of coding might now take just a few days.

If you’re a beginner software developer, leveraging AI isn’t just a cool trick—it can be a game-changer for your learning and career growth.

However, simply having an AI tool doesn’t automatically make you a better developer.

One report noted that while 75% of engineers use AI tools, many teams see no measurable performance gains. The key is knowing how to use AI effectively.

In this guide, we’ll share exactly that.

We’ll explore how AI can become your personal coding mentor, pair programmer, and career coach guiding you from learning the basics all the way to landing a job.

Every section below packs actionable tips and example prompts you can start using today to get ahead. Let’s dive in!

The exact way to use AI so it actually teaches you

Learning to code can feel like drinking from a firehose—there’s so much to absorb.

This is where AI shines as a personal tutor. You can ask an AI-powered assistant (like ChatGPT, Perplexity or Gemini) to explain complex programming concepts in simple terms, provide examples, and even quiz you. The result? You grasp new topics faster and with less frustration.

In fact, 62% of developers say AI tools help them learn faster. Even those just learning to code have caught on – roughly 80% of coding beginners are already using or planning to use AI to boost their learning. AI can break down a tough concept step by step or give you analogies that make it click. It’s like having a patient teacher on call at any hour.

Here’s the prompts to learn faster:

Don’t just passively read tutorials—actively engage with an AI.

For example, if you’re confused about how recursion works or how a Python loop operates, you can prompt the AI to walk you through it. You can also ask for learning roadmaps (for instance, “How do I go from zero to hero in web development?”) and even get the AI to generate practice exercises.

The key is to treat the AI as an interactive learning partner.

Below is a premium prompt that you can try right now to turbo-charge your learning:

Project:
[PROJECT NAME] using [TECH]

Objective:
I want to create a [PROJECT NAME] using [TECH], but I am unsure how to structure it. I want you to guide me like a professional [TECH] developer.

Your Role:
Act as a professional [TECH] developer and help me approach this project the way an expert would.

How I Want the Guidance:

1. Pseudocode & Structure First – I don’t want the actual code immediately. Instead, I need a structured approach and a clear breakdown of sections and elements.
2. Thinking Process Explanation – Explain how a professional would plan and structure the page before writing any code.
3. Step-by-Step Tutorial Format – Guide me through the process in a structured, tutorial-like manner.
4. Conversational Assistance – Give me 1-2 tasks at a time. Once I complete them, I’ll return for the next step.
5. Code on Request – If I need actual code, I will explicitly ask you for it. Otherwise, just provide the structural approach.

Now, guide me step by step as a professional would.
What’s the first thing I should do?

By using prompts like these, you’ll not only get answers but also learn how to learn more effectively. The AI can point you to important topics, explain the “why” behind solutions, and reinforce your knowledge through Q&A. Over time, this constant guidance can significantly shorten the time it takes to go from novice to competent coder.

You can check more such prompts here: **Prompts!**

Debug in Seconds, Not Hours—with this AI Prompt

Once you have the basics down, the next challenge is implementing them:

Writing code.
Building Projects.
Solving Real Problems.

This is where AI becomes your pair programmer, sitting right next to you (in a virtual sense).

AI coding assistants like ChatGPT, Perplexity or Gemini can generate snippets of code, suggest improvements, and help debug errors. The impact on your productivity can be dramatic.

Developers using ChatGPT, Perplexity or Gemini, for example, often see code tasks completed much faster than usual.

One study observed code getting merged around 50% faster when AI assistance was involved. Another team saw a 59% decrease in time spent searching the web for solutions once they started using AI for coding help.

Think about the time you save when you don’t have to do back-and-forth through dozens of Stack Overflow posts because the answer pops up instantly with an AI assistant!

Here’s your ultimate prompt:

Think of the AI as an ever-ready coding buddy.

Starting a project? Ask it to create a boilerplate or outline for your code.

Stuck on a bug? Show the AI your error message or a problematic code snippet.

Need to refactor or optimize something? The AI can propose cleaner, more efficient code.

It can often pinpoint the issue or suggest a fix and while it accelerates your work, studies show this doesn’t mean lower quality—in controlled trials, teams using AI did not sacrifice code quality for speed. You still review and test your code, of course, but the heavy lifting and grunt work are eased by AI assistance.

Use the below AI prompt into your development workflow to fix real issues:

Project/Feature: [name or brief]
Tech Stack: [language/framework + versions]
OS/Env/Package Manager: [e.g., macOS 14, Node 20, pnpm]
Repo/Path (optional): [link or local path]

Objective:
I want to diagnose and fix a real issue (or ship a small feature) in [TECH]. Guide me like a professional [TECH] developer would—fast, precise, and verifiable.

Your Role:
Act as my AI pair programmer. Prioritize clarity, speed, and correctness.

How I Want the Guidance:
1. Structure First (no code yet):
Give me a brief diagnosis hypothesis (2–4 bullets).
Propose 1–2 surgical steps to test the hypothesis.
List exact commands (copy/paste), files to inspect, and where.
2. Professional Planning (concise):
Explain how an expert would approach this (high-level rationale, not step-by-step internals).
3. Tutorial Flow (turn-based):
Give me only 1–2 tasks per turn. Wait for my results before moving on.
4. Code on Request:
Only provide code/diffs when I say: “Code please.”
5. Verification First:
For every task, include how to verify (command, expected output, test).
6. Fail-Forward Rule:
If results differ, tell me exactly what to capture next (logs, stack trace, file snippet) and the next best probe.

Context I’ll Provide (prompt me for what’s missing):
1. Error message / stack trace: [paste]
2. Relevant file snippet(s): [paste path + code]
3. What I already tried: [bullets]
4. Constraints (time, libraries, style): [notes]
5. Interaction Format (each turn you send):

Hypothesis: (2–4 bullets)
1. Why this next step: (1–2 bullets, concise)
2. Tasks (1–2 only): numbered, reproducible
3. Commands / Paths: fenced block
4. Verify: exact check + expected signal
5. If not resolved: what to collect next

Start Now — What’s First?
Ask me for the minimum info you need (logs, file paths, versions), then give me the first 1–2 actions.

By using an AI pair debugger, you’ll not only write code faster but also learn better ways to code.

The AI might introduce you to new functions or libraries, show you best practices, and help you avoid common pitfalls. It’s like having an experienced developer reviewing every line you write. Over time, you’ll notice your own coding skills improving by imitation and practice.

And whenever you hit a roadblock, you have a partner to brainstorm solutions with—available 24/7.

Again, you can check more such prompts here: **Prompts!**

A 7 Day Step-by-Step AI Plan For Your Job Hunt

The ultimate goal of all this learning and building is to land that software development role.

Here too, AI can give you a serious edge by making AI as your career coach and interview partner.

You can practice coding interviews, get help polishing your resume, and even simulate common interview questions with an AI. This kind of preparation can dramatically boost your confidence and performance when it’s time to talk to real hiring managers.

Here’s how to use this 7 day plan:

Time: 60–90 min per weekday, 2–3 hours on the weekend.
Tools: Any LLM (ChatGPT/Perplexity/Gemini), LinkedIn, GitHub, a resume editor, Loom/ScreenRec, Notion/Google Sheets.
Rule: Never invent experience. Use AI to clarify, tailor, and present your real work better.

Day 1: Set up the system and target roles

Goal: Build your funnel and calibrate exactly what “fit” looks like.

Deliverables:

A tracker (Notion/Sheet).
One master resume draft.
Keyword map for 2 target roles.

Steps

Create a tracker with columns: Company | Role | Job Description (JD) link | Keywords used | Resume file | Cover letter file | Applied date | Status | Last touch | Next action.
Pick 2 roles (e.g., Junior Software Engineer, Frontend Developer). Gather 3–5 JDs for each.

Prompts

Extract the hiring signal (paste 3–5 JDs):

You are my ATS and hiring-signal analyst. 
From these job descriptions, extract and group the top 25 unique keywords into:
- Must-have hard skills
- Nice-to-have hard skills
- Tools/frameworks
- Soft skills and behaviors
Return as a compact table with frequency counts. [PASTE JDs]

Build a baseline resume from raw notes:

You are my resume editor for [Designation] role. 
Turn these raw notes into a one-page resume with metric-leaning bullets, past-tense for past roles, present-tense for current, and no fluff. 
Output plain text I can paste. 

[PASTE NOTES/EXPERIENCE]

Close keyword gaps for ATS:

Compare this resume to the Must-have list below. Identify missing or weakly expressed skills and suggest honest wording that reflects entry-level exposure (courses, small projects). Do not fabricate. 

[PASTE RESUME] 

[PASTE MUST-HAVES TABLE]

Day 2: Ship a tiny proof-of-work project (aligned with your JD)

Goal: A small, JD-relevant project with a README and 60–90s demo.

Deliverables:

Repo with README, screenshots.
Loom demo link in README.

Steps

Choose the smallest feature set that mirrors the JDs.
Build, document, record quick demo.

Prompts

Scope a minimal, JD-aligned app:

Act as a staff engineer. 
From this JD, design the smallest possible project that proves fit in 6–8 hours max. Include features, acceptance criteria, a stretch goal, and a simple test plan. 

[PASTE JD]

Scaffold and reasoning notes:

Generate a step-by-step build plan for the above scope in [STACK]. Include folder structure, commands, and a brief “why” for key choices (db, auth, API). 
Return as a checklist I can follow.

README and demo script:

Create a compelling README with sections: 
Problem, Solution, Key decisions, How to run, Tests, Screenshots, Next steps. 
Then write a 60–90 second narration script for a Loom demo that highlights outcomes before tech.

Day 3: Tailor resume and cover notes per JD

Goal: Produce tailored PDFs for 2–3 roles today.

Deliverables:

2–3 tailored resumes and short cover notes.
ATS cross-check.

Steps

For each JD: tear down → map to bullets → ATS pass.
Export a unique PDF per application.

Prompts

JD → checklist of what to mirror:

Turn this JD into a requirements checklist. Label each as Core or Secondary. 

[PASTE JD]

Rewrite bullets to mirror the JD honestly:

Rewrite 6 resume bullets to align with the Core items. Use my real experience only. Add small measurable outcomes where true. One line each, strong verbs first.

[PASTE CURRENT RESUME OR MASTER PROFILE] 

[PASTE CHECKLIST]

ATS sanity scan:

Compare the tailored resume to the JD. List critical keywords missing or underemphasized. Propose natural phrasing that fits my background without exaggeration. 

[PASTE TAILORED RESUME] 

[PASTE JD]

Short cover note (5 lines max):

Write a concise cover email for this JD. Reference 2 JD specifics, link my demo, and state availability. Tone: plain, confident, no clichés. 

[PASTE JD] 

[PASTE PROJECT/LOOM LINK]

Day 4: Precision outreach for referrals

Goal: Start 3–6 warm conversations at target companies.

Deliverables:

Personalized connection notes.
One short DM per target.
A structured follow-up.

Targets: 1 engineer, 1 team lead, 1 recruiter per company.

Prompts

Harvest personalization nuggets:

From this LinkedIn profile and their recent post text, extract 2 specific details I can reference (shared tech, talks, repos, articles). Return as bullets. 

[PASTE PROFILE TEXT + 1–2 RECENT POSTS]

Connection request (140 chars):

Write a 140-character connect note referencing the above nuggets. Goal: earn a brief chat about their team’s workflow. No job ask yet. 

[PASTE NUGGETS]

First DM (3–4 lines):

Draft a 3–4 line message: acknowledge their work (use nugget), share a 60–90s demo link relevant to their stack, and ask for a 12-minute chat about how juniors add value on their team. No resume attachment.

Post-chat referral ask:

After a positive 10-minute chat, write a polite message asking if my background fits [ROLE]. Include 1–2 specific JD matches and link to the demo again. Tone: grateful, non-pushy.

Day 5: Interview prep sprint (coding, behavioral, design)

Goal: Practice like it’s real. Capture feedback. Iterate.

Deliverables:

One timed coding problem with review.
Two STAR stories refined.
One junior-level design drill.

Prompts

Timed coding rehearsal:

Give me one medium [LANGUAGE] problem. Timebox to 25 minutes. After I submit, score me on correctness, readability, complexity, and communication. Provide an optimal solution and 2 follow-ups that test edge cases.

Behavioral STAR bank from my history:

Create 6 STAR stories from these experiences for themes: Ownership, Debugging under pressure, Conflict, Learning fast, Ambiguity, Teamwork. Keep each to 5 tight bullet lines. 

[PASTE EXPERIENCE HIGHLIGHTS]

Junior system design drill:

Run a 10-minute junior system design interview (pick from: URL shortener, rate limiter, notes app). Drive back-and-forth. Force me to state assumptions, data model, APIs, basic scaling, and a single tradeoff. Summarize my gaps and give a one-page improvement plan.

Day 6: Portfolio and profile polish

Goal: Make trust easy. Show proof first, tech second.

Deliverables:

GitHub: 2–3 pinned repos with clean READMEs and demo links.
LinkedIn: headline, About, and Experience updated.
Resume header with GitHub + Loom.

Prompts

GitHub README tightening:

Tighten this README to be recruiter-friendly. First 5 lines must show: Problem, Outcome, Tech, Live/demo link, How to run. Keep the rest scannable. 

[PASTE README]

LinkedIn headline (5 options):

Rewrite my LinkedIn headline for a junior SWE role: Role + core stack + outcome proof (demo). 220 chars max. Provide 5 distinct options. 

[PASTE CURRENT HEADLINE/STACK/DEMO LINK]

LinkedIn About (3 lines):

Write a 3-line About section focused on outcomes and proof. Mirror phrases used in these target JDs to increase search relevance. 

[PASTE 2–3 JD SNIPPETS]

Experience bullets alignment:

Convert these experience bullets to be JD-relevant, one line each, outcome-first. Avoid buzzwords. 

[PASTE BULLETS]

Day 7: Apply smart, follow up, and review the funnel

Goal: Send tailored applications, follow up, analyze what worked, plan Week 2.

Deliverables:

5–7 tailored applications sent.
Follow-ups scheduled in tracker.
Funnel analysis and next-week experiments.

Prompts

Concise cover note per application:

Draft a 5-line cover letter for this JD. Reference 2 specifics, link my demo, and name one next step I’m ready for (e.g., a 20-minute technical screen). 

[PASTE JD] 

[PASTE PROJECT/LOOM LINK]

Post-apply LinkedIn nudge to recruiter:

Write a 3-line LinkedIn message to the company recruiter: mention the role, one JD match, and the 60–90s demo link. Tone: respectful, brief, confident.

Funnel analysis from my tracker:

Analyze this week’s tracker data. Identify where the funnel leaks (views→replies, replies→screens). Recommend 3 experiments for next week with clear hypotheses and how to measure success. 

[PASTE TABLE OR SUMMARY]

Thank-you note template:

Draft a concise thank-you email that references two specific topics we discussed in the interview and includes one follow-up artifact (link to improved README, small fix, or brief doc).

Daily 60-minute Workflow (Mon–Fri)

15 min: JD teardown → tailored bullets.
15 min: one targeted outreach.
20 min: one practice rep (coding or behavioral).
10 min: update tracker and schedule tomorrow’s “one thing.”

Success benchmarks and when to adjust

Tailored apps/week: 10–15.
Warm conversations/week: 5–8.
Target conversions:
- JD → phone screen: ≥ 15%
- Phone screen → onsite: ≥ 30%
- Onsite → offer: ≥ 20%

Prompt to diagnose slowdowns:

Given these weekly metrics, find the bottleneck and propose 3 targeted experiments. 
Label each by expected impact and effort, and tell me exactly what to change in resume, outreach, or project proof. 

[PASTE METRICS]

Take care of below things

Do not fabricate experience, titles, or results.
AI drafts; you verify and personalize.
Keep artifacts consistent across resume, LinkedIn, GitHub, and how you speak in interviews.

Run this 7-day sprint again next week.

Improve one lever per loop. That’s how you compound into interviews and offers.

So that’s it for this time.

P.S. If this changed how you think about AI and software development, share it with one developer friend who needs to see this. The compound effect of AI adoption is real, but it only works if you start now.

If you have any doubt then please reply to this email, comment it below or you can directly DM me your doubt at my LinkedIn. Thanks for reading till the end and would love to hear something from your side now.

Okay then, bye! 👋🏻

Manas 🥂

Founder, Codexai

P.P.S. I help developers, creators and early stage founders find clarity, direction, and momentum with a 60 min consulting call.

Explore all sessions here: Book Your Breakthrough, NOW!!!

The Future of Work is Touch, Trust, and Timing

Manas Moon — Mon, 08 Sep 2025 19:01:15 +0000

The question isn’t if AI will replace jobs. It’s which ones—and when.

Microsoft just dropped a study analyzing 200,000+ real Copilot conversations.

The results are nothing but brutal clarity: 40 jobs are at high risk of extinction. Another 40 are relatively safe.

This isn’t a sci-fi headline. This is the ground shifting beneath our feet.

Here’s the Microsoft Research Paper: https://arxiv.org/pdf/2507.07935v2

The Jobs on the Chopping Block

Writers. Translators. Journalists. Customer service reps. Even data scientists.

Notice the pattern?

These are roles where success = words, numbers, and predictable outputs.

AI thrives here. It doesn’t get tired, it doesn’t procrastinate, and it doesn’t demand a raise.

Think of ChatGPT rewriting a press release in seconds. Or a synthetic AI voice replacing your favorite late-night radio DJ. That’s not a hypothetical—it’s already happening.

The Jobs That Survive (For Now)

Phlebotomists. Surgeons. Construction helpers. Massage therapists.

Again—see the pattern?

These are roles where success = touch, trust, unpredictability.

Try asking AI to hold your hand before a surgery. Or to carry a cement bag up three flights of stairs. Or to comfort a grieving family.

That’s where humans still reign supreme. And will, for a while.

The Bigger Lesson Nobody’s Talking About

People think this list is about “safe” vs. “unsafe” jobs.

It’s not.

This is about inputs vs. outcomes.

AI is unbeatable at inputs: drafting, editing, analyzing, responding.

Humans still dominate outcomes: synthesizing, managing, leading, creating trust.

If your entire job is pushing inputs around, AI will catch you.

If your value is in shaping outcomes, you’ll thrive.

What This Means for You (and Us)

Stop worshipping status. Historians were once seen as intellectual giants. Telemarketers once made fortunes. Both are now on AI’s kill list. Status ≠ security.
Learn to synthesize. The winners will be those who can combine disciplines—coding + communication, design + business, AI + psychology.
Entrepreneurship isn’t optional. When machines eat jobs, the safest bet is creating your own. Even if it starts as a side hustle, control is leverage.
Respect scarcity. Physical labor, trust-based work, and crisis management are scarce—and scarcity drives value.

Think about it: in a world where everyone can draft an article with AI, the rare skill isn’t writing. It’s knowing what to write, why it matters, and how to sell it.

The Silent Revolution

The industrial revolution replaced muscle with machines.

The AI revolution is replacing knowledge with algorithms.

That means the next edge—the human edge—comes from what AI cannot do:

Trust.
Empathy.
Synthesis across silos.
Accountability under chaos.

That’s the cheat code.

Not knowing which prompt to use, but knowing which outcome matters.

Our Takeaway and Manas’s Prediction

Don’t obsess over whether your job is “safe.”

Ask yourself: “Am I building skills AI can’t easily replicate?”

If the answer is no—pivot.

If the answer is yes—double down.

Because the future of work won’t be about competing with AI.

It’ll be about collaborating with it—and out-playing those who don’t know how.

If this issue gave you clarity, forward it to one friend.

That’s how this movement grows.

Subscribe here if you’re not already inside.

The future belongs to those who don’t just read about AI—who use it.

Manas 🥂

Founder, Codexai

PS: I help developers, creators and early stage founders find clarity, direction, and momentum with a 60 min consulting call.

Explore all sessions here: Book Your Breakthrough, NOW!!!

I Tried AI Editors For 14 Days—Here’s What Happened

Manas Moon — Mon, 08 Sep 2025 17:43:22 +0000

“Should I use Cursor? Windsurf? Pair AI? Which one is the best?”

Here’s the uncomfortable truth: it doesn’t matter as much as you think.

Everywhere you look, founders are marketing their AI code editors like they’ve reinvented the wheel. Cursor, Windsurf, Claude Code—shiny logos, fancy UI, big promises.

But if you peek under the hood?

The differences are microscopic.

The performance jump you get by switching from Cursor to Windsurf (or vice versa) is almost negligible. Sure, the UI feels different. The marketing feels louder. But the actual output? Nearly identical.

That’s the paradox: the only big differentiation right now is branding, not breakthroughs.

Why That’s a Good Thing

Here’s where most developers trip up.

They burn days (sometimes weeks) switching tools, re-learning shortcuts, migrating settings… chasing the illusion that “maybe the next editor will make me a 10x engineer.”

But the real truth?

The LLMs powering these editors (GPT, Claude, Gemini, etc.) are doing 90% of the heavy lifting.

The “context windows,” “retrieval strategies,” and other features these editors brag about? Useful, yes. Game-changing, no.

The leap forward isn’t which editor you use.

The leap forward is in how good you are at using one consistently.

The Psychology of Sticking

Think about it.

Netflix vs. Prime. iPhone vs. Samsung. Coke vs. Pepsi.

Once you pick one and get comfortable, you rarely switch—not because the competitor is worse, but because the activation energy to switch is too high for too little gain.

Same with AI code editors. Cursor, Windsurf, Pair AI… all solid. None worth losing sleep over.

So What Should You Do?

Here’s the Codexai principle:

Pick one (anyone). Cursor, Windsurf, Claude Code—doesn’t matter.
Stick to it. Don’t waste cognitive energy chasing “marginal upgrades.”
Focus on depth. The real advantage comes from your workflow, your problem-solving ability, your mastery of prompts.

Do this and you won’t just “use” an AI editor—you’ll bend it into your own personal coding assistant.

Final Thought

Don’t get caught in tool FOMO.

Your edge won’t come from switching editors every quarter. It will come from going deep with one, mastering the craft, and letting the LLMs evolve under the hood while you focus on what actually matters: building.

Because the truth is… the AI code editor you choose today won’t decide if you become a 10x engineer.

You will.

💡 If this helped clear your head, hit reply and tell me: which AI code editor are you using right now or just hovering the keys around VS Code?

Your insights might end up in the next Codexai issue.

Stay sharp,

Manas 🥂

Founder, Codexai

PS: I help developers, creators and early stage founders find clarity, direction, and momentum with a 60 min consulting call.

Explore all sessions here: Book Your Breakthrough, NOW!!!

AI Learning Feels Like a Mess

Manas Moon — Mon, 03 Mar 2025 10:04:50 +0000

The Problem Is You are Busy, But So Is Everyone Else

You want to learn AI, but there’s work, studies, life, and maybe even a cat demanding your attention. Meanwhile, others are building AI projects, landing jobs, and making you feel like you're falling behind. The truth? They’re not smarter. They just use their time better.

You Have Time – You’re Just Wasting It

Think you have no time? Let’s check: How much time do you spend scrolling social media, watching Netflix, or “researching” AI without actually building anything? Found 30 minutes? Great. That’s all you need.

Why Watching Tutorials Won’t Make You an AI Expert

Passive Learning Is a Trap (Stop Watching, Start Doing)

Watching 100 AI tutorials won’t make you an expert. Building just one project will. Imagine learning to drive by watching YouTube videos—you’d still crash. AI works the same way.

Building Projects = Real AI Learning

“You don’t learn AI by reading about it. You learn it by breaking things, fixing them, and breaking them again.” Every AI project teaches you more than any course ever will.

Consistency Over Intensity – The 30-Minute AI Hack

Spending 10 hours on AI once a month won’t work. 30 minutes a day? That’s the secret. Think of it like the gym—you won’t get fit by lifting weights once a year. AI learning is the same.

The 30–60 Minute Rule – Your AI Superpower

One Hour a Day = AI Mastery in Months

One hour a day? That’s 30 hours a month. That’s a full AI project completed, skills sharpened, and confidence boosted.

What Can You Do in 30–60 Minutes?

Week 1: Mini AI Experiments

Forget complex projects. Start with small AI tasks—text classification, sentiment analysis, or predicting tomorrow’s weather (hint: just say ‘rain’ and you’ll be right half the time).

Week 2: Adding AI to Small Apps

Use AI in something real. Chatbots, simple image recognition, or a to-do list that judges your tasks (“You’re seriously postponing ‘Go to Gym’ again?”).

Week 3: Debugging = Real Learning

Your AI model will break. That’s good. Debugging teaches you more than any theory ever will.

Week 4: Showcasing Your AI Work (Because It’s Useless If No One Sees It)

Upload your projects to GitHub. Share them on LinkedIn. Brag a little. You’ve earned it.

Time Hacks to Fit AI Learning Into Your Schedule

Time Blocking – AI Learning Like a Meeting

Put AI on your calendar. Treat it like an important meeting. If someone asks, just say, “I have an AI strategy session.” Sounds fancy, right?

The 2-Minute Rule – Trick Your Brain into Starting

Not in the mood? Commit to just 2 minutes. You’ll likely keep going. It’s like promising to eat just one chip—you know that’s a lie.

The Eisenhower Matrix – Cutting Out Useless Tasks

AI learning should be in the “important but not urgent” category. Skip the unnecessary stuff (like rewatching AI tutorials) and focus on building.

How to Stay Motivated (When AI Feels Hard)

Track Your Progress – The Power of Small Wins

Use a progress tracker. Seeing daily AI work adds up and keeps you motivated. Plus, you’ll have proof that you’re actually learning.

Find an AI Learning Buddy

Accountability works. Join an AI community. Share struggles. Celebrate wins. Maybe even compete on who builds the coolest chatbot (bonus: the loser buys coffee).

Remember WHY You Started

Want a better job? Freelance gigs? Build cool AI projects? Keep that reason in mind. A strong “why” beats all excuses.

Final Thoughts – Start Now, Not “Someday”

AI learning isn’t about having more time—it’s about using time smarter. 30–60 minutes a day is enough to build real AI skills. The key? Start now, not tomorrow. Because tomorrow never comes.

And with this we are signing off. See you in the next article.

🚧 PS: More such articles on Codexai

Cheers xx! 🥂

How I built an AI-Powered Code Reviewer (and you can too).

Manas Moon — Fri, 21 Feb 2025 20:07:49 +0000

AI is flipping the game for developers, and honestly,

I got fed up of seeing people waste hours debugging code what a machine could do it in seconds. So, I thought—why not build an AI (agent type program) that does the boring stuff.

It all started when I was working on a project and constantly had to review my own code. While AI-powered coding assistants like GitHub Copilot help with writing code, I wondered, why isn’t there an AI to review my code? That’s when I decided to build one. So yeah, AI-powered code review isn’t just a convenience—it’s a lifesaver.

The plan was simple:

Create a command-line tool where I can input a code snippet.
Use OpenAI’s GPT-4 to analyze and review the code.

(If you don’t know where to find your secret API key: Check Here.
Return a detailed review with suggestions, best practices, and potential bug fixes.

After some research, I decided on the following stack:

Backend: Python (Standalone CLI tool)
AI Model: OpenAI’s GPT-4 API
Environment: Terminal-based command-line application

You can subscribe to Codexai for more such cool AI prompts.

Workflow

Here’s your premium prompt:

Please generate a Python script for a terminal-based AI code reviewer application that uses OpenAI's GPT model. 
The script should allow users to paste their code into the terminal, and upon submitting it, receive a detailed review of their code. 

The review should include feedback on:

1. Code Quality
2. Best Practices
3. Potential Bugs
4. Performance Improvements
5. Security Concerns

The script should load the OpenAI API key from a .env file and use it to call OpenAI's GPT-4 model. 
The program should allow the user to input code directly into the terminal, and when they press Enter twice, the review should be generated and displayed.

The Python script should include proper error handling and user prompts for a smooth user experience. 
Also, ensure the code is clean, well-commented, and modular for easy understanding. 
The review output should be structured and clear, providing actionable insights for the user.

Here’s your hands-on tutorial:

📌 Step 1: Setting Up the Project

Install Dependencies

I started by creating a new Python project and installing the necessary libraries:

mkdir ai-code-reviewer && cd ai-code-reviewer
python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install openai python-dotenv

Next, I created a .env file to store my OpenAI API key. You need to edit this file and add your own API key:

OPENAI_API_KEY=your_openai_api_key_here

📌 Step 2: Writing the AI Review Logic

I created reviewer.py to handle the review process:

import openai
import os
from dotenv import load_dotenv

def review_code(code_snippet):
    load_dotenv()
    openai.api_key = os.getenv("OPENAI_API_KEY")

    prompt = f"""
    You are an expert software engineer. Review the following code and provide feedback on:
    - Code quality
    - Best practices
    - Potential bugs
    - Performance improvements
    - Security concerns

    Code:
    {code_snippet}
    """

    response = openai.ChatCompletion.create(
        model="gpt-4",
        messages=[{"role": "user", "content": prompt}]
    )

    return response["choices"][0]["message"]["content"]

if __name__ == "__main__":
    print("Paste your code below (Press Enter twice to submit):")
    user_code = []
    while True:
        try:
            line = input()
            if line == "":
                break
            user_code.append(line)
        except EOFError:
            break

    code_snippet = "\n".join(user_code)
    print("\nReviewing your code...\n")
    review = review_code(code_snippet)
    print(review)

📌 Step 3: Running the Code Reviewer

To run the script, simply execute:

python reviewer.py

Then, paste your code into the terminal and press Enter twice to get a review.

That’s how I built my AI-powered code reviewer! 🚀

Next Steps? Try running it on different code snippets and see how it performs.

Let me know if you use it! 😊

🚧 PS: Want more AI tips, tricks, and in-depth tutorials? Stay tuned for the next issue, where I’ll share something more useful for you.

Got a favorite AI prompt? Or an AI tool you swear by?

Let me know (@Manas Moon)—I’m always excited to learn new ways to use AI.

Once again, you can subscribe to Codexai for more such cool AI prompts.

Manas | Founder @Codexai

Cheers xx!! 🥂

How to be confident in coding?

Manas Moon — Sat, 25 Jan 2025 18:25:46 +0000

Remember your first time riding a bike? At first nervous, unsure, fumbling to figure it out, maybe you finished early a few times. But then, one day, you just got it.

Coding works the same way.

Confidence will only come (in coding) when you’ve solved X numbers of quality questions.

Running away from your problems won’t build confidence—it never will. Facing your mistakes head-on will. Learn. Improve. Grow.

When you use this prompt, you’re doing more than solving questions. You’re proving to yourself, little by little, that you can figure things out. Confidence isn’t the absence of fear—it’s knowing you have what it takes to move forward, no matter what.

Keep practicing, and watch as your coding "bike" turns into a rocket ship.

Workflow

Let’s say you've learned four key Python topics: Variables, Data-types, Loops, and Functions. Now, to truly master them and build confidence, use this prompt. It will provide output like this:

Here’s your premium prompt:

I am learning [TECHNOLOGY] and studied these topics today:   

[LIST OF TOPICS YOU WANT QUESTIONS ON]  

I don’t feel confident yet because I haven’t practiced solving enough questions.  

Please act as a [TECHNOLOGY PROFESSIONAL] with over 10 years of experience. Create [NUMBER OF QUESTIONS] questions to:  
-- Test my understanding.  
-- Challenge me with real-world problems.  
-- Improve my confidence in these topics.  

Present the questions in a table with these columns:  

1. Question: The question or problem to solve.  
2. Concepts Involved: Key ideas or skills the question tests.  
3. Pre-requisites: Knowledge needed before solving the question.  

Start with basic questions and move to advanced ones. Each question should help me learn and improve.

This prompt is your ultimate cheat sheet! Just replace the placeholders—[TECHNOLOGY], [DESIGNATION/ROLE], [DURATION], and others—with your specific needs, and let it supercharge your learning.

It’s like handing your brain the ultimate power-up.

Follow these steps, and you’ll be building amazing projects, boosting your confidence, and mastering skills faster than you think.

Don’t procrastinate—use this today! Your learning journey deserves no delay.

(Imagine your future self high-fiving you for starting now.)

This isn’t just a tool; it’s your flexible companion. Adjust it to match your unique journey.

And listen, if you ever get stuck, don’t stress—even the best coders in the world face bugs. (Debugging is like arguing with your code and you will be always right in the end. Don’t worry!)

To get more such premium prompts, subscribe to Codexai

🚧 PS: Want more AI tips, tricks, and in-depth tutorials? Stay tuned for the next issue, where I’ll share something more useful for you.

Got a favorite AI prompt? Or an AI tool you swear by?

Let me know (@Manas Moon)—I’m always excited to learn new ways to use AI.

Manas | Founder @Codexai

Cheers xx!! 🥂

Use this AI prompt to learn any new technology, FAST!

Manas Moon — Wed, 22 Jan 2025 07:42:21 +0000

Are you tired of tutorial hell, watching endless videos, and still not feeling confident? No one can understand this situation better than me, because I was also in that same situation some time back.

But one day I was cleaning my almirah and found one of my old dairy where I used to write mental models used by successful peoples, there I found 2 concepts that had helped me improve my situation. Those mental models were:

First Principle Thinking Method & Project Based Learning Method.

Then I thought, “hmm why not use that mixture to solve my own coding problems” (problems here refers to our miserable situation).

Before this, I was drowning in so many courses, projects, and roadmaps which made me feel so overwhelming, like I was making some kind of progress but I was not.

But then this prompt (that I came up with after 27 trials) helped me build one path to follow, break concepts into fundamentals and apply them in building projects.

That’s why today, we’ll create a roadmap and list of real-life projects so you can master any tech stack with just one powerful prompt.

Workflow

Here’s your premium prompt:

I want to learn [TECHNOLOGY] completely but, I don't want to go through tutorial hell.

So, firstly, create a beginner's roadmap for becoming a [DESIGNATION/ROLE] in [DURATION] months using [TECHNOLOGY], assuming I don't know anything and want to learn while dedicating [HOURS PER DAY] daily.

Create the roadmap in detail and provide the reference links too.

Also, assume yourself as a professional tutor of [TECHNOLOGY] and craft a series of projects that help me learn [TECHNOLOGY] from scratch.

You must understand that I don't know anything in [TECHNOLOGY/PROGRAMMING] and please create a list of [NUMBER OF PROJECTS] projects where every required concept is included and taken care of.

I know creating a long project list upfront might be overwhelming, but having the list will help me pace myself accordingly. Adjustments can be made as needed during the journey.

I also want to learn by building real-life projects weekly or as often as possible, although it's not mandatory.

Additionally, I want to learn using First Principle Thinking and Project-Based Learning, combining the two methods for deeper understanding:

1. Project-Based Learning Method: Learn by building projects and solving real-world problems.
2. First Principle Thinking Method: Break down concepts into fundamental components for better understanding.

The projects should progress in complexity, with each new project building on the concepts from the previous ones while introducing new topics.

I prefer text-based tutorials over video tutorials, but a mix of both works.

Provide this in a tabular format with the following columns:

1. Name of the Project
2. Concepts Used
3. Prerequisites
4. New Concepts Learned
5. Reference Links

Start by creating the curriculum for each foundational technology or skill related to [TECHNOLOGY], followed by the project list. Include foundational projects if necessary for prerequisites (e.g., [FOUNDATIONAL TECHNOLOGIES]).

Don't just start creating the curriculum. First, tell me what you understood by analyzing the above prompt. If you have any questions, don't hesitate to ask. I will answer everything you need clarification on.

This prompt is like a cheat sheet for your learning journey! Just replace the placeholders—[TECHNOLOGY], [DESIGNATION/ROLE], [DURATION], and others—with your specific needs. Then, let the magic unfold.

Follow the roadmap step by step, and you'll be building cool projects, gaining confidence, and mastering your chosen technology in no time.

While it provides most of what you'll need, think of it as a flexible framework rather than a rigid rulebook. You can tweak and adjust it as you go to suit your evolving goals and needs.

🚧 PS: Want more AI tips, tricks, and in-depth tutorials? Stay tuned for the next issue, where I’ll share something more useful for you.

Got a favorite AI prompt? Or an AI tool you swear by?

Let me know (@Manas Moon)—I’m always excited to learn new ways to use AI.

Manas @Codexai.com

Cheers xx!! 🥂

5 Uncommon Advices from one beginner coder to another beginner coder!

Manas Moon — Thu, 25 Apr 2024 20:51:35 +0000

Hello and Welcome Everyone!
Whether you are a beginner or an expert in programming.
If you are a beginner then learn from this and if you are an expert then your input is very valuable for all of the beginners.
First of all, why I'm qualified to write this post and why this will become your final blog to start.

My name is Manas Moon and I myself is not an expert in programming.
In fact I have less than 1 year of experience in this field, a pro-procrastinator and not mastered a single programing language until now.
But I'm improving myself day-by-day and I have taken guidance & advice from many industry experts and I have a habit to writing their advices in my notes.
In-short I'm sharing my personal notes of getting started in programming, this advices have helped me so far. Hope it does for you too.

⚠️ Disclaimer: Not everything written in this post will work for you, try it yourself first and whatever works for you, that works for you & ignore the rest as your ex ignores you.

Read this blog post till the end and you will have you own roadmap for getting started.
Okay then, Let's get started.

Advice 1: Don't waste your time searching for the best roadmap.

The best roadmap is one that helps you reach towards your goals.

10 people will have 10 different roadmaps but that roadmap is based on their experience, what have worked for them.

But what about us? Will that same roadmap work for us? May be! But for majority of us, it will not.
It will not because they created the roadmap according to challenges they faced throughout “their journey”.

So what to do??

There's a website I personally follow specific for roadmaps called as “roadmap.sh” where all the roadmaps are available.
You can check it out, if you like.
Here's the link: ▶️ https://roadmap.sh/

Every roadmap is great, and every roadmap will lead you towards some destination if followed till end.
The main question is “Is that your desired destination?”. If yes, Great! If not then change the path, not the goal.

You only care of completing the roadmap completely from the start to end, don't change the path between the journey.
The things that are left between your decided path can be learnt wherever needed. Everything is available on the internet you just have to search for it.

Advice 2: Your first programming language will never be your last programming language.

This advice is given to me by Rahul bhaiya who has 8+ years of experience in tech, so we can think this advice as a legit advice as other advices.

He told me that when he got his first job at that time he only knew one language that is Python, but the company uses Typescript.
He was very confident with his python skills but it was almost useless in that company because nobody works with python.

So he has to learn a completely new language from scratch.

Remember this little story of Rahul bhaiya because it will help you understand the next advice well.

He also told me when he switches the company every single time he has to learn a new language.
This advice is also give me by my many other mentors, so I believe in this.

As I remember he also told me that in tech if you stopped learning then both your personal as well as financial growth starts decreasing.
So, Keep Learning and Keep Growing.

What is your thoughts on this? Please comment.

So moving towards the next advice and Don't forget Rahul Bhaiya.

Advice 3: Master the basics and everything else will take care of it.

As you know everything has to start from zero. No matter how far or how big you have to become, but you have to start it from zero.

I'm a daily user of “First Principle Thinking Method”, so according to me:

Coding is nothing but a medium to give instructions to our computer so that they can work for us. Coding is nothing different than simple languages like English, Hindi and other languages. Also, English is nothing but the combination of 26 alphabets.

So similarly programming languages are also almost similar to each other, the main difference is how they are written (i.e. syntax)

Remember Rahul bhaiya?

The time he taken to learn new language from scratch is between 1-2 months only.

How he did it?
By mastering the basic concepts.

He also knew that coding is nothing but a language with which we can communicate with computers.

So he masted the basic concepts like variables, data types, functions, loops, statements, etc. That helped him learn everything with an unbelievable pace.

If the base is strong, the building stays long. ~ Manas Moon

Advice 4: Everyone tells you what have helped them, you must try yourself first before believing it.

You don't have to believe everything that has come to your ears. If you got time you should first try it out and then make any conclusions about it.

If you ask any advice from anyone, then will have their biased opinion based on their own personal experiences.

And you know, everyone got their own problems (meaning everyone's life is different). Their advice may or may not work for you, but if you try their advice then you will definitely find out what you whether that advice is working for you or not.

I have written less in this section because you can understand most of the context by reading the title and above part of this section.

So moving towards the last but not the least , final advice…

Advice 5: Celebrate the smallest progress you have made toward your goals.

It's hard to keep going when there is no one watching you work.

You have to become your THAT ONE friend that supports you, mentor that guides you and motivator that motivates you to keep going.

The best way nowadays for celebrating your progress is by Building In Public

You can use X(Twitter), LinkedIn, Instagram or any other social media platforms to share and celebrate your progress publicly.

I can tell from my personal experiences, with time you will make friends from all over the world that will help you whenever you are in need.

Keep your consistency on point and the rest is sorted.

So these are my 5 uncommon advices for beginner coders.

I have not included the general advices but you have to follow them too.

Advices like :

Be more consistent with your task completions.
Build more cool projects.
Practice, practice and practice more.
And more useless generic tips. (just ignore them) You must take care of them too.

Progressing on your coding journey may seem daunting at times, but remember that every step forward, no matter how small, is a step in the right direction.

Follow the advices that works for you. Keep Coding, Keep Learning, and Keep Pushing Yourself to new heights.
Thank you for reading.

Subscribe to my newsletter to get notified whenever new blog comes, here's the link : https://theprojecthub.substack.com/

Happy Coding!

Storytime: Funny Coding Confessions.

Manas Moon — Wed, 10 Apr 2024 18:23:37 +0000

Hey everyone! How's it going, fellow coders, tech enthusiasts, and all you curious minds out there? Take a seat, grab a drink, and get cozy because today, I'm about to spill the beans on my wild ride through the world of coding.

But before we jump in headfirst, let me give you the lowdown on who I am.

I'm Manas, just a regular 20-year-old dude with big dreams and an even bigger love for all things tech. And let me tell you, I've got a tale that's bound to keep you on the edge of your seat!

Meeting Ankush

It's one of those regular evenings where the weight of coding deadlines feels like it's crushing your soul. Desperate for a breather, I decide to step out and take a leisurely stroll to the neighborhood Pan shop, hoping that a quick smoke break would provide the much-needed respite.
Little did I know, this mundane trip would turn into one of the most enlightening encounters of my life.

As I entered the shop and reached for my pack of cigarettes, I couldn't help but notice a man, slightly older than me, already lost in the haze of his own thoughts, puffing away contently. His name was Ankush.

Now, I'm not usually one to strike up conversations with strangers, but there was something about Ankush that piqued my curiosity. Maybe it was the way he carried himself with such confidence, or perhaps it was the subtle aura of wisdom that seemed to envelop him. Whatever it was, I found myself blurting out a simple "Hey, mind if I join you?"

To my surprise, Ankush responded with a warm smile and a nod, gesturing to the empty seat beside him. And just like that, our unexpected camaraderie began.

As we kicked back and relaxed, swapping stories and chuckles, the conversation naturally gravitated towards our shared passion for programming. Now, let me tell you about Ankush – he wasn't your average coder. With over two decades of experience tucked under his belt, he was more like a coding guru. And boy, did he have stories to share.

As our chat gained momentum, Ankush started unraveling the tapestry of his programming journey. And let me tell you, it was quite the ride – filled with laughter, disbelief, and maybe even a few tears. From quirky mishaps that left us doubled over in laughter to heart-stopping disasters that had us on the edge of our seats, Ankush had truly experienced the full spectrum of coding adventures.

The Case of the Missing Semi-Colon

Ah, let me regale you with the tale of the missing semi-colon – a saga that had both Ankush and me doubled over in laughter.

He told me,

He was buried deep in the trenches of a high-pressure project, with deadlines breathing down his neck like an impatient boss. Sound familiar? Well, it gets better.

In his rush to appease the relentless demands of the client, he dashed off a chunk of code faster than you can say "syntax error." But here's the kicker – he neglected to sprinkle in those pesky semi-colons where they rightfully belonged.

Now, I know what you're thinking – how could one tiny punctuation mark cause so much chaos?
Oh, you have no idea.

As Ankush hit the compile button, expecting smooth sailing ahead, chaos erupted like a volcano on a bad day. Error messages spewed forth from the depths of the compiler, flooding the screen with cryptic warnings and nonsensical gibberish.
Poor Ankush, in a state of panic, frantically sifted through lines of code, searching for the elusive culprit.

Hours turned into eternity as he embarked on a quest of epic proportions – to uncover the whereabouts of the missing semi-colon. It was a journey fraught with frustration, despair, and more than a few colorful expletives.
But lo and behold, after what felt like an eternity, Ankush emerged victorious, clutching the errant semi-colon like a prized trophy.

Lesson learned, my friends: always dot your i's and cross your t's – or in this case, remember to dot your semi-colons.
As Ankush so eloquently put it, "A missing semi-colon may seem insignificant, but in the world of coding, it's the difference between smooth sailing and a shipwreck." Wise words, indeed.

The Database Disaster

But wait, let me share with you another story that had both Ankush and me gripping our seats with dread – the Database Disaster: When Data Goes Wild.

Ankush leaned in, his eyes reflecting the intensity of the memory. "Imagine this," he said, his voice tinged with disbelief. "A seemingly innocuous update query meant to tweak a few records in the database. Simple task, right? Well, not quite."

With a flicker of frustration crossing his face, Ankush recounted the events that followed. A minuscule typo nestled within the lines of code, invisible to the naked eye, but potent enough to unleash chaos upon the unsuspecting database.
Instead of executing as intended, the query morphed into a digital wrecking ball, careening through the rows and columns with reckless abandon.

Thousands of entries fell victim to the database's newfound autonomy, each alteration sending shockwaves through the system. Ankush found himself thrust into a whirlwind of panic as frantic calls from irate clients flooded in, emergency meetings sprung up like wildfire, and sleepless nights became the norm in a desperate attempt to salvage what remained of the project.

"It was a nightmare scenario," Ankush admitted, his tone heavy with the weight of the memory. "But you know what they say – sometimes, the greatest lessons come from the most unexpected of places."

And indeed, from the ashes of that database disaster emerged a newfound respect for the power of precision in coding and a humbling reminder of the importance of meticulous attention to detail.

Finding Humor in Failure

As he spun his tales of coding catastrophes, I found myself drawn not just to the mishaps themselves, but to the man behind them. His ability to find humor in the face of failure was nothing short of inspiring.

He is a seasoned programmer, battle-hardened by years of debugging and troubleshooting, sitting across from me with a grin on his face as he recounted the countless times he'd fallen flat on his face in the world of coding. It was a refreshing reminder that even the best of us stumble from time to time.

As he spoke, it became clear that Ankush didn't view failure as a mark of incompetence, but rather as a rite of passage. Each bug, each glitch, each colossal screw-up was not a reflection of his skills as a programmer, but an opportunity to learn and grow. And let me tell you, he seized those opportunities with gusto.

"In the world of coding," he declared with a twinkle in his eye, "there are no mistakes, only happy accidents waiting to be discovered." His words struck a chord with me, resonating deep within my fledgling programmer's soul.

In that moment, I realized that failure wasn't something to be feared or avoided at all costs – it was an integral part of the journey towards mastery. It was the messy, unpredictable path that led to innovation and breakthroughs.

So the next time you find yourself face to face with a bug that just won't budge or a project that seems destined for disaster, remember Ankush's words of wisdom. Embrace the chaos, find the humor in the madness, and keep pushing forward.

Because in the end, it's not about how many times you fall down – it's about how many times you get back up and keep on coding.

Embracing the Imperfect Perfection of Coding

As my unexpected chat with Ankush wrapped up, I found myself feeling a mix of emotions – a blend of inspiration and determination swirling within me like a storm. You see, coding isn't just about lines of code or algorithms; it's about embracing the messy, imperfect journey that comes with it.

Sure, there are moments when coding feels like an uphill battle, where bugs seem to multiply faster than you can squash them. But therein lies the magic – in those moments of struggle, we find opportunities to learn and grow. It's in those late-night debugging sessions and hair-pulling frustrations that we discover our resilience and tenacity.

So here's to embracing the chaos, to laughing in the face of failure, and to forging ahead with a heart full of passion and curiosity. Because isn't that what makes the journey worthwhile? It's not just about reaching the destination; it's about relishing every twist and turn along the way.

As I bid farewell to Ankush and stepped out into the cool evening air, I felt a renewed sense of purpose coursing through my veins. I couldn't wait to dive back into my code editor, armed with newfound wisdom and a determination to tackle whatever challenges lay ahead.

And who knows? Maybe one day, I'll look back on this moment – this collection of coding confessions shared over a pack of cigarettes at the local Pan shop – with fondness and nostalgia. Perhaps I'll have my own stories of epic fails and triumphant successes to pass on to the next generation of wide-eyed coders.

But until then, I'll continue on my journey with an open mind and a willingness to embrace the imperfect perfection of coding. So here's to the highs and lows, the wins and losses, and everything in between. Here's to the wild and wonderful world of ones and zeros – may we navigate it with laughter, humility, and a whole lot of heart.

So there you have it, folks – my biggest programming fails as a 20-year-old, as seen through the eyes of a seasoned veteran named Ankush.

Until next time, happy coding!

Explaining HTML Forms to a 5 year old with syntax!

Manas Moon — Mon, 08 Apr 2024 17:25:49 +0000

Hello, fellow web enthusiasts!

Welcome to our cozy corner of the internet, where we're about to embark on an exciting journey into the realm of HTML forms.
Whether you're just starting out on your web development adventure or looking to brush up on your skills, you've come to the right place.

Now, before we jump into the technical nitty-gritty, let's take a moment to imagine something fun.

Picture yourself hosting a fabulous party, filled with laughter, games, and your closest friends. As the host, you want to make sure everyone has a blast, right?

Well, think of HTML forms as your secret weapon for keeping the party vibes going strong on your website!

In this blog post, we'll be your friendly guides as we explore the ins and outs of working with HTML forms.
But fear not, we won't be delving into the dry, dusty depths of coding jargon.

Instead, we'll be taking a playful approach, breaking down complex concepts into bite-sized nuggets of knowledge that even a five-year-old could understand.

So grab your favorite beverage, get comfy, and let's embark on this thrilling adventure together.
By the end of our journey, you'll be armed with the skills and know-how to create captivating forms that'll dazzle and delight your website visitors.

Are you ready? Let's dive in!

Explaining Forms to a 5-Year Old.

Alright, imagine you're having a big party with all your friends.
You want to make sure everyone has a great time playing games, right?
So, to find out which games they like best, you create a special box.
This box is magical because it lets your friends write down their favorite games inside it. Now, this box is like a super cool thing called an HTML form.

Just like the magic box at your party, an HTML form on a website lets people type in their answers to questions or fill in information.
Once they've written down what they want, they can send it back to you, just like when your friends put their game choices in the magic box at your party.

So, basically, HTML forms are like magical boxes on websites where people can share their thoughts or give information back to the website owner.
Cool, right?

Setting Up Your HTML Form.

Okay, so now let's talk about setting up your magical box, also known as an HTML form.
It's a bit more technical, but don't sweat it, we'll make it super easy!

So, in your website's code, you begin by using something called the form tag.
It's like drawing a big empty box on your webpage where you'll put all your form stuff, like where people can type their names or choose their favorite color.

Here's how it looks in HTML syntax:

See? It's like saying, "Hey, I'm creating a space for people to fill in their info or make selections."

Inside this box, you can add different things like spaces where people can write words (we call those "text fields"), boxes they can tick if they like something (that's a "checkbox"), or buttons they can click to submit their answers.

Think of it as setting up the stage for your magical box where all the fun stuff will happen!
Cool, right?

Adding Input Fields.

Now, we're going to add the actual places where people can write down their answers in our magical box, also known as an HTML form.

So, imagine you have a piece of paper, and you want your friends to write their favorite games on it.
You'd create little spaces on the paper where they can write, right?

Well, in our form, those spaces are called "input fields."
Here's how we do it in HTML code:

In this code, the label is like a tiny sign that tells your friends what to write, like "What's your favorite game?"

And the input is where they actually write their answers. It's like a blank space on the paper.

Oh, and see that for="favorite-game" in the label tag?

It's like pointing to the specific space where your friends should write. It's like saying, "Hey, this label goes with this input!"

So when someone clicks on the label, it focuses on the input field, just like when you point to a space on your paper.

Simple, right? We're making progress!

Submitting the Form.

So, imagine your friends have finished writing down their favorite games on the paper you gave them.
Now, they need to give you back the paper so you can see what they wrote, right?

Well, in our magical HTML form, we need a way for people to give us back their answers too!

Here's where the fun part comes in: we add a special button called a submit button.
It's like the "I'm done, here you go!" button for your friends' answers.

Check out how we do it (syntax):

See that button with type="submit"?
It's like a magical button that sends all the filled-out information back to you when clicked.
It's like saying, "Okay, I'm done writing, here are my answers!" And when they click it, yeeee!
Their answers zoom back to you.

Pretty cool, huh?
With just a click of a button, you get to see what everyone wrote.
And that's how our magical HTML form works its wonders!

Handling the Submitted Data.

So, imagine your friends have happily filled out their favorite games on the paper and clicked the magical "submit" button.
Now, what happens next?

Well, in web development, we usually send all that juicy information to a special place called a server for processing.
But hey, let's keep things simple for now. Instead of diving into the technical details, let's do something fun!
We'll just show your friends what they wrote right back on the screen. (Using JavaScript)

Here's how we do it in our code:

Now, in this little block of JavaScript, we're doing something cool!

We're grabbing what your friends wrote in the input field (that's their favorite game) and showing it back to them in a pop-up message called an alert box.
It's like saying, "Hey, I got your message! Your favorite game is [whatever they wrote]!”

Oh, and see that return false; at the end?
It's like saying, "Hold on! Let's not send the form away just yet. We want to show your answer first!"
So, it stops the form from doing its usual thing of disappearing off to a server.

And that's it! Your friends get to see their answers right away, without leaving the page.
How awesome is that? We've made our HTML form come to life with just a few lines of code!

And there you have it, friends!
You've now got the hang of the basics when it comes to working with forms in HTML.
Think of forms as the magic boxes of the web—they're like friendly helpers that let people interact with your website by sharing information.

Now, armed with this newfound knowledge, it's time to unleash your creativity!
Feel free to experiment with different types of fields, like text boxes, checkboxes, and buttons.

Go ahead and have fun building all sorts of awesome forms for your web projects!

Whether you're creating a simple contact form or designing a survey for your users, remember that the possibilities are endless.
So, don't be afraid to let your imagination run wild and make your forms as unique and engaging as can be.

With a bit of practice and creativity, you'll be crafting beautiful and user-friendly forms in no time.
So go forth, my fellow web wizards, and may your forms be ever magical!

Thank you for reading.

If you enjoyed diving into the fascinating world of HTML forms with me today, then you won't want to miss out on the exciting content coming your way on @thepracticaldev my blog @manasmoon_

Be sure to hit that follow button to stay updated on all the latest posts, tutorials, and tips for mastering web development.

And hey, let's stay connected beyond the blogosphere! Swing by my social media profiles to join the conversation, share your insights, and be part of our growing community of aspiring developers.
Checkout my all social accounts here : https://linktr.ee/ManasMoon

Together, we'll embark on an incredible journey of learning, creativity, and endless possibilities. See you there!
Manas Moon

Understand Float and Flexbox in Comparison with Books.📚

Manas Moon — Wed, 27 Mar 2024 11:57:47 +0000

Before diving deep into the topic, Float and Flexbox in one line:👇🏻

Float and Flexbox are two ways to put things side by side on a webpage.

Like arranging books on a shelf!📚

Floats are like magic magnets that stick elements next to each other.
But sometimes they act tricky and need extra commands to behave!

Flexbox is designed to make arranging things easy-peasy,
Like putting books in neat rows and columns.

With Floats, you gotta set sizes for everything, which can be a bit confusing.
It's like measuring each book's width and height before placing them!

Flexbox automatically adjusts sizes and positions,
Like a super flexible bookshelf that moves things around to fit!

Floats sometimes struggle with making all books on the shelf the same height.
It's like some books grow taller and others stay short!

But Flexbox solves this!
It's like magic making all books the same height, so your shelf looks neat and tidy!

With Floats, making things look good on phones and tablets can be tricky.
It's like rearranging books for different bookshelves!

But Flexbox is naturally good at fitting things into different spaces.
It's like a shape-shifting bookshelf that adjusts for any room!

In short, Floats are like old-school magic tricks, while Flexbox is the modern superhero making web layouts a breeze!

A personal tip,
You don't have to learn all these properties,
Understand the basics and PRACTICE by making projects.

If you find this short blog useful,
Follow @manasmoon_ for more such tips and tricks.
And take your projects to the next level! 💻✨