Rana MS’ Post

A senior software developer once told me that understanding code is different from copying code. That truly hit me while learning coding. I noticed that I could follow tutorials, but the moment I tried it on my own, I got stuck. That’s when it clicked that watching is not the same as understanding. So I changed my approach. Instead of just following along, I started pausing more, asking AI why each line of code exists and not just accepting it blindly, and trying things my own way even if it breaks. It’s slower, 𝘺𝘦𝘴 but it makes sense. If you’re learning to code or anything whatsoever, this might help: Don’t rush tutorials. Focus on understanding what’s happening and why. That’s where the real growth is. #SoftwareDevelopment #LearningJourney #JavaScript #BuildInPublic #Coding #ProgrammingLanguages #AtLeast3HoursOfDailyCoding

That's spot on, Isaac Akerele In addition, for a vibe coder, it's all rosy and good when AI does the work and then you want something specific but couldn't achieve it. You reminded me of a scenario when i was working on a backend php script on Owode and needed to fix a bug in the code. Rolled in my code to DeepSeek AI and was happy with the new fix, but to my surprise, all my existing class and id were overruled. Like you said, Having deep understanding of what you're doing or want to do goes a long way. And for new ones learning to code at this age, use your initiative as you use learn and ask questions to understand and not just code to solve a problem. That way, you'll be better fixer and builder as you grow. This experience taught me AI can make a fool of anyone, even seasoned developer, at times #BuildInPublic #LearningJourney #founderstory

Being a Software Engineer is basically Fixing one bug… Creating three new ones… Then acting surprised like: “Who wrote this code?” 👀 (it was me. 10 minutes ago.)😂 Some days you feel like a genius 😎🤠 Other days, a missing semicolon will humble you real quick 😅 But honestly? That’s the beauty of it. - You keep learning. - You keep building. - You keep breaking things… and fixing them better. At the end of the day, it’s not just about code it’s about solving problems and growing a little every single day. If you’re a developer, what’s the funniest bug you’ve ever had? #SoftwareEngineer #CodingLife #Debugging #TechLife #Developers #BuildInPublic #100DaysOfCode #Programming #LinkedInPolls #JavaScript #CareerGrowth #Coding #Developer #Coder #ComputerScience #SoftwareEngeering

🚀 As a Developer, Writing Code is Easy… Writing Good Code is the Real Skill! In today’s fast-paced tech world, it’s not enough to just build applications — we must build them clean, maintainable, and secure. That’s where SOLID Principles come into play 💡 🔹 #S – Single Responsibility Principle One class → One responsibility 🔹 #O – Open/Closed Principle Open for extension, closed for modification 🔹 #L – Liskov Substitution Principle Subclasses should be replaceable 🔹 #I – Interface Segregation Principle Prefer many specific interfaces over one large 🔹 #D – Dependency Inversion Principle Depend on abstractions, not concrete implementations ✨ Following these principles helps us: ✔️ Write clean and readable code ✔️ Improve maintainability ✔️ Reduce bugs ✔️ Build scalable and secure applications #Java #SOLIDPrinciples #CleanCode #SoftwareDevelopment #CodingBestPractices #Developers #Programming

🚀 Master OOPs Like a Pro & Write Scalable Code! 💡🔥 Object-Oriented Programming isn’t just a concept — it’s a superpower for developers 🧠⚡ From Encapsulation 🔒 to Polymorphism 🎭, from Inheritance 🧬 to SOLID Principles 🏆 — mastering OOP helps you: ✅ Write clean & maintainable code ✅ Build scalable applications 🚀 ✅ Think like a software architect 🧠 ✅ Crack interviews with confidence 💼 💡 Pro Tip: Great developers don’t just write code… they design systems! 👉 Start thinking in Objects, not just functions. 👉 Follow DRY, KISS & YAGNI principles. 👉 Prefer Composition over Inheritance. 🔥 The difference between a beginner and a pro? Code that works vs Code that scales! Let’s level up together 💪🚀 Medium - https://lnkd.in/g4xnbMs9 Google Blogs - https://lnkd.in/gwZ6Twub Personal Site - https://lnkd.in/gX7vyv64 Medium - https://lnkd.in/g4xnbMs9 #OOP #Programming #SoftwareDevelopment #CleanCode #SOLID #Developers #CodingLife #Tech #FullStackDeveloper #RubyOnRails #100DaysOfCode #DevCommunity

While building a feature recently, I faced a simple but interesting problem: 👉 Given a date (day, month, year) as input, how do we find the day of the week? At first, I explored Zeller’s Congruence — a mathematical formula to solve this. It works, but honestly… it felt a bit lengthy and not very intuitive for real-world development. Then I came across something much cleaner 👇 Using Java 8’s LocalDate API: Create a date using LocalDate.of(year, month, day) Get the day using getDayOfWeek() Format it using getDisplayName(TextStyle.FULL, Locale.ENGLISH) ✨ That’s it — no complex math, no manual calculations. 💡 What I learned from this: Modern tools are not just about reducing code They encapsulate complex logic internally They allow developers to focus more on design, readability, and problem-solving ⚡ Big realization: As developers, we often try to solve everything from scratch. But knowing when to use built-in abstractions is just as important as knowing the core logic. Every day I code, I discover something new. And that’s what makes development exciting — learning, building, and constantly improving. 🚀 Have you ever replaced a complex solution with a much simpler built-in feature? Would love to hear your experience 👇 #Java #Java8 #SoftwareDevelopment #ProblemSolving #LearningJourney #CleanCode #Developers

Most people think coding is about writing logic. But it's something deeper… It’s about thinking clearly when things don’t work. I spent hours debugging a small issue, not because it was hard, but because my thinking was messy. The moment I slowed down, broke the problem and questioned every assumption… The solution appeared in minutes💡 Good developers don’t just code fast. They think better. And that’s what I’m working on every single day. #SoftwareDevelopment #CodingJourney #ProblemSolving #Java #Learning

Topic: Learning from Code Reviews Code reviews are one of the fastest ways to grow as an engineer. Every review is an opportunity to: • Learn better approaches • Understand design decisions • Improve code quality • Share knowledge within the team But the value depends on how we approach them. Good code reviews: • Focus on improvement, not criticism • Ask questions instead of giving orders • Suggest better alternatives • Keep long-term maintainability in mind The goal is not just to approve code. The goal is to make both the code and the developer better. What’s the best feedback you’ve received in a code review? #CodeReview #SoftwareEngineering #Learning #BackendDevelopment #Java

Most developers get stuck not because the problem is hard. They get stuck because they don’t have a clear approach. Here’s the exact method I use to solve any coding problem: 1. Understand the problem deeply → Read it twice. Don’t rush. 2. Identify input & output clearly → What are you given? What do you need to return? 3. Start with brute force → Always begin simple. 4. Optimize step-by-step → Use patterns like hashmap, two pointers, stack 5. Write clean code → Readable > clever 6. Dry run with examples → Catch mistakes early 7. Debug like a detective → Trace step by step, don’t panic 8. This approach works for: • LeetCode • Interviews • Real-world debugging This single mindset shift will improve your problem-solving faster than solving 100 random questions. Strong developers don’t just code fast. They think clearly. Follow CodeWithIshwar for daily developer growth - Ishwar Chandra Tiwari | CodeWithIshwar #CodeWithIshwar #leetcode #developers #programming #softwareengineering #coding #webdevelopment #java #javascript #100DaysOfCode

🚀 Lately, I’ve been diving into SOLID Principles and how they impact backend development. At first, it felt theoretical… but once applied, everything started making sense. 🔹 S — Single Responsibility → Keep classes focused (less chaos) 🔹 O — Open/Closed → Extend without breaking existing code 🔹 L — Liskov Substitution → Replace components without issues 🔹 I — Interface Segregation → No unnecessary dependencies 🔹 D — Dependency Inversion → Build flexible, loosely coupled systems 💡 Why this matters in backend? 👉 Cleaner and maintainable code 👉 Easier debugging & testing 👉 Better scalability as system grows 👉 Less tight coupling between services ⚡ Biggest learning: Good code is not just about making it work… it’s about making it easy to change and scale. Still learning, but this mindset shift is powerful. #BackendDevelopment #Java #SystemDesign #CleanCode #SOLID #Learn