- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
Game per day 110 #unity3d #solodev #indiedev #gamedev #coding
Day 110 of building a new mobile game in Unity every day.
Today's game had a bug. How do I fix bugs? The vast majority of the time it shouldn't take hours to identify bugs, and certainly not days.
1. Figure out how to reproduce it. You need to know exactly when it happens so you can verify it is fixed, and identify if there are multiple bugs.
2. Identify the state before and after the bug, understanding how the input gets to the corrupted output. Your defect is along that stream.
3. Isolate the defect as much as possible, comment out code or write tests for sub modules to verify which part has the issue and which parts work. If you have a bug in Master, you can use git bisect to identify which commit introduced the defect.
4. Once you have identified and fixed the issue core issue (which should not usually take extra lines of code unless you need to add a check), consider a root cause analysis - especially if you work in a team or the bug was in Master. You don't want to repeat the same mistakes. Sometimes it's just an accident, but it could indicate a systemic issue such as lack of knowledge or testing.
#unity3d #solodev #indiedev #gamedev #coding
Видео Game per day 110 #unity3d #solodev #indiedev #gamedev #coding канала Resonant Solutions
Today's game had a bug. How do I fix bugs? The vast majority of the time it shouldn't take hours to identify bugs, and certainly not days.
1. Figure out how to reproduce it. You need to know exactly when it happens so you can verify it is fixed, and identify if there are multiple bugs.
2. Identify the state before and after the bug, understanding how the input gets to the corrupted output. Your defect is along that stream.
3. Isolate the defect as much as possible, comment out code or write tests for sub modules to verify which part has the issue and which parts work. If you have a bug in Master, you can use git bisect to identify which commit introduced the defect.
4. Once you have identified and fixed the issue core issue (which should not usually take extra lines of code unless you need to add a check), consider a root cause analysis - especially if you work in a team or the bug was in Master. You don't want to repeat the same mistakes. Sometimes it's just an accident, but it could indicate a systemic issue such as lack of knowledge or testing.
#unity3d #solodev #indiedev #gamedev #coding
Видео Game per day 110 #unity3d #solodev #indiedev #gamedev #coding канала Resonant Solutions
Комментарии отсутствуют
Информация о видео
20 апреля 2026 г. 17:16:26
00:01:09
Другие видео канала





















