GameDev is still running late when it comes to this. The most popular engines are still full of deep and rigid inheritance trees, strongly coupled classes and modules and the One above them... The Singleton. We'll investigate why the Singleton seems to be such a tempting solution at the beginning and how it grasps the unsuspecting programmer while the project grows and petrifies the whole project. We'll challenge this mythical creature with the support of the good programming principles.
While you are reading this description you could have invoked some actions before which haven’t finished yet. For example: boiling water for a tea or downloading some file on your computer. You are doing it this way mostly probably because you don’t want to waste your time on things, that are independent of you and you are interested only in result of this processes.
This real life situation can happen also in your software systems by using asynchrony on many layers in your: code, components, server and architecture. Using it requires different thinking but it brings many interesting tools and methods based on asynchrony like: reactive programming, actor model, event sourcing, messaging servers, non-blocking architecture ect. It created also some terminology, patterns and anti-patterns around it. That’s what I want to present and talk with you on this lecture.
Has your water for tea already boiled ? :)
What Surveyor, Health Care Manager, Marketing Specialist, Career and Social Communication Specialist do have in common? They all spent a lot of time and energy developing and care about soft skills. They also work as Scrum Masters where soft skills and hard skills are required.
From our experience we know that technical and domain knowledge is something you can learn in practice. However it is not applicable to soft skills which are sometimes much more difficult to obtain. To be able to develop your soft skills you usually need to spend a lot of time and work hard, on your way of seeing the world and yourself, controlling your ego, and emotional awareness. That's why we want to share our experience of work as a Scrum Master with you.
We all know code review is an important part of every project and can significantly influence its final quality. But to achieve desired results with code review, the process has to be carried out in the right and competent way.
During my presentation, I’ll tell you about my experiences with code review. I’ll also share with you valuable hints on efficient code review you’ll be able to implement in your everyday work.