/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 btorpey.github.io
Who Knows What Evil Lurks ... - Confessions of a Wall Street Programmer
| | sergioprado.blog
Bug hunting with static analysis tools - sergioprado.blog
5.4 parsecs away

Travel
| | The best way to spend less time fixing bugs in software is not creating bugs in the first place, and a static analysis tool is perfect for this job.
| | nrk.neocities.org
A gentle introduction to static analyzers for C
5.3 parsecs away

Travel
| | [AI summary] This article provides an introduction to static analyzers for C, focusing on tools like compiler warnings, Cppcheck, GCC's fanalyzer, and clang-tidy, emphasizing ease of use, minimal setup, and reducing false positives.
| | ddanilov.me
How I solved a bug by disabling C++ extensions | Dmitry Danilov
6.0 parsecs away

Travel
| | Tips on how to make your compiler strictly follow the C++ standard
| | patshaughnessy.net
Learning to Read x86 Assembly Language - Pat Shaughnessy
25.0 parsecs away

Travel
| [AI summary] The article discusses the process of learning to read x86 assembly language, focusing on how it can be a useful skill for understanding low-level operations of microprocessors. It outlines the challenges of reading assembly, especially in debugging scenarios, and provides an example of translating Ruby code into x86 assembly using Crystal. The article also explains the syntax and structure of x86 assembly, including register usage, instruction suffixes, and the differences between AT&T and Intel syntax. It highlights the complexity of x86 assembly due to its historical evolution and the need for understanding register sizes and operand notation.