This week’s article is delayed due to my hectic schedule. I have to run around and therefore will have very little time to post my latest article.
Many of us use preprocessors such as #define, #ifdef, #else and many others. Most of the time when people are first introduced to C programming, one of the things they’ll learn is - always use #define to define your constants.
As we enter into more complicated stages of programming, we’ll usually find other preprocessors such as #ifdef, #ifndef and #else.
In C++, the use of #define is extremely undesirable, falling short of making it forbidden. So, is C++’s standards too paranoid or is it justified? Let’s find out… Read the rest of this entry »
“I know what I’ve written so I don’t need to document my own codes!”
“It’s my project! I’ve done it for many years therefore I don’t need to document my codes!”
“I know my code very well, I don’t need to document them for myself at all!”
Obviously, today I’m going to discuss about the memory programmers have. It seems that every programmer out there have the kind of memory that nobody can have! I mean, remembering childhood memories is one thing, remembering logical lines of codes is another!
Although it’s possible to remember how the code itself work logically in bits and piece, but can a developer really remember all the detailed logic and rationale? If yes, does it mean that we no longer or shouldn’t even need code documentations in the first place?
While I’m still preparing the long list of instruction documentations, I’ve decided to add one article here which I think a lot of people either know about or are totally ignorant about.
This is about poor header management. For a start, let me just clarify what headers are we talking about here. It actually refers to 2 things.
On top of that, on some weeks, we’ll talk about the rational of certain Script Instructions and why they’re there, how they work, what to look out for and what you to know other than the information available in the documentations.
Status
As of now, the tutorials are still being prepared as the Strides Octopus is going through its own upgrading. The instruciton documentations are still being prepared as we speak. However all that will take time and I’ll periodically update everyone (not just on Tuesdays).
Once the tutorials and documentations are up, I’ll revert to post Tuesday’s weekly strictly on Tuesdays only.
Please be patient for now.
Important!
The targeted Strides Octopus version for the tutorials will be Strides Octopus 3.1.4 as there’ll be some changes to the creation of the project initialization steps.
The current Strides Octopus version as of now is Strides Octopus 3.1.3.
This tuesday was a special day for me and therefore I couldn’t make a post.
So I’ll make up by posting today for a rather different topic. This time I’ll share my experience regarding the weird feeling I felt during my development using C++ codes versus my development using Strides scripts.
A lot of people usually think that build times are long and unnecessary, including myself as well.
But… there was once I had a terrible burnout and as a result, I couldn’t even organise my thoughts properly when developing using my very own Strides Octopus.
- It’s already almost 1 yr late!