James Dellar’s Post

I just finished the course “C# Best Practices for Developers” by Reynald Adolphe! This course gave a great overview of best practices to follow. I could definitely see a lot of these tips working not only in standardizing codebases and changes between developers but creating readable organized code that would be easier to debug and understand by a third party. https://lnkd.in/dwEsBHBD #c.

Today, I watch this video as my daily lesson. Performance is a key interest for me but the high performance code still look scary to me, lol. I think I have to balance between complexity and maintainability with high-performance patterns. Even I feel scary with them I also feel good about them as well. https://lnkd.in/gekCradZ

Comments are crucial in programming because they provide clarity about the functionality and purpose of the code to other developers. By writing clear comments, you ensure that others can understand and maintain the code more easily. Moreover, when something goes wrong, comments become invaluable for debugging and troubleshooting—and sometimes, they can even save you from getting fired. 😂

My second code practice is done........

How To Feel Safe While Modifying Code?

How should you organize your C code for a project?   #CProgramming #CodeOrganization #CodingTips Hey fellow coders! 👋 Are you wondering how to organize your C code effectively? 🤔 Here are some tips and tricks on how to structure your project for better readability and maintainability: - Instead of stuffing everything into your main.c file, consider creating separate files for different functions and modules. - Create folders like src, include, t... Source: https://lnkd.in/gEwWJC24 #mymetric360

When programmers turn into detectives during code reviews!🕵️♂️🔍 . . . #CodeDetectives #SolvingBugs #DebuggingMasters #CodeCrackin #CodeReviewChamps #ProgrammerProblems #ApptunixUAE

Code reviews in a nutshell: 10 lines changed = 10 comments 1000 lines changed = 0 comments, LGTM (looks good to me) If you feel like you are beating each other with the stick during every code review, tomorrow's newsletter will help. I'll guide you through 10 tips for legendary code reviews. Come join 2,732 developers who will be reading it: https://lnkd.in/djSGihGa

I like to remind teams that code reviews are for the good of everyone involved and constructively building a better code base together. They're not for egotistical bullying of more Junior engineers mistakes or fruitless nitpicking. They're a great way to share amongst the team how things in the code base work and help the reviewing engineers and the reviewed engineers. They should feel like friendly team collaboration and peering. If it feels like the gauntlet, then it's time for a change in mentality. Usually a short meeting or some space after a stand-up with some positive examples helps steer the team the right direction. We do want to be vocal in catching things so we actually improve. So passively just saying "ok" to whatever isn't the goal. Ask questions, encourage discussion, and keep it friendly, light energy, and kind. Creating a standard checklist the reviewer checks off too is a great way to ensure engagement and not lazy "ok". Some checks though can be and should be automated. That's another conversation.

I support frequent, small-batch releases. The practice reduces costly mistakes & shortens recovery time. But it doesn't guarantee high-quality code. The best code I've seen was the result of: ✓ clear working agreements about code & testing ✓ ensemble programming ✓ humility