Why You Need to Build Projects in Coding

I had bookmarked over 100 tutorials on automation. Never opened a single one. Then in one week, I learned Make, Typeform, Carrd, Airtable, and Softr—and tied them all together. What changed?  I had a project to build. Most of us try to learn tools in isolation. We watch courses. We follow tutorials. We bookmark resources we’ll never revisit. But tools don't make sense in a vacuum. You can't learn how to connect five different platforms by studying them one at a time. That's where project-based learning changes everything. When you have something real to build, the tools stop being abstract concepts. They become solutions to specific problems you need to solve right now. Here's why project-based learning is the fastest way to master new tools, or indeed, new subjects: 1: Projects give you a clear finish line. - Without a project, you'll wander down every rabbit hole. - With a project, you learn exactly what you need—nothing more. - The goal pulls you forward when curiosity tries to pull you sideways. Clarity comes from constraints, not endless possibilities. 2: Projects force you to connect the dots between tools. This is where the real learning happens. Make handles automation. Typeform captures input. Airtable organizes data. Softr turns it into an app. Carrd builds the landing page. Alone, each tool is interesting. Together, they solve a problem you couldn't solve before. Project-based learning doesn't just teach you tools. It teaches you how to tie them together into something that works. 3: Projects compress your learning curve dramatically. - I bookmarked 100+ tutorials and learned nothing. - One real project taught me five tools in seven days. - Theory builds confidence. Projects build competence. You don't learn to swim by reading about water. 4: Projects teach you what theory never will. Courses teach you features. Projects teach you decisions. Should you automate this step or do it manually? Which tool fits best here? How do you troubleshoot when two platforms won't talk to each other? These are questions you only encounter when you're building something real. I finished 80% of my project in one all-nighter. Then I spent four days stuck on the last 20%. That struggle taught me more than any tutorial ever could. 5: The best learning project is one you care about. - Pick something you want to exist. - Make it small enough to finish in a week. - Make it real enough to push through when it gets hard. Passion combined with quick, small wins is the antidote to quitting. #life #upskilling #business

"People hiring don't care about your projects." False. In fact, some job posts ask for them. When I used to look at dev applications, I would occasionally come across resumes that included a list of projects. When I saw projects that had similar, or identical, tech stacks, I dug in to know more about them. Specifically, what problems candidates solved, and how. I saw how projects were created. I looked at documentation, code quality, and so on. It gave me a glimpse at someone's ability to do the things they'd do at work. I also made sure my team leads reviewed those projects to make sure I didn't miss anything. When everything looked good, I'd move that person on to a phone screen.  Sometimes I'd look at resumes that were unimpressive and got impressed by the projects in their portfolio, typically a GitHub profile. If you can't create projects because you don't have time, open source contributions are a great alternative. If you include projects on your resume, it will only help. Especially for early career engineers, recent grads, and bootcampers. The people that need to see your projects, will. -- 👋 Hi, I'm Jonathan. I help job seekers in the tech industry land interviews and offers. #techjobs #jobseekers #portfolio #projects #protips

Copy a project from GitHub or YouTube to land a job… That’s not how it works anymore. “What project should I add to my resume?” That’s one of the most common questions I get from juniors. And honestly, I’ve asked the same thing in the past. Back then, the default answer was simple: “Build an e-commerce website.” “Make a full-stack MERN app.” “Do something with ML “ So we did. Copied projects from GitHub. Followed 3-hour YouTube tutorials. Changed a few colors. Added our name to the footer. Done. It worked… kind of. But here’s what I’ve realised now, especially with how fast AI is evolving: Your resume doesn’t need another “portfolio project.” It needs a “problem solver.” These days, anyone can use Cursor or bolt to build a full-stack app in a few hours. What makes your project different? Not the tech. The problem it solves. Let me give you an example: You want to send 100+ personalized emails to students. Mail Merge? Already exists. But your emails are landing in spam. So you build a small Python script that sends emails like a human would. Slowly. With better delivery. Tiny project. Few lines of code. But real value. That’s what recruiters remember. Not how many lines of code you wrote. But how many problems you solved. You can use AI. You should use AI. But don’t be just a copy-paster. Understand what you’re building. Learn the stack. Because your project should say one thing.. “I don’t just code. I solve.”

Coding Portfolios are like resumes. Most of them look the same and it’s very hard to tell if the candidate is any good from a “vanilla” portfolio. However, a half finished project that is trying to solve a real problem is far more interesting and persuasive than another front end “about me” project with fancy CSS. So if you want to become a professional coder, stop focusing on ‘filling up the portfolio’. That is “window dressing”. Instead focus on building usable things that address a real-life use case.  You don’t need many.  One or two “real” projects is enough to showcase how you think, and how you build solutions to ambiguous problems. I know there’s lots of suggestions on HOW to find projects.  And most suffer from one problem – they look at other examples and copy them.  Consequence?  Everything starts to look the same and you dont stand out in the job market. And again, your focus shifts to window dressing rather than learning how to use the tool (code) to solve real life problems. Here’s how I learn a new technology. I start with Why. Learn WHY I’d use it, not just WHAT it does.  Why helps us understand WHEN we should choose to use it. Then I zoom out and find real life things that can be represented by that “tool”. Learning for loops? Why would you ever need to loop over something? Oh…when you want to go through a list of things.  WHY would you want to do that?  Maybe to find one or more things in that list. To extract. To validate. To check. To update. Ok what lists do I encounter everyday that ARE NOT the obvious ones. ( Yeah - no shopping lists and TODO lists) How about lists of: 🗓 Birthdays? 💹 Investments? 💼 Jobs you would like? 🌴 Trees in the park? 🎼 Songs that last only 1 week on the charts? 💻 APIs that return other lists? As you start to think like this you will start to think about how you’d define these objects and what data you would need to store and retrieve and process. Now you’re starting to think like a coder. You’re starting to understand all the times you would want to loop over a list. This way, as you dig deeper you will learn the tools, but most importantly you will learn HOW to use them. And each little micro project from your real life becomes a project for your portfolio that is different, unique to your experience and which you are PERSONALLY connected to. That will help a lot more than just building the same portfolio projects everyone does. 👉 One tip: don’t think of projects as “products” or “startup ideas”. That’s too grandiose and overwhelming.  Small micro projects are better to learn a new technology, because each technology was designed and created to solve a specific class of problems.  Understand those classes of problems … not just the tech. Learn how the tool solves that class of problems. Repeat. #careerchange #softwarengineer

For folks who use GitHub and are in early stage careers and hope to add GitHub as a value add to your profile - here is a note. If interviewing for an SDE role, GitHub projects that don't solve a problem and are just a coding exercise are not very helpful. This may sound perplexing but it needs to be said. : Hiring managers and tech leads (like me) look for problem-solvers. A repository full of practice exercises might show you can write code, but it doesn’t demonstrate that you can build impactful solutions. ► How to Make Your Projects Stand Out 1. Frame Them as Solutions: Instead of presenting your project as "just another app," position it as a business solution or a tool that solves a real-world problem. For example: - Instead of “Expense Tracker App,” say, “A tool for freelancers to manage and categorize expenses for tax season.” - Instead of “Weather App,” frame it as, “A weather app optimized for agricultural planning with location-based crop suggestions.” 2. Highlight the Problem It Solves: Every great project starts with a problem. Make it clear what problem you identified and how your project addresses it. - Example: “This tool was designed for small business owners who struggle with automating their daily sales tracking.” 3. Show Quantifiable Value: Numbers tell a story. Include metrics like: - How much time/money the solution saves. - How many users it could potentially impact. - Any test data or feedback you’ve collected. - Example: “This app reduced invoice processing time by 35% in a real-world test case.” 4. Document It Well: A project is only as good as its README. Include: - A brief description of the problem it solves. - Key features. - Instructions on how to run/test it. - Screenshots, GIFs, or a demo link to bring it to life. Having a GitHub full of clone apps or unfinished side projects sends the wrong signal. It doesn’t show creativity, ownership, or impact, it shows you can follow tutorials, and that’s not what companies hire for. Instead, invest your time into one or two high-impact projects that: - Solve real-world problems. - Show off your ability to understand user needs. - Demonstrate your thought process, design skills, and technical execution. So, take a step back, revisit your GitHub, and think: - Does this project solve a problem? - Can I explain its value to someone outside of tech? - Would I hire someone based on this work? If the answer isn’t “yes,” it’s time to rethink how you approach your projects. Remember: One impactful project > 100 clones. Focus on impact, not just output.

💡 𝗘𝘃𝗲𝗿𝘆 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝘀𝗵𝗼𝘂𝗹𝗱 𝗱𝗼 𝘁𝗵𝗶𝘀 𝗼𝗻𝗰𝗲 𝗶𝗻 𝘁𝗵𝗲𝗶𝗿 𝗰𝗮𝗿𝗲𝗲𝗿 -- 𝗶𝘁 𝘄𝗶𝗹𝗹 𝗰����𝗮𝗻𝗴𝗲 𝗵𝗼𝘄 𝘆𝗼𝘂 𝘀𝗲𝗲 𝘆𝗼𝘂𝗿 𝘄𝗼𝗿𝗸 𝗳𝗼𝗿𝗲𝘃𝗲𝗿! 🚀 The one career-defining experience every developer should have: 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗳𝗿𝗼𝗺 𝗮𝗯𝘀𝗼𝗹𝘂𝘁𝗲 𝘇𝗲𝗿𝗼. Not maintaining an existing system. Not adding features to a mature product. Not inheriting code, pipelines, and databases. But starting with nothing --a blank canvas -- opening a blank editor, staring at that empty repo, laying the first brick yourself, and turning an idea into a living, working piece of software. It’s a challenge that pushes you out of your comfort zone and reshapes the way you think about engineering, ownership, and impact. --- 𝗪𝗵𝘆 𝗱𝗼𝗲𝘀 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿? Because nothing humbles you more -- and nothing grows you faster -- than realizing how many moving parts come together before the first feature even sees the light of day. --- 𝗛𝗲𝗿𝗲’𝘀 𝗮 𝗾𝘂𝗶𝗰𝗸 𝗰𝗵𝗲𝗰𝗸𝗹𝗶𝘀𝘁 𝗼𝗳 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂’𝗹𝗹 𝗳𝗮𝗰𝗲: 🔐 Authentication (JWT, OAuth, sessions) 🗄️ Database schema, migrations & permissions 🌱 Environments: dev, staging, prod - with secrets 🛠️ Unit, integration & end-to-end tests ⚡ CI/CD for automated deployments 📜 API design with clean docs (Swagger / OpenAPI) 🛡️ Security basics: validation, HTTPS, rate limits, CORS 📦 Docker & deployment to cloud (AWS / GCP / Azure) 📊 Logging, error monitoring & caching (Redis / Memcached) 🧹 Code quality with linters, formatters & static analysis 📖 A README your future self will thank you for --- 💡 𝗬𝗼𝘂 𝗱𝗼𝗻’𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗺𝗮𝘀𝘁𝗲𝗿 𝗮𝗹𝗹 𝗼𝗳 𝘁𝗵𝗲𝘀𝗲 -- 𝗷𝘂𝘀𝘁 𝘁𝗼𝘂𝗰𝗵 𝘁𝗵𝗲𝗺. The goal is to understand what it really takes to move an idea from nothing to “it’s live.” Once you’ve gone through this journey, you’ll never see your daily work the same way again. You’ll respect the invisible layers holding projects together. And you’ll know what it truly takes to ship end-to-end. --- 🔥 𝗜𝗳 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲𝗻’𝘁 𝗱𝗼𝗻𝗲 𝘁𝗵𝗶𝘀 𝘆𝗲𝘁, 𝘀𝗲𝘁 𝗶𝘁 𝗮𝘀 𝗮 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗺𝗶𝗹𝗲𝘀𝘁𝗼𝗻𝗲. It might just be the most eye-opening project of your career.

3 reasons why you should work on side projects as software developer. Full cycle experience First year as a software developer, I only worked on codebase that others have setup. Only added new APIs to existing API gateway setup, only added new fields to database created by someone else. When I had to setup a typescript repository by my own, it took me a week to get everything ready. At that point I realized it’s important to get a full cycle experience. With a side project, I setup frontend repo, hosted frontend using cloudfront, setup API gateway, setup web server repo, setup a new database. Every step taught me a lot about intricacies of running a full stack application from scratch. Full stack experience Developers in company usually gets to work on specific stack - backend or frontend, hardly getting a chance to work full stack. Working on side projects will give you exposure to everything - UI design, how browser works, frontend to backend communication, API design, application logic, database design, asynchronous processing. Try new technologies When I started as an sde at amazon, i was amazed to see how each Aws services can be used as Lego block to build real world applications. Aws has 100+ services, each with unique set of features. Unless you have a means to explore, you can’t really navigate through plethora of services and features provided by each. And side projects are a great way to explore these and build something fruitful out of it.

𝐇𝐨𝐰 𝘁𝗵𝗲 𝐫𝐢𝐠𝐡𝐭 𝐩𝐫𝐨𝐣𝐞𝐜𝐭 𝘄𝗶𝗹𝗹 𝗵𝗲𝗹𝗽 𝘆𝗼𝘂 𝗰𝗿𝗮𝗰𝗸 𝗪𝗮𝗹𝗺𝗮𝗿𝘁, 𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁 𝗮𝗻𝗱 𝗧𝗼𝗽 𝗠𝗡𝗖'𝘀. These days, most resumes look the same becoz everyone’s showcasing similar projects, often built by following the same online tutorials. So, what makes your resume stand out in in thousands people? Here's is the key things which you need to keep in mind before making any project: 1. 𝐒𝐨𝐥𝐯𝐞 𝐚 𝐫𝐞𝐚𝐥 𝐩𝐫𝐨𝐛𝐥𝐞𝐦: Even a small one. start building things I actually needed, A notes manager for my class. A budget tracker to stop overspending. A project reminder tool. These weren’t groundbreaking. But they were genuine and that authenticity stood out in interviews. 2. 𝐆𝐨 𝐣𝐮𝐬𝐭 𝐛𝐞𝐲𝐨𝐧𝐝 𝐲𝐨𝐮𝐫 𝐜𝐨𝐦𝐟𝐨𝐫𝐭 𝐳𝐨𝐧𝐞: One new concept in every project. - React then try Firebase - HTML/CSS then learn deployment etc… It proves that you're growing, not just repeating tutorials. Recruiters love seeing genuine project rather copied one’s. 3. 𝐓𝐞𝐥𝐥 𝐚 𝐬𝐭𝐨𝐫𝐲 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞 𝐩𝐫𝐨𝐣𝐞𝐜𝐭: Ask yourself: - Why did I build this? - Who did it help? - Did anyone actually use it? Stories are remembered. Dashboard aren’t. 4. 𝐊𝐞𝐞𝐩 𝐢𝐭 𝐀𝐜𝐭𝐢𝐯𝐞 (𝐢𝐟 𝐩𝐨𝐬𝐬𝐢𝐛𝐥𝐞) Add a README. Share it on LinkedIn. Polish the UI. Push an update. A live project,even a smaller makes your resume way more attractive than an inactive GitHub repo. 5. 𝐖𝐡𝐲 𝐈 𝐫𝐞𝐜𝐨𝐦𝐦𝐞𝐧𝐝 𝐭𝐡𝐢𝐬? Because I’ve lived both sides. I’ve built projects just for marks. And I’ve built things that got me interviews, referrals, and confidence. #Internship #Resumeshortlisting #Projectswithpurpose #SoftwareEngineering #Developerjourney #Portfolio #Hr #Softwaredevelopment #Resume #Github

BIG Reality Check for Students! Your CGPA DOES NOT decide your job offer anymore. Recruiters today look for proof of skill, and the best part is that you don’t need a 9.0 CGPA to prove that. Here’s what companies actually check now: - Hackathon projects: can you build under pressure? - Open-source work: can you collaborate and write clean code? - Kaggle competitions: can you apply logic to real data? - Consistent GitHub commits: do you keep learning? - Your LinkedIn profile: can you communicate what you’ve built? These are the signals that get even average students interviews at Google, Amazon, and Microsoft. If you are 1st, 2nd, or 3rd year, here’s a practical roadmap to follow this semester. Do one item from each column every month, and document it publicly. 1) Build (projects + hackathons) - Start: Projects World, Project Learn, Coding N Concepts. - Hackathons: Devpost, Major League Hacking. 2) Practice & compete (algorithms, data) - LeetCode or InterviewBit daily, Kaggle for data projects. 3) Contribute & commit (collaboration) - Find beginner issues on GitHub, join 1 open-source repo, push small daily commits. 4) Visibility & applications (tell your story) - Polish a LinkedIn post that explains your project, use OffcampusJobs4U and remote job boards to apply. So stop chasing grades you can’t change. Start building proof you can show.