Zen & the Art of C/SIDE Development

You and I spend our professional lifes maintaining, extending and debugging existing C/AL code - both written by our very capable friends at Microsoft, and by our (hopefully) equally capable co-workers at NAV partner organizations.

Intuitively, we know exactly which pieces of code are easy to grasp, and which require a little more time and mental effort. Some features can be built upon with a fair amount of confidence in the resulting code, others require thorough testing before we can finally declare them ready for release. Some areas in the application are a pain to debug, whereas others offer a highly enjoyable sense of elegance and transparency.

In the next few weeks, I plan to write on this blog about the best practices that I have compiled over the last few years. Some stem from books that I have read on the subject (Clean Code by Robert C. Martin is warmly recommended in this context), others are merely a boiled-down version of my own meandering experience. Admittedly, none are rocket science, but by discussing them I hope to change the way you think - I guess that, in a sense, that does make my attempts a kind of brain surgery.
See if you agree (and let me know if you don’t).

Thanks for reading!