EL YAZID ISMAILI’s Post

C++ _Functions Part2 تم شرح Passing Arguments :   Pass by Value Pass by Reference Default Parameters  Passing Arrays to Functions Static Variables & Global variable & Local Variables #CPP #Programming #Functions

emplace_back(...) and push_back(...) are not always interchangeable. emplace_back(...) Builds the object directly inside the container by forwarding constructor arguments. push_back(obj) Adds an existing object to the container, with a copy or move depending on what is passed. This difference is often minor, but it matters more when: → objects are expensive to construct or copy → the code is performance-sensitive → you want clearer intent in the code Do you have a team guideline for when to use emplace_back versus push_back? #cpp #cplusplus #performance #stl #cleancode #softwareengineering #programming

💡 C++ Tip — Day 7/100 auto can silently change your type ⚠️ int x = 10; const int& ref = x; auto a = ref; // int ❗ (const & lost) auto& b = ref; // const int& ✅ ⚡ auto removes references and top-level const by default. That means: auto → makes a copy auto& → keeps reference const auto& → safest for read-only access Using auto blindly can lead to unexpected copies & bugs #CPP #CPlusPlus #ModernCPP #Programming #CodingTips #100DaysOfCode #Developers #SoftwareEngineering #CodeQuality #TechCommunity #LearnCPP #AdvancedCPP

I have options for dynamic generic array in C. Which one should I choose ? 1. Void * 2. Macros Confidential Section #C #Programming #Lowlevel #Systems #DSA

Ever wonder how the C++ compiler actually tells the difference between overloaded functions? We write functions with the exact same name and take the magic for granted. But under the hood, the linker requires a unique identifier for every single function. The secret? Name Mangling. Check out the image below! 👇 The compiler automatically alters the function's name based on the number and types of its arguments. To us, it’s just display(). To the compiler, they are two completely different entities (like i for int, d for double). The ambiguity is resolved before the code is even linked. It's a great reminder of how much heavy lifting the compiler does behind the scenes to keep our APIs clean and readable. What’s a concept you used for years before finally looking under the hood? Let's hear it below! #CPP #Cplusplus #SoftwareEngineering #TechTrivia #Programming #BackendDevelopment

Real talk: Your API breaks when traffic spikes. No limits. No protection. Fix: - Add rate limiting - Queue heavy tasks - Cache common responses Plan for spikes before they happen. #Programming #Backend #Performance #DevTips

Solved the Target Sum Expression problem in C++ today. The challenge was to count how many different expressions can be formed by placing '+' or '-' before each number in an array so that the final result equals the target. For example: arr = [1, 1, 1, 1, 1], target = 3 Output = 5 What I learned: 1. Each number gives us two choices: add or subtract 2. This problem can be solved efficiently using Dynamic Programming 3. We track how many ways each sum can be formed as we move through the array Key takeaway: Instead of generating all expressions manually, DP helps us store intermediate results and avoid repeated work. #cpp #programming #dsa #dynamicprogramming #codingchallenge #leetcode #geekforgeeks #softwaredeveloper

std::vector vs std::deque vs std::list — same STL family, very different trade-offs. At first glance, they all store sequences of elements. But under the hood, their memory layout and performance characteristics are completely different. std::vector → Contiguous memory → Excellent cache locality → Usually the default choice std::deque → Segmented memory → Fast insertions at both ends → Good compromise when you need flexibility std::list → Doubly linked structure → Efficient insert/erase with iterators → But poor cache locality 💡 One of the most common misconceptions in C++: std::list is not always faster for insertions in real-world scenarios. 👉 In practice, memory layout and cache behavior often matter more than theoretical complexity. I put everything into a visual to make the differences easier to grasp at a glance. Curious about your habits: Do you default to std::vector, or do you regularly use deque / list in production? #cpp #cplusplus #stl #performance #softwareengineering #coding #programming

C15 Union Types: finally, compiler-checked “either/or” results 🚨 Tired of returning object (or building awkward base classes) just to say “this method returns A *or* B”? C15 brings a real solution: union types. ✨ What clicking gets: ✅ How `union` declares a closed set of case types (even unrelated ones) ✅ Implicit conversions so assignments stay clean ✅ Exhaustive pattern matching—the compiler forces every case to be handled (no `_` / `default` safety blanket) ✅ A clear roadmap for broader exhaustiveness in C# 🧠 Example vibe: define `Pet(Cat, Dog, Bird)` once… then `switch` with confidence knowing every case is covered. If discriminated unions were missed in C#, this is the most C#-native take yet. 🔥 https://lnkd.in/dsu5t_8M #csharp #dotnet #programming #patternmatching #compilers

auto is the chess pawn of C++. Ignored in the opening. Underestimated in the middle game. Then modern C++ took it to the last rank — and promoted it to queen. What once looked like an ordinary keyword has become one of the most practical and powerful features in modern C++. Today, auto helps developers write code that is: • cleaner • safer • easier to maintain • more expressive with complex types, iterators, lambdas, and templates The real value of auto is not “typing less.” It is about improving readability where the type is obvious, reducing redundancy, and letting the code focus on intent. Used well, auto is not laziness. It is modern C++ maturity. #cpp #moderncpp #softwareengineering #programming #developers #coding #cplusplus