Akram

I asked my hacker, friend to go through the security flaws in my vibe coded app His response: 💀

I knew a guy from a tier-3 college who dreamed of becoming a software engineer. Low CGPA.😭 Poor attendance . Average coding skills. Almost no confidence. When placements started, he couldn’t solve even basic tech interview questions. That’s the wakeup call. Instead of giving excuses, he made one simple decision: For a few months, nothing mattered except coding. No paid bootcamp. No shortcuts. Just DSA, projects, and long hours with his laptop. Most days were frustrating. Many days felt like zero progress. But he kept showing up anyway. Slowly, patterns appeared. Logic improved. Confidence returned. Months later, he cracked interviews and became a software engineer with a decent offer. People called him talented. They didn’t see the boring consistency behind it. Truth: In tech, you don’t need to be extraordinary. You just need to stay when it’s hard, silent, and nobody is clapping. That’s where engineers are made.

Day 10 learning JavaScript... - I looked into Object.freeze() - I learned primitive and complex types, how they store values and access their memory location. - Reviewed existing stuff I learned. #dev #javascript PC: Pinterest.

I still can't believe i don't have any physical friends. My phone fell yesterday and the screen went completely blank. I also forgot to charge my PC, so for a whole 24 hours I was without any device. It honestly felt like a part of me was missing. 🥹

What's one project you've built that taught you more than any course, tutorial, or certification ever could? Sometimes a single messy project teaches more than 100 hours of watching videos.

The cards are done. ✅ 8 hours of coding. A day well spent. 🤍 Next: mobile responsiveness and footer. If all goes well, i will deploy it on Vercel this Sunday.🚀

I spent 4 months working on this... Introducing social0.app Post your content everywhere in seconds. ✅ Publish to 9 social platforms ✅ Schedule everything from one dashboard ✅ Upload once, publish everywhere ✅ Built for creators, founders & marketers 🎉 Launch offer: 33% off the Pro plan for a limited time. I'd love your feedback ❤️

Concurrency is tough. but learning these will make it easy for u: 0. Thread Safety (race conditions) 1. Locks (Mutex, RW Locks) 2. Optimistic vs pessimistic locking 3. Lock-free/CAS (compare & swap) 4. Deadlocks (detection/prevention) 5. Thread pools 6. Futures & async 7. Backpressure (producer/consumer) 8. Context switching overhead 9. Event loops vs threads

My Story 2024 November : 😎 I left my hostel and moved to my brother-in-law's house. That one decision changed my career. I had one goal: 🎯 Crack Kubernetes. Land a better job. So I made a promise to myself. ⏰ Every weekday: • 5:00 AM – 7:00 AM: Study before work. 🌙 Every evening: • 2 hours of revision. • Hands-on labs. • Quizzes. 📅 Weekends: • More labs. • More practice. • More consistency. I followed this routine for 90 straight days. No shortcuts. No excuses. I completed my Kubernetes course and kept practicing until I was confident. Then came the job hunt. • Built a strong Naukri profile. • Applied directly on company career pages. • Used ChatGPT to improve my resume, self-introduction, and interview answers. • Practiced speaking in front of a mirror with my laptop camera on until my answers felt natural. Then came my first interview. I got rejected within 10 minutes. It hurt. But I didn't quit. I noted every mistake and worked on it. A few days later, I got another interview. This time I told myself: "This is my moment." I stayed calm. Answered confidently. Trusted my preparation. The result? ✅ Cleared all technical rounds. ✅ Cleared the HR round. ✅ Received an offer with a 100% salary hike. The biggest lesson? Success wasn't luck. It was 90 days of discipline, consistency, and refusing to give up after one rejection. If you're trying to switch jobs, remember: One rejection doesn't define your future. Your next interview could change your life.

@swarupdcs Been there. 😄 One thing that clicked for me was treating array methods as verbs: map transforms, filter selects, reduce accumulates. Picking the right one makes the code read almost like English.

Finished another automation project today Built an AI-powered complaint handling workflow in Make that reads Gmail complaints, categorizes them, logs them to Google Sheets, routes them and sends confirmations automatically. Learnt a lot about AI-powered information extraction...

I came from a non-CS background in school, so when I entered college, Computer Science felt overwhelming. Throughout my 2nd year, I kept telling myself, "Maybe I'm just not made for CS." I watched others progress while I doubted whether I was capable of becoming a developer. Then I took a break and spent time reflecting. I realized something important: no one else was going to change my life for me. The only person who could change my story was me. So I started learning again—one step at a time. The more I built, the more I discovered that I didn't hate Computer Science. I had only been afraid of it. Now, I genuinely enjoy CS more than I ever enjoyed Biology. If you're doubting yourself because you're from a non-CS background or feel like you're "behind," don't let that define you. Your starting point doesn't decide your future. Your willingness to keep learning does.

Interviewed a Senior Full Stack Engineer today. Knew React, Node.js, PostgreSQL, Redis — everything. Then I asked: "Your app works perfectly for 1,000 users. You get featured on Product Hunt. 50,000 users sign up in 3 hours. The app crashes. You have 30 minutes before the CEO calls. Walk me through exactly what you do." Silence. Your turn: 1,000 users → fine ✅ 50,000 users → crashed ❌ 30 minutes ⏱️ What's your step-by-step response? 👇 (The first 3 things you do reveal your entire engineering mindset)

Underrated life advice: Pick the city before the job. The place you live fuels your energy, your pace, and your future network. The job is just what funds it. I chose Bangalore because so many people recommended it as the best place for startups, builders, and opportunities. So far, I think I made the right decision. What do you think? Was Bangalore the right choice? 👇

You do NOT need 2 years to become hireable as a junior developer. You do need 3 focused months. A realistic 3-month plan: Month 1: 🔹 Pick one path: frontend, backend, or full-stack 🔹 Strengthen your fundamentals 🔹 Build 1–2 solid projects 🔹 Stop jumping between random tutorials Month 2: 🔹 Polish your GitHub, CV, LinkedIn, and portfolio 🔹 Add a clean README 🔹 Add a live demo 🔹 Make your features easy to understand 🔹 Make sure you can explain your code clearly 🔹 Start applying to jobs that actually match your stack Month 3: 🔹 Apply consistently every week 🔹 Tailor your CV to the role 🔹 Practice interview questions 🔹 Do mock interviews 🔹 Improve your weak areas 🔹 Build or upgrade one more project if needed Focus on this: 🔹 consistency over intensity 🔹 clarity over trying to be everything The goal in 3 months: Look like someone worth interviewing. Save this if you’re trying to get your first dev job.

I’ve spent years building projects on my own. Now, I want to build with people. If you need a frontend developer for your startup, side project, or open-source project, I’m available to collaborate. Please repost if you can - it might reach the right person. ❤️

Hi, I'm Tara Frontend dev. Mechanical Engineering student. Currently breaking things on the backend too This intro probably won't go viral. Here it goes anyway 🙃 If you're in tech, let's connect

Day 81 of Learning Backend Worked on the reaction system for Nexus chat today. Added a reactions array to my MongoDB message schema and created a Socket.IO event that: – Receives messageId, emoji, and username – Finds the message in MongoDB

There are two ways to learn something new: 1. Read everything first, then start building. 2. Learn the basics, start building, make mistakes, figure things out, and keep learning along the way. I personally prefer the second approach. I don't know why, but that's how I've learned most things :)

Leetcode is like chess. It's a high IQ coded activity but in fact it's all memorizing patterns. People don't win at chess because they out-think you, they win because they out pattern match you. Only at the highest level does some IQ come into it, Leetcode has no such level.