Varun Srinivasan
@v
my unifying theory is that 1. debuggers are overkill for most web services, where the logic layer is simple and the data / infra layer holds the complexity 2. debuggers are very effective for software where the logic layer is real-time and complex (operating systems, games, basically anything with a runloop)
6 replies
3 recasts
126 reactions
woj
@woj.eth
that’s a lot of words to call me a script kiddie
3 replies
0 recast
65 reactions
July
@july
yup - agreed https://warpcast.com/july/0x5c2ea8a9
1 reply
1 recast
3 reactions
Gabriel Ayuso
@gabrielayuso.eth
I always use logging, not console.log per se but just add logging with levels (traces, debug, info, warn, error; use them all) as much as I can and then control that with flags. Not sure if debuggers have improved to work well with parallelism but I tend to avoid them since they mess with the loops and make it harder to find race conditions, etc. Another reason why I stopped using debuggers is because many aren't easy to use and I've switched tech stacks so many times I don't have time to learn them.
0 reply
0 recast
2 reactions
jj 🛟
@jj
Same with traces - i think the people selling the observability love it because it makes infra more complex and expensive, therefore taken more seriously. Otel thou is pretty cool, its like the kubernetes of observability, can take it with you wherever
0 reply
0 recast
1 reaction
Anuraj R
@anurajenp
debuggers are simpler in some domains 🙃 https://warpcast.com/anurajenp/0xe7b65cd5
0 reply
0 recast
0 reaction
dude
@imthedude
Take it easy, and if it's easy, take it twice
0 reply
0 recast
0 reaction