DEV Community

SAR
SAR

Posted on

Coding/Dev

#software

Coding/Dev: The Honest Guide to Not Screwing Up Your First Year

Article illustration
Photo: AI-generated illustration

Hook - The Brutal Truth About My First 100 Days

I still remember my first day at Infosys in 2018, bhai. My mentor told me, "Beta, you'll write your first production bug within 6 hours." I laughed it off, thinking, "Kya baat kar raha hai?" But, six hours later, I had pushed code that crashed our client's payment gateway. The cost? ₹2.3 lakhs in downtime. That's when I realized — coding isn't about writing perfect code; it's about writing code that doesn't bankrupt your company. So, what can you do to avoid making the same mistakes I did?

Contemporary interpretation of modern technology concept
Contemporary interpretation of modern technology concept

Getting Started - Stop Overthinking, Start Building

Let's cut through the noise, yaar. You don't need a ₹15,000 course from Udemy or that fancy MacBook Pro M3. What you need is a ₹35,000 Lenovo IdeaPad (which I used for 2 years) and the willingness to type npm install 47 times until you understand what's happening. I mean, think about it - how many of us have wasted time and money on courses and gadgets, only to still be clueless about coding? It's time to stop overthinking and start building, bhai.

Start here, no excuses:

  1. Pick ONE language. Not five. ONE. I recommend JavaScript because:

    • It runs everywhere (frontend, backend, mobile)
    • Companies actually pay for it (average ₹8-12 lakhs for JS devs in Bangalore)
    • The platform doesn't require a PhD to navigate

  2. Install Node.js 20.10.0 LTS (not the latest, trust me on this)

# Download from nodejs.org - current LTS is 20.10.0
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs
Enter fullscreen mode Exit fullscreen mode


Make sense?

  1. Create your first project: 
// app.js
const http = require('http');
const server = http.createServer((req, res) => {
 res.writeHead(200, {'Content-Type': 'text/plain'});
 res.end('Hello, startup founder who thinks coding is easy!');
});
server.listen(3000, () => console.log('Server running on port 3000'));
Enter fullscreen mode Exit fullscreen mode

Yes, that's it. No frameworks, no build tools, just pure Node.js. Most tutorials will make you install Express, React, MongoDB, Redis, and Kafka before you even understand HTTP. Don't be that guy, bhai. What's the point of having all these tools if you don't know how to use them?

Contemporary interpretation of modern technology concept
Contemporary interpretation of modern technology concept

Essential Tools - What Actually Works in 2024

Let me save you ₹50,000 in tool subscriptions, yaar. Here's what I actually use daily:

VS Code 1.84.2 (Free) - Not WebStorm, not Sublime. VS Code because:

  • Extensions like Prettier 3.2.5 (auto-formatting), ESLint 2.4.0 (linting), GitLens 14.5.2 (Git superpowers)
  • Integrated terminal that doesn't crash like iTerm
  • GitHub costs ₹600/month but saves 200+ hours/year

Git 2.43.0 - Install via Homebrew on Mac or winget on Windows:

git config --global user.name "Your Name"
git config --global user.email "youremail@gmail.com"
git config --global core.editor "code --wait"
Enter fullscreen mode Exit fullscreen mode

Postman 10.21 (Free tier sufficient) - For API testing. Yes, curl works but when you're debugging at 2 AM, GUI helps.

Docker Desktop 4.26.1 - When your code works on your machine but breaks on production. ₹0 for personal use, ₹5,000/year for teams.

Figma (Free) - For designing UI before you waste 40 hours coding something that looks terrible.

Don't install: IntelliJ IDEA (₹15,000/year unless company pays), Notion (overrated), 15 different VS Code themes. Pick one setup and master it, bhai. It's like trying to learn too many programming languages at once - you'll end up being a master of none.

Modern visualization: modern technology concept
Modern visualization: modern technology concept

Learning Path - The Anti-Tutorial Approach

Everyone will tell you to follow the "complete roadmap." Here's what actually works:

Month 1-2: JavaScript Fundamentals

  • Variables, functions, async/await (not promises yet)
  • DOM manipulation with vanilla JS
  • Build a calculator that actually works

Month 3-4: Backend Basics

  • Express.js 4.18.2 (install: npm install express@4.18.2)
  • REST APIs, middleware, error handling
  • Connect to MongoDB Atlas (free tier) or PostgreSQL on ent is a

Real project example:

// server.js
const express = require('express');
const app = express();
app.use(express.json());

let todos = []; // In-memory [id: Dat](https://supabase.com/), don't judge

app.get('/todos', (req, res) => res.json(todos));

app.post('/todos', (req, res) => {
 const todo = { id: Date.now(), ...req.body };
 todos.push(todo);
 res.status(201).json(todo);
}); You know what I mean?

app.listen(3000, () => console.log('Todo API running'));
Enter fullscreen mode Exit fullscreen mode

So, what's the best way to learn, bhai? Is it by following tutorials or by working on real projects? I'd say it's a mix of both. You need to have a solid foundation in the basics, but you also need to apply that knowledge to real-world problems.

Communities - Where Real Learning Happens

Reddit and Discord aren't just for memes, yaar. Here's where I actually grew:

Discord Servers:

  • The Programmer's Hangout (~120k members) - Real devs, real advice
  • JavaScript Mastery (paid community ₹1,500/month) - Worth it if you're serious
  • Dev.to community - Better than Twitter for technical discussions

Local Meetups:

  • Bangalore JavaScript (monthly, usually at Microsoft office)
  • Mumbai Software Crafters (small but high-quality)
  • Your college's coding club - Don't skip this

Twitter/X Accounts to Follow:

But here's the thing - 90% of "developers" in these communities just consume content. You need to contribute, bhai. Answer questions, share your screw-ups, write about what you learned. I got my second job because I answered a Docker question on Dev.to that impressed the hiring manager. So, don't be shy - put yourself out there and learn from others.

Pro Tips - Lessons from Screwing Up Daily

Debugging > Writing Code

I spent 6 months thinking I needed to write more code. Wrong, yaar. I needed to debug better. Learn Chrome DevTools, understand the Network tab, master console.log strategically. One console.log(err) saved me more time than rewriting entire modules. It's like trying to find a needle in a haystack - you need to know where to look.

Version Control isn't Optional

Still saving files as "final_final_v2_copy.js"? Stop, bhai. Git isn't just for teams. It's your undo button for life. Commit every working state. Branch for every feature. Merge with confidence. You don't want to lose your work because you didn't use version control, trust me.

Read Documentation, Not Tutorials

MDN Web Docs > W3Schools. Official React docs > random YouTube video. I know, tutorials are easier. But docs teach you to think, tutorials teach you to copy-paste. When you're stuck at 11 PM with production down, docs will save you, yaar. So, take the time to read the documentation - it's worth it.

Build in Public

Post your code on GitHub, even if it's ugly. Write about what you learned. I shared my first React app (a terrible todo list) and got 3 job interview calls. Companies want developers who communicate, not coding robots, bhai. So, don't be afraid to share your work - it's a great way to learn and get feedback.

Learn Testing Early

Jest 29.7.0 + React Testing Library. Write tests for your functions:

// math.test.js
test('adds 1 + 2 to equal 3', () => {
 expect(1 + 2).toBe(3);
});

test('filters active users correctly', () => {
 const users = [
 { id: 1, active: true },
 { id: 2, active: false }
 ];
 const activeUsers = users.filter(user => user.active);
 expect(activeUsers).toHaveLength(1);
});
Enter fullscreen mode Exit fullscreen mode

What I'd Do - Your Action Plan

If I had to restart today, here's my exact playbook:

Week 1: Environment Setup

  • Install WSL2 if on Windows, iTerm2 if on Mac
  • VS Code with Prettier, ESLint, GitLens extensions
  • Git configured globally
  • Node.js 20.10.0 installed

Week 2-4: JavaScript Basics

  • Complete "JavaScript30" by Wes Bos (free)
  • Build 3 mini-projects: calculator, weather app, todo list
  • No frameworks, just vanilla JS

Month 2: Backend Introduction

  • Follow "The Net Ninja" Node.js playlist (not the 3-hour crash course)
  • Build REST API for your todo list
  • Deploy on Render.com free tier

Month 3: Database Integration

  • Learn PostgreSQL basics (free on Supabase)
  • Connect your API to database
  • Learn basic SQL queries

Month 4-6: Specialization

  • Pick React OR focus on backend depth
  • Build one substantial project (portfolio website, blog, something personal)
  • Apply to 10 jobs even if you feel underqualified

Month 7-12: Polish & Network

  • Contribute to open source (start with documentation)
  • Attend 6 meetups
  • Write 12 blog posts about your learning journey

The key? Consistency over intensity, yaar. Code for 1 hour daily rather than 12 hours on weekends. Your brain needs time to digest concepts. So, don't try to cram too much into one day - take it slow and steady.

Remember: 90% of developers are winging it, bhai. You're not behind, you're just more honest about it. Now go build something that breaks, fix it, and repeat. And most importantly, don't be afraid to ask for help - that's what the community is for, yaar.

Disclosure: Some links in this article are affiliate links. I may earn a commission if you purchase through them — at zero extra cost to you. This helps keep the content free.

Top comments (0)