I don't think I've ever been a super competent debugger user. May have to expand my skill tree.
-
-
Replying to @generativist
Skip the debugger and use print[f] Debuggers are best for a small subclass of issues (havn't figured out what that subclass is), but they can also send you an a wild goose chase if your issue is memory corruption or threading bugs.
4 replies 0 retweets 2 likes -
Replying to @clolsonus @generativist
debuggers can tell you the line of code your program blew up on, but if you can't figure that out already, you are probably into memory corruption or thread issues. Disclaimer, I'm not a web developer so maybe debuggers are good for css?
1 reply 0 retweets 1 like
Replying to @clolsonus
debugging some go issues for a long-running service right now
9:56 AM - 25 Apr 2020
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.