Blogs

Other Parts of This Series: Part 1: Becoming a Pragmatic (Better) Programmer - Part 1 (Intro, Team Player) Part 3: Becoming a Pragmatic (Better) Programmer - Part 3 (Decouple, Concurrent Coding, Project & Team) Pragmatic Programmer (Photo Credit: Unsplash) Story Ismael gets hired by an established IT company as a senior software developer. He has worked on several projects and in various business fields throughout the years, gaining expertise and experience. Based on his skills and experience, he keeps a respectable approach when designing or programming a system. ...

Other Parts of This Series: Part 2: Becoming a Pragmatic (Better) Programmer - Part 2 (Design, Implement, Debug) Pragmatic Programmer (Photo Credit: Unsplash) Story Sajjad is an experienced programmer who has worked in the software industry for many years. He tries to be skilled and make himself fit for use in any situation and any kind of project. He always works to sharpen the basic knowledge and not be dependent on any particular tools or technology, but rather always try to choose good tools and technology that are fit for that particular scenario. He observes some common characteristics that great (pragmatic) programmers hold. Like they are early adopters or fast learners, critical thinkers, rethinkers, and realistic. Some of them are jacks of all trades. So Sajjad also keeps these characteristics, keeping the attitude and philosophy of approaching problems and solutions like a pragmatic programmer. ...

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. ...