4200 - Strengths and Weaknesses (Blog 3)

Strengths and Weaknesses

Strengths

  • Strong Communications skills. 
  • Good understanding of the discipline, patterns and data types. 
  • Willingness to tackle challenges in an effort to learn and further strengthen skills.
  • Good in teams
  • Good understanding on where to start when tackling errors and issues
  • Never content with where I am at a time with current skillsets and understanding, in an effort to keep pushing myself.

Weaknesses

  • Bad when working individually as a sole contributor to a single project. I like working around people more as it gives me more motivations.
  • I need to ask twice to ensure I've gotten something right. Might not be compatible with all types of personalities. 
  • Currently not very satisfied with where my foundational knowledge. I still need some more practice in some areas to get a complete understanding of things I've forgotten.
  • Uncertainly of applying certain patterns or how to correctly apply them, which can sometimes lead to over redundant and bloated code.

Areas for Further Development

  •  Complete satisfaction with having a great foundational knowledge to an extent which I can even create my own data types with having a deep understanding of for example of how to use them. Ambitious, I know, but I want to still attempt it.

-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