4200 - Introductions (Blog 1)

An Introduction

Welcome again, Amirali Mohayaee here. I'll be dedicating this sub-section of this blog to the 4200-specific items, which will be tagged under the 4200 label.

My main goal for starting this blog was as I had mentioned in my initial post on the blog, was and still is to document my work and what I go through and to also comment interesting and relevant articles and information.

While initially I had mentioned a select types of projects back in 2017, I will be deviating from those as they are both outdated and not very viable and attractive as portfolio pieces. I would rather have very good and impressive work-examples to show instead. One can't really learn by not branching or avoiding pitfalls.

What I'd aspire to be is someone with a solid foundational knowledge base and keen eye and discipline for solving problems. I would also like to reach for a high-level understanding in framework development, making use of the right patterns and data types, rather than do what I do now and pollute my code.

The reason why I am looking of focusing on these topics is that they are actually my weak points from my own perspective, but I will go more in depth in a later blog post.


-Amir

Comments

Post a Comment

Popular posts from this blog

4200 - Previous Experience (Blog 2)

Prior to joining the 4200, I had some experience with projects ranging from group projects to individual ones. The programming languages I've covered throughout the years are C++, C#, Java, Python 3 & 5 and HTML5. I'd definitely consider C++ the one I'm most familiar with. The projects I've worked on range from published work on appstores from when I worked at KillerBlitz and VectorDojo studios, ranging from working with the Android SDK to Unity. Majority of my other projects are on Github with those consisting of OpenGL and DirectX, with decent familiarity with said APIs. I've also had good familiarity with IDEs such as VisualStudios and Oracle for multitude of different projects. -Amir
Read more

A Small Look at Constructor Data-member Evaluation Order (C++)

I have a habbit of regularly going back to basics and doing a form of high-speed review of whatever in relation to general programming. I tend to forget small details, but if left for too long, these items add up and people can end up subconsiously forgetting entire topics and/or functionalities. One interesting thing that may be a small and rather overlooked feature of C++ would be the way the constructor, or rather the compiler would package data memebers of a constructor in the order the class member variables are listed. Ctor::Ctor( GameType& gtRef ) : randomizer( rand() ), gameObj0(x(randomizer), y(randomizer)), gameObj1(x(randomizer), y(randomizer)) { flag = false; }  In the above example, everything seems fine, however in the class body, there was something wrong when debugging the issue. private: MainWindow& wnd; Graphics gfx; // Game Objects GameObject gameObj0; GameObject
Read more