Abhilash Krishnan’s Post

Code comments at the right places can be invaluable. Came across an enlightening piece from Dan Harper (the post is linked at the end), where he shares a compelling narrative about the hidden complexities of software maintenance and the unexpected consequences of seemingly minor configuration changes. It's a vivid reminder of the critical role code comments can play in saving future developers from painstaking hours of unnecessary debugging and, potentially, months of head-scratching. Something like this comment added around that setting could have prevented it: // IMPORTANT: This service is set to "conservative" mode due to a known issue with memory corruption when deep-duplicating objects using the XYZ library. Changing this to "performance" mode has previously led to intermittent service failures. This decision was made after extensive debugging to prevent errors related to incompatible shared memory models. Please refer to git history around [specific date or commit hash] for more context. Link to Dan's post: https://lnkd.in/dGE_FXAC #CodeComments #SoftwareDevelopment #DebuggingTips #CodeQuality #ProgrammingBestPractices

An Overview of Code Quality: Basics and Best Practices

Day 34 & 35 of #100DaysOfCode I did a lot of code review, rectification, replanning, documenting and deployment. Read for the full details 👇 https://lnkd.in/dJaQee7k

For most of us, we only perform (peer) code review on the (system/production-level) code we wrote. What about the tests we wrote? How do we ensure the tests in our codebase(s) are working as per intended and meaningful? Read this article to find out: https://lnkd.in/gmMtQmYP

What is good code? It’s the code you never have to write. By that, I mean code that handles various scenarios simply by adjusting a configuration file instead of adding endless if-else conditions. If you are doing this, you’re already ahead of 95% of developers. Good code minimizes complexity and lets you focus on solving problems rather than rewriting logic.

Code Quality 2024 : Introduction This is the start of a series about how to achieve code quality. https://lnkd.in/eJ7QsiQ3

[𝗖𝗹𝗲𝗮𝗻 𝗖𝗼𝗱𝗲] 𝗖𝗼𝗻𝗰𝘂𝗿𝗿𝗲𝗻𝗰𝘆 Making concurrent code correct is hard. There are several important principles:  - Separate your thread-related code from the rest. - Do not try to chase down non threading bugs and threading bugs at the same time. - Test your thread-related code with various configurations on different platforms repeatedly and continuously. - Understand the potential sources of issues: multiple threads operating on shared data, or using a common resource pool, shutting down, or completing the iteration of a loop. - Improve your chances of finding erroneous code by instrumenting your code. 𝗧𝗼𝗱𝗮𝘆'𝘀 𝗳𝗼𝗰𝘂𝘀: 𝗖𝗼𝗻𝗰𝘂𝗿𝗿𝗲𝗻𝗰𝘆. ----- You are not ready for deployment if your code is not clean. Clean code means maintainable. Maintainable means survival and growth. 

How to modernize legacy code: the technical side of refactoring 🛠 Inherited code is like an old engine in a car: it might still run, but sooner or later, it's going to give you trouble. Especially if you’ve driven it a long way 🏎 Our Software Developer, Dmytro Khandzhanov, with 10 years of experience, shared experience in his article on DOU 🔥 Main issues: maintaining, flexibility, and testing legacy code — like playing a game on the hardest difficulty level 🔧 Our approach: refactoring with Clean Architecture to make the code more maintainable and scalable Check out the article via the link 📲 https://lnkd.in/eA7X52wT

Code review comments have their purpose, but can be overused. There are other things you could do. Some code review comments could be: - A discussion about software architecture - A ticket to make another change later - A commit fixing the spelling. https://lnkd.in/e4C9ADp4

Code reviews shouldn't get bogged down in trivial details. The real focus should be on ensuring the code fulfills its purpose effectively and performs optimally.