youtube.com/watch?v=K09c5g… #gamedevdigestai #DevGAMM #talk #gamedev #mobilegames #optimization #careerdev TITLE: Step up your Engineering Game! CHANNEL: DevGAMM BRIEF DESCRIPTION: Talk by Jisan Haider Joy, Senior Unity Developer in the Core Tech team at Kolibri Games. The presentation covers professional growth paths for mobile game developers, technical skills and personal qualities needed for success in the industry. SUMMARY: (00:00) Jisan introduces himself as a Senior Unity Developer at Kolibri Games with 9 years of experience, working on optimization, bug fixing, and developing new systems for the company's successful games like Idle Miner Tycoon and Idle Bank Tycoon. He shares that one of his games reached 4 million DAU during the pandemic. (04:45) The speaker notes that while learning game dev has become easier due to information accessibility, many developers face career growth slowdown after a certain stage. The reason is that higher levels require more abstract skills and broader responsibility. (09:12) Jisan emphasizes the importance of technical skills: proper use of data structures, understanding design patterns and optimization. He provides an example of incorrect Dictionary and List usage leading to performance issues. (17:41) Talks about the importance of multithreading in Unity despite engine limitations. Suggests separating Model and Controller for work in separate threads, using Observer pattern for communication with the main thread. (29:32) Jisan shares three golden rules of a successful developer: being predictable, reliable, and consistent. Emphasizes the importance of clear team communication, understanding task scope, and responsible approach to work. USEFUL IDEAS: 1. Time-slicing for heavy operations (26:18) - dividing large calculations across several frames to avoid performance spikes. Especially useful in idle games when recalculating multiple dependent values. 2. Moving Model and Controller to separate threads (18:18) - if the controller doesn't work with View directly, its logic can be executed in a background thread, using an event model for UI updates. 3. Task timeboxing (37:21) - breaking work into short 2-3 hour intervals to maintain focus and productivity. Helps avoid burnout and improves code quality. 4. Reliability principle (38:38) - focus on quality problem solving, even if it takes more time. One quality fix is better than multiple temporary solutions. 5. Architecture for scaling (15:19) - plan systems considering future growth, especially for saves and configurations. Example given of how a save file can grow to 50MB when adding content. QUOTE OF THE DAY: "Don't strive to be a star programmer or genius - be the person in the team who can be relied upon. Own your product, love it, and treat it as your own."