Главная
Study mode:
on
1
Intro
2
Rules of the game
3
Where's the damage?
4
Shotgun debugging
5
What's the correct approach?
6
Scientific method
7
How to make it hard to form a hypothesis
8
Better way to do it
9
Correct way to do it
10
Software working on localhost?
11
Work should not be hard!
12
Bad logging practice: ambiguous log
13
Bad logging practice: log overflow
14
Good logging practices
15
TDD hint
16
How to (mess up) log aggregation
17
Your arrogance is your enemy
18
Hemispherectomy
19
Dissociative identity disorder
20
Weak hypothesis
21
How to address the source of the pain?
22
How do we debug the brain?
23
Have a book
Description:
Explore the pitfalls of software architecture and project management in this GeeCON 2022 conference talk. Delve into counterintuitive problems and learn how to navigate them without jeopardizing your career. Discover insights on debugging algorithms, effective logging practices, managing burnout, understanding neuroscience, dealing with depression, evaluating third-party software, handling toxic personalities, creating useful diagrams, optimizing CPU cycles, and challenging religious definitions of architecture. Gain valuable solutions to make your development life easier, including tips on forming hypotheses, implementing scientific methods, and improving logging techniques. Benefit from the speaker's personal experiences as they address topics such as SLAs, workplace challenges, and the importance of mental health in the tech industry. Acquire practical knowledge on debugging both code and the human brain, and learn why having a good reference book is essential for success in software development. Read more

Malevolent Architect: Only Bad Decisions in Software Development - GeeCON 2022

GeeCON Conference
Add to list
0:00 / 0:00