C Compilation Process: Preprocessing, Compilation, Assembly, Linking

Most beginners think memory management in C++ is just about new and delete. It’s not. It’s about responsibility, discipline, and understanding how your program behaves when nobody is watching. This article is a solid reminder that performance isn’t magic — it’s memory management done right. Once you truly understand pointers and allocation, you stop writing code that just runs… and start building systems that scale. Master memory, and you master C++. Read more on medium Medium:@talhaulfat93 #cpp #programming #softwaredevelopment #coding #computerscience #memorymanagement #developers #tech #automation #learning

Dived deep into some core concepts that shape how efficient and safe programs are built: • Object Lifetime (Stack & Scope Lifetimes) – understanding how and when objects are created and destroyed • Memory Model – getting clarity on how memory is structured and accessed • Smart Pointers – explored std::unique_ptr, std::shared_ptr, and std::weak_ptr (thanks to Yan Chernikov for the clear explanations) • Deep dive into std::unique_ptr – ownership and zero-overhead abstraction • Memory Leaks – why they happen and how to prevent them • Forward Declarations – reducing dependencies and improving compile times • Header Files in C++ – understanding structure and best practices (Saldina Nurak) Each of these topics adds another layer to writing cleaner, safer, and more efficient C++ code. Still a lot to explore, but enjoying the process of strengthening fundamentals step by step. #CPP #LearningInPublic #Programming #SoftwareEngineering #SmartPointers #MemoryManagement #100DaysOfCode

🚀 Testing your C fundamentals! Can you predict the output of this nested loop? for(int i = 1; i <= 3; i++) { for(int j = 1; j <= 2; j++) { printf("%d%d ", i, j); } } Drop your answer in the comments 👇 #CProgramming #EmbeddedSystems #CodingChallenge #Loops #LearningInPublic

“I wish I knew this roadmap before learning C…” Want to become a professional in C? Here’s a simple roadmap that actually works 👇 - Master basics (syntax, loops, functions) - Learn pointers & memory (MOST IMPORTANT) -Understand stack vs heap & memory layout - Practice file handling & system basics -Write clean, modular code (.h / .c) -Solve problems on HackerRank & LeetCode -Build real projects (data structures, mini tools) -Learn debugging with GDB -Explore advanced topics (function pointers, optimization) 💡 Consistency is the key: Code → Fail → Debug → Repeat #programming #cprogramming #embedded #softwareengineering #learncoding

💡 DP (Dynamic Programming) becomes simple with the right problem — Counting Bits (LeetCode 338) 👉 dp is using previous results to compute new results Instead of recomputing, just reuse:   `bits[i] = bits[i >> 1] + (i & 1)` Same patterns. Less work. Faster solution. #DynamicProgramming #LeetCode #DSA #CodingInterview #ProblemSolving #BitManipulation

Project #2 — Temperature Converter in C++ As part of my learning journey in C++, I built a (console-based Temperature Converter) focused on improving code structure, modularity, and user input handling. This project helped me move further from just writing code to designing cleaner and more maintainable programs. What I Focused On - Using (enum) to represent temperature units clearly   - Structuring data using (struct)  - Writing modular and reusable functions   - Implementing strong input validation   - Improving overall code readability  Features - Convert between:  - Celsius ↔ Fahrenheit    - Celsius ↔ Kelvin    - Fahrenheit ↔ Kelvin   - Clean formatted output   - Continuous conversion loop   - Input validation for better user experience  What I Improved From My Previous Project - Better separation of logic (input / processing / output)   - More consistent function design   - Cleaner flow and user interaction   - Improved handling of invalid inputs  Demo video below GitHub Repository: https://lnkd.in/eQrJH7tq  Next Step Refactoring my projects into (Object-Oriented Programming (OOP)) and building more advanced applications. #cpp #programming #softwaredevelopment #coding #learning #github #beginners #100DaysOfCode #ProgrammingAdvices

🚀 Testing your C fundamentals! Can you predict the output? int a = 5; int b = 20; int *p = &a; p = &b; *p = 30; printf("%d %d", a, b); Comment your answer 👇 #CProgramming #EmbeddedEngineer #CodingChallenge #Pointers

Your C code tells WHAT to do. The linker script tells WHERE it lives in memory. And almost nobody reads it. Until something crashes. A linker script is the blueprint of your MCU's memory. It tells the toolchain: → Where does code (.text) go? → Flash (non-volatile) → Where do global variables (.data) go? → RAM → Where do uninitialized variables (.bss) go? → RAM (zeroed) → Where does the stack start? → Top of RAM → Where does each core's memory begin? → Multi-core specific A simplified example: MEMORY { FLASH (rx) : ORIGIN = 0x80000000, LENGTH = 2M RAM (rwx) : ORIGIN = 0x70000000, LENGTH = 256K } SECTIONS { .text : { *(.text) } > FLASH .data : { *(.data) } > RAM AT> FLASH .bss : { *(.bss) } > RAM .stack : { . = ORIGIN(RAM) + LENGTH(RAM); } > RAM } Why this matters: 1. Stack overflow — if your stack grows into .bss, you corrupt global variables. Silent. Deadly. 2. Multi-core — on AURIX TC3xx, each core has private DSPR. Put Core 1's data in Core 0's memory? Random crashes. 3. Flash vs RAM — code runs from Flash. Variables live in RAM. Initialized variables (.data) start in Flash and get COPIED to RAM at startup. 4. Memory budget — the linker map file tells you exactly: "You've used 87% of Flash and 92% of RAM." Ship it? Or optimize? The linker script is the most powerful and least understood file in embedded development. Read yours today. What memory issue has the linker script helped you solve? #LinkerScript #EmbeddedC #MemoryManagement #MCU #EmbeddedSystems #Programming

Ever faced a memory leak… in code or in life? 😂 Post: In C, forgetting to free() memory leads to leaks. In life, forgetting to “let go” does the same. 🔹 Deleted the node 🔹 But memory still occupied That’s not just a bug… that’s emotional engineering 😄 👉 Lesson: Always clean up your pointers (and your past) #CProgramming #LinkedList #MemoryLeak #CodingHumor #SoftwareEngineering #EmbeddedSystems #DebuggingLife #TechMemes #ProgrammerLife

🚀 Day 7 of My LeetCode Journey Today’s problem: Reverse Integer At first glance, it looks simple — just reverse digits. But the real challenge was handling 32-bit integer overflow without using 64-bit storage. 🔍 What I learned: How to extract digits using modulo (%) Building the reversed number step by step Most importantly, checking overflow before updating the result ⚠️ Edge Case: If the reversed number goes beyond the 32-bit range [-2³¹, 2³¹ - 1], we must return 0 💡 Example: Input: 123 → Output: 321 Input: -123 → Output: -321 Input: 1534236469 → Output: 0 (Overflow case) Consistency over perfection 💪 #Day7 #LeetCode #DSA #CProgramming #CodingJourney #ProblemSolving