#Debugging
25 notas · última:
Become a Better Programmer: 7 Habits to Grow
The article says better programming comes from strong basics, deliberate problem-solving, clean code, debugging, documentation, networking, and building real projects.
How to Help Someone with Their Code Using the Socratic Method
The article argues that giving direct answers blocks learning, while Socratic questioning helps learners reach conclusions themselves and strengthens debugging, assumptions-checking, and long-term reasoning.
8 effective debugging strategies to find and fix bugs like a pro
The article argues that debugging skill is central to trusted software work and lists eight practical tactics: reproduce the bug, narrow it down, use tools, and take breaks when needed.
Occam's Razor - Mental Model
The page explains Occam’s Razor as a problem-solving principle that favors the simplest explanation that works, using debugging, tech support, and product decisions as examples.
How Inline Return Values Simplify Debugging in Visual Studio 2022
Visual Studio 2022 adds Inline Return Values to show function return values directly in the editor, and Copilot can explain them or suggest fixes during debugging.
The 66% Problem
The text argues that AI assistants write code that is “almost right,” but hard to debug, creating new bugs and a deceptive sense of productivity.
Advanced Debugging in C#
The article shows advanced debugging techniques in Visual Studio 2022 for C#: conditional breakpoints, tracepoints, hit count, filters, code editing, execution pointer, object IDs and string visualizer.
How to Improve Your Programming Skills by Building Games
The article argues that building games teaches programming through systems thinking, event-driven code, performance, debugging, input handling, design, and creative problem solving.
C# attributes you should know #2: [DebuggerStepThrough] and [DebuggerHidden]
The post explains how [DebuggerStepThrough] lets code run without being debugged, how [DebuggerHidden] hides code from the debugger, and how they differ in the Call Stack.
Exploring the path of a new and unfamiliar codebase
The author outlines a practical way to get comfortable in a new codebase: explore the product, set up the environment, pick simple bugs, debug systematically, and ask for help when needed.
Debug Your .NET Core Apps in WSL 2 with Visual Studio
The .NET Core Debugging with WSL 2 – Preview extension lets you run and debug .NET Core apps in WSL 2 from Visual Studio, with launch profiles for the default or a chosen distribution.
Using git bisect
The article explains how git bisect narrows a commit range to find the first bad commit, using a checkout bug as a real-world example of marking commits good and bad.
Oh shit, git!
The page collects plain-English fixes for common Git messes, including reflog recovery, amending commits, moving commits to the right branch, checking staged diffs, and starting over by recloning.
Debugging techniques in Elixir
The post compares simple printing with two Elixir debugging options: IEx.pry/0 for inspecting a running process and :debugger for breakpoints, variable inspection, and step-by-step navigation.
The Art of Debugging
Remy Sharp argues that debugging is learned through experience and shows a practical workflow: replicate the bug, isolate the cause, then eliminate it with tools and tests.
10x engineer: 10% of the time
The post argues that perceived productivity in software engineering comes from a few practiced habits: debugging well, staying unblocked, choosing between manual work and tools, and reading code effectively.
Programmer Momentum
The piece argues that coding progress depends on momentum built by keeping context loaded, planning the next steps, and avoiding interruptions, bugs, and stopping mid-flow.
5 functions of the Console object you didn’t know
The page highlights five lesser-known Console methods for debugging in Chrome: assert, table, profile, group, and time, and briefly explains what each one does.
Seven Things You Should Stop Doing with Node.js
The post lists seven Node.js habits to avoid: nested callbacks, wildcard versions, console.log debugging, using GET and POST for everything, semicolons, comma-first style, and the default maxSockets limit.
Must Have Gems for Development Machine in Ruby on Rails
The page lists Ruby on Rails development gems that speed up debugging, profiling, logging, database inspection, mail testing, code analysis, and app boot time, with brief notes on what each gem does.
Great Programmers Write Debuggable Code
The post argues that good programmers add logging and tools that make failures easier to debug, because when code breaks, useful logs help narrow down the cause without needing a special debug build.
Functions Explained
The post explains JavaScript functions as named blocks, then shows how arguments, hoisting, declaration versus expression, scope, and naming affect behavior and debugging.
How to be a Programmer: A Short, Comprehensive, and Personal Summary
The chapter argues that programmers need strong debugging, performance, documentation, estimation, and teamwork habits, and that all of them depend on experimentation, judgment, and clear communication.
UsingTheJRubyDebugger
Explains how to use the JRuby debugger, including which versions already include ruby-debug, how to install the needed gems on older versions, and how to start debugging Rails apps or local Ruby programs.
Coding tricks of game developers
A collection of game-dev anecdotes about deadline pressure, memory and performance hacks, and pragmatic workarounds that kept projects moving when shipping was close.