Interesting read, this is really tricky to measure such latency. It looks like we might have room for improvements on latency still. Curious to see if the proposed fixes will make it in kwin.
Interesting family of testing and debugging tools indeed. I should definitely reach out to those more.
Good point, disabling asserts in production is not the best default position to have.
OK, I find it funny. That said, there's a kernel of truth in this piece: there's clearly a taxonomy of bugs and you better know on what you just stepped.
Examples of how i3 and go stamp versions. This is indeed good habits to ease dealing with errors in production.
Interesting color coding for hex editor. It indeed brings interesting properties.
Lots of good insights in here. Of course YMMV and some definitely depends on your context. That's a lot of dimensions to keep in mind though.
Yes, we have lots of layers nowadays. But you can read them to figure out when something doesn't work like you expect. This is one of the most important skills of the trade.
OK, this is definitely a very cool hack. It can definitely help to debug locally.
Error handling is still not a properly solved problem in my opinion. At least the Rust community discusses the topic quite a bit. This is good inspiration for other ecosystems as well I think.
A good summary on the important rules to follow to debug something.
Early days but this looks like interesting tooling to inspect and debug programs using Rust channels.
An interesting way to approach the topic of GPU programming nowadays. It might indeed make more sense nowadays than reaching for putting pixels on screen as a first objective.
Interesting dive into an heisenbug... Definitely not easy to debug.
Indeed, carefully reading larger chunks of code and looking for the historical context around it can go a long way in finding bugs.
Interesting talk. The tools presented can indeed go a long way helping people figure out what's wrong with a piece of code or learning some of the harder parts of a language.
Very interesting bug hunt prompted by some mysterious character in some strings and leading all the way to PDF viewers.
You like weird bugs involving shell implementations, syscalls and filesystems? Somehow I do, this was an interesting one.
A very important tool to have around and know how to use. This is a neat introduction.
This is an important piece of advice. You need to try things for yourself and fail to really learn. I'm not talking about failing in production of course. But trying to break something locally to see how it behaves, reading the errors, etc. is part of learning. This is how you will troubleshoot things faster the next time.