Programming-Basic

Detailed Refactoring Series: Part 1: Refactoring - Part 1 (Principle, What It Is & Is Not, Identify the Smells First) Refactoring Book Book introduction Martin Fowler’s “Refactoring: Improving the Design of Existing Code” is a classic book that teaches developers how to improve the structure of existing code without changing what it does. Refactoring makes code easier to read, maintain and expand, helping teams write better software over time. ...

Detailed Clean Code Series: Part 1: Writing Clean Code - Part 1 (Conceptually Clean and Bad Code) Clean Code Book (Photo Credit: SoBrief) Book introduction “Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin (popularly known as Uncle Bob) is one of the most influential books in software engineering. It focuses on the principles, patterns, and best practices for writing clean, maintainable, and efficient code. ...

Other Parts of This Series: Part 3: Writing Clean Code - Part 3 (Formatting, Class & Object, Miscellaneous) Code Smells (Photo Credit: Axify) Story Our prophet Hazrat Muhammad Sallallahu Alayhi Sallam advised us that “Always try to avoid the acts of sin/bad things because if someone can avoid the bad work, he/she will start doing good work automatically.” This is true for both our real life and writing code. If we can avoid the code smell or bad code, then our code will automatically be good and clean. So identifying the code smell is important. ...

Other Parts of This Series: Part 2: Writing Clean Code - Part 2 (Name, Function, Comment) Part 4: Writing Clean Code - Part 4 (Identify Code Smells/Bad Code) Clean Code - Formatting, Class & Object, Miscellaneous (Photo Credit: Sotatek) Remember 2 things: The only measurement of your code is WTFs / Minute. That is what the readers feel when reviewing code. Linux Torvalds, the creator of the Linux operating system, says, “Talk is cheap; show me the code.” So if we connect the above 2 points, then we can easily understand that our code should be talkable and self-describing because when anyone reviews/reads our code, they should feel well and comfortable enough. ...

Other Parts of This Series: Part 1: Writing Clean Code - Part 1 (Conceptually Clean and Bad Code) Part 3: Writing Clean Code - Part 3 (Formatting, Class & Object, Miscellaneous) Clean Code - Name, Function, Comment (Photo Credit: Prezi) Remember 2 things: The only measurement of your code is WTFs / Minute. That is what the readers feel when reviewing code. Linux Torvalds, the creator of the Linux operating system, says, “Talk is cheap; show me the code.” So if we connect the above 2 points, then we can easily understand that our code should be talkable and self-describing because when anyone reviews/reads our code, they should feel well and comfortable enough. ...

Other Parts of This Series: Part 2: Writing Clean Code - Part 2 (Name, Function, Comment) Clean Code (Photo Credit: Dev Community) Story Arman and Rakib are classmates. They both complete their readings and homework regularly. But their approach to finishing the homework is quite different. Although they finish their homework on time, the quality of work is quite different. For example, Arman is a more qualified student than Rakib. Because he does his homework in the most organized way. He always tries to make notes of his homework so that he can reuse the notes and its knowledge later when this will be applicable. He keeps his homework simple, short, and sweet. That’s why his homework can be felt, understood, and create a happy feeling for others who read his notes and homework later. ...

Basic Knowledge List for CS/CSE Freshers University life is the prime time for grabbing knowledge and getting ready for industry. But there has been a misconception that anyone can only be industry-ready only when he/she starts working or has a job. This is not true at all. Undoubtedly, whoever is willing to prepare himself upfront should start at the university or at least immediately around graduation completion. ...

Steps (Photo Credit: iStock) Story Ismael started his career as a “Software Engineer—Level I” at a reputable software firm. He was promoted to “Software Engineer—Level II” after successfully completing a year in his current role. He passed another year in this promoted role. But gradually he started to feel a lack of motivation or engagement. This became a problem for his career. He therefore got ready and began taking action to address the issue. He thus took the following steps to address the problem: ...

Other Parts of This Series: Part 7: Let’s Feel Programming Fundamentals - Part 7 (Algorithm) Concurrency Vs Parallel (Photo Credit: TechDifferences) Story Remember the principle Virus (Viru Sastre Buddeh) from the 3 Idiots movie. He was able to write simultaneously with his 2 hands. He could do multiple tasks at a time. My friend Sharif is a true die-hard fan of Principle Virus. He also can do multiple tasks at a time. He can write with his 2 hands, 2 legs, and other works simultaneously. Sometimes some works depend on each other, and then he has to wait until the dependent work is done. ...

Other Parts of This Series: Part 6: Let’s Feel Programming Fundamentals - Part 6 (Data Structure) Part 8: Let’s Feel Programming Fundamentals - Part 8 (Threads, Async-await, Concurrency, Parallel) Algorithm (Photo Credit: knowitallninja) In this part, we will try to understand what a algorithm is. Also see different types of algorithm based on the solution procedure. Please note: we will not dive deep for the sake of simplicity. If you feel really interested, you can explore each of them in details. And may be I will write each of the topic in details in future insha Allah. ...