SERKUT YILDIRIM’s Post

💬 Day 9 of My Java Learning Journey ☕ Today, I explored one of the most underrated but powerful concepts — Flowcharts. 🧩 Before writing a single line of code, flowcharts help visualize how logic flows step by step. They make problem-solving clearer and coding much smoother. Here’s what I learned 👇 🔹 Purpose of Flowcharts: To represent the logic of a program visually — making it easy to debug, plan, and explain. 🔹 Common Symbols: ➡️ Oval — Start/End ➡️ Parallelogram — Input/Output ➡️ Rectangle — Process ➡️ Diamond — Decision 🔹 Examples I practiced: ✔️ Flowchart to find the largest of two numbers ✔️ Flowchart to calculate Simple Interest ✔️ Flowchart for swapping two numbers 💡 Insight Gained: Coding is not just typing syntax — it’s thinking in logic. Flowcharts train your brain to think like a computer before you ever touch the keyboard. #Day9 #LearnInPublic #NamasteJava #JavaLearningJourney #100DaysOfCode #Flowcharts #ProblemSolving #ProgrammingBasics #LogicBuilding #CodeNewbie #JavaForBeginners #BackendDevelopment #DeveloperJourney #WomenInTech #LearnJava #CodeConsistency #KeepCoding #BuildInPublic

C# Constants vs Readonly – What Developers Really Need to Know Most developers know the textbook definitions — but the confusion usually comes when deciding which one to use in real scenarios. And if an interviewer asks this question, they’re not looking for definitions… They’re evaluating your understanding of when and why to use each. Let’s simplify it with practical explanations and examples. 👇 🔒 1. const – Compile-Time Constants A const value must be assigned a constant expression at compile time. This means anything requiring runtime evaluation is not allowed. ❌ Value type example (invalid) void Calculate(int Z) { const int X = 10; const int Y = X + Z; // ❌ Error: Z is only known at runtime } ❌ Reference type example (also invalid) const MyClass obj1 = null; // ✔ Allowed const MyClass obj2 = new MyClass(); // ❌ Not allowed (requires runtime allocation) ✅ When to use const Use const when a value: • Never changes • Must stay identical across all builds and environments • Is guaranteed to be known at compile time Common examples: • Error codes • Application-wide static values ⸻ 🔧 2. readonly – Runtime Constants A readonly field can be initialized: 1️⃣ When declared 2️⃣ Inside the constructor This makes it perfect for values that are fixed after object creation but determined at runtime. ✅ When to use readonly Use readonly when a value: • Should not change after initialization • Depends on runtime inputs • Varies per instance Common examples: • Configuration values loaded at startup • Immutable object properties • Instance-level identifiers ⸻ 💡 Final Thought Choosing between const and readonly isn’t just about syntax — it’s about writing clean, predictable, and intentional code. • Use const for compile-time, unchanging values. • Use readonly for runtime-initialized, per-instance constants. Mastering this distinction leads to better design and more robust C# applications. 🚀 #Developers #CleanCode #ProgrammingTips #SoftwareDevelopment #DeveloperCommunity #LearnToCode

Beyond Fowler's Refactoring: Martin Fowler's Theatrical Players kata is brilliant for teaching refactoring mechanics. But there's a gap between refactored code and production-ready code. I created an advanced version demonstrating patterns that bridge this gap. What Fowler teaches (essential foundation): - Extract Method - Split Phase - Replace Conditional with Polymorphism What's still missing: 1. Type Safety : Fowler uses strings for play types like "tragedy" and "comedy" - one typo and you have a runtime bug. The advanced version uses type-safe enums where the compiler catches typos before the code even runs. IDE autocomplete works, refactoring is safe, and invalid types are impossible to create. 2. Value Objects Fowler uses primitive integers for both money and credits. Problem: you can accidentally add money to credits and the code compiles fine - but it's completely wrong. With value objects (Money and VolumeCredits), mixing incompatible types becomes a compile-time error. The type system prevents an entire class of bugs. Plus you get currency awareness, proper formatting, and precision handling built-in. 3. Domain Boundaries Three separate layers: Event Domain (what happened - performances, invoices) Calculation Domain (business rules - pricing strategies) Presentation Domain (formatting - text, HTML, JSON) This separation means you calculate once and can format the same results as text for email, HTML for web, JSON for API, or PDF for reports. No calculation logic duplication. 4. Make Illegal States Unrepresentable through the type system: Can't create negative audience sizes Can't create empty play names Can't mix money with credits Can't create invalid play types The compiler enforces business rules. Bugs are caught at compile-time, not in production. Check it out for learning production worthy code practices. Full implementation on GitHub (link in comments) Detailed blog post with examples and comparisons (link in comments) #SoftwareArchitecture #DomainDrivenDesign #Java #Refactoring #TypeSafety #CleanCode

Learn to write production ready code. Move beyond the common refactorings you know and learn to think on a higher plane.

Explaining Automation by Sharing Your IDE Let's talk about that. Last week, I decided to refresh my memory on design patterns in automation.  I watched a talk from a skilled developer who compared his Java code with and without design patterns. He showed his IDE. Showed the BEFORE, with the "quick and dirty" approach. Then he showed the other way around, when you use the 𝘍𝘢𝘤𝘵𝘰𝘳𝘺 𝘱𝘢𝘵𝘵𝘦𝘳𝘯 and the well-beloved 𝘗𝘢𝘨𝘦 𝘖𝘣𝘫𝘦𝘤𝘵 module. In meetings, I often see people try to explain automation by scrolling through endless lines of code. Then it hit me. That is awful.  No one can follow it, and no one learns anything. If you want to explain architecture, 𝘀𝗵𝗼𝘄 𝘁𝗵𝗲 𝗶𝗱𝗲𝗮, 𝗻𝗼𝘁 𝘁𝗵𝗲 𝘀𝘆𝗻𝘁𝗮𝘅. We have today our beloved genAI to throw up the code for us.  Use a diagram, a workflow, or even a whiteboard. It's the understanding of a concept that is missing, it's the strategy that we would need in out future.  If the code really matters, share a link to the repo, than I can check specific chank of your code there, to drill it down. 💭 What do you think about “code walkthrough” in a meeting?

#CleanCode #SoftwareCraftsmanship #Java #BestPractices Part 14: The Code Quality Ecosystem #14 Clean Code in Practice: Tools and Techniques Clean code isn't just a philosophy—it's a practice backed by tools and processes that ensure maintainability and reduce technical debt. 🛠️ Code Quality Automation: · Static Analysis: SonarQube, Checkstyle, PMD, and SpotBugs integration · Code Formatting: Google Java Format and pre-commit hooks · Dependency Analysis: Maven/Gradle dependency updates and security scanning · Architecture Enforcement: ArchUnit for architectural rule testing 📈 Technical Debt Management: · Debt Tracking: Identifying and quantifying technical debt · Refactoring Strategy: Boy Scout Rule and dedicated refactoring sprints · Code Review Culture: Effective pull request practices and checklists · Knowledge Sharing: Pair programming and mob programming sessions 🎯 Maintainability Metrics: · Cyclomatic Complexity: Keeping methods simple and focused · Testability Indicators: Dependency injection and single responsibility · Documentation Quality: README-driven development and living documentation · Onboarding Time: How quickly can new developers contribute? Code quality isn't a luxury—it's the foundation that allows teams to move fast without breaking things. #CleanCode #SoftwareCraftsmanship #Java #BestPractices

🚀 You use ArrayList every day. But do you know what’s hiding under the hood? 👇 We all use this line every day 👇 List<String> list = new ArrayList<>(); Here’s the real inheritance chain 👇 Iterable     ↓   Collection (extends Iterable)     ↓   AbstractCollection (implements Collection)   ↓   List (extends Collection)     ↓   AbstractList (extends AbstractCollection, implements List)     ↓   ArrayList (extends AbstractList, implements List,       RandomAccess, Cloneable, Serializable) 💡 Quick takeaways: ✅ Iterable is what makes enhanced for-loops (for-each) possible. ✅ AbstractCollection & AbstractList provide skeleton implementations so subclasses only need to implement key methods. ✅ ArrayList adds dynamic resizing, fast lookups, and cloning support. ⚙️ Hidden Insight: Your everyday ArrayList isn’t just a list — it’s a layered masterpiece of interfaces + abstract classes + marker interfaces that make it fast, flexible & reliable 🚀 #Java #Coding #DeveloperTips #ArrayList #Programming #LearnJava #OOP

This text provides a concise yet comprehensive explanation of the foundational principles of Object-Oriented Programming, but what makes it particularly insightful is how it connects each concept not just to coding technique, but to software quality attributes—like modularity, security, flexibility, and maintainability. It subtly highlights that OOP isn’t only about organizing code but about managing complexity and change —the true challenges of software engineering.

✨ New article in my LINQ series! Before building our own LINQ methods, we’re taking one smart step first: unit testing. In this post, I show how to use xUnit to test the behaviour of two essential LINQ methods: Where and Any. It’s a simple and powerful way to define how our methods should work before we write a single line of implementation code. ✅ Learn how to: - Set up xUnit in a .NET project - Write your first LINQ-style tests - Prepare for implementing MyWhere and MyAny Check it out here 👇 🔗 Read the full article here: https://lnkd.in/dRsvY4-k #dotnet #csharp #linq #programming #developers #testing