Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Mo 09.09.2024 00:00:08 62.066 +2 3.696.609 59,6 Fosstodon 4.2.12 500 So 08.09.2024 00:00:15 62.064 +5 3.694.121 59,5 Fosstodon 4.2.12 500 Sa 07.09.2024 00:00:44 62.059 +6 3.693.330 59,5 Fosstodon 4.2.12 500 Fr 06.09.2024 00:00:33 62.053 +5 3.690.277 59,5 Fosstodon 4.2.12 500 Do 05.09.2024 00:01:06 62.048 +2 3.687.723 59,4 Fosstodon 4.2.12 500 Mi 04.09.2024 00:01:06 62.046 +1 3.684.706 59,4 Fosstodon 4.2.12 500 Di 03.09.2024 00:00:09 62.045 0 3.681.789 59,3 Fosstodon 4.2.12 500 Mo 02.09.2024 00:00:32 62.045 +2 3.679.515 59,3 Fosstodon 4.2.12 500 So 01.09.2024 00:00:08 62.043 +7 3.677.338 59,3 Fosstodon 4.2.12 500 Sa 31.08.2024 00:00:00 62.036 0 3.674.391 59,2 Fosstodon 4.2.12 500
Esparta (@esparta) · 11/2019 · Tröts: 579 · Folger: 49
Mo 09.09.2024 18:05
A systematic approach to debugging, by @nicole
https://ntietz.com/blog/how-i-debug-2023/?utm_source=atom&utm_medium=feed
> Here's the process laid out in sequence. After going through the steps, I'll provide more detail on each one.
1. Figure out the symptoms.
2. Reproduce the bug.
3. Understand the system(s).
4. Form a hypothesis about where the bug is.
5. Test this hypothesis, and repeat if needed.
6. Fix the bug!
> Check the fix, and repeat if needed. We go through quite a bit of this process before even touching code
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Tusky