people who tell you to using code debuggers are just gaslighting

just console.log all the way, everyone does it and it's fine

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)

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

I said you have big data, that’s a compliment

that’s a lot of words to call me a script kiddie 

Engineering

creating and destroying; flying cars, roc.camera, july.rocks

I never want to see the word STM32 ever again

yup - agreed

https://warpcast.com/july/0x5c2ea8a9

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.

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

creating and destroying; built flying cars & autonomous vehicles, now building /faust, more here: /july, web: july.rocks

printf can be used in this use case too 😉 I have done this. 

F103 is cortexm3 I guess. What you need to do is first write a custom printf without all the garbage in newlib nano c library which you are probably linking to if you are using gcc. Then you can retarget it to uart. You would also need a custom hardfault handler and start up code to initialize the UART registers during startup before main. 

There are cases where you can’t use debuggers because in the finished product you generally disable the jtag/swd port and then you can’t debug the system with a debuggers. So you need some way to get the stack trace when a fault happens.

debuggers are simpler in some domains 🙃

debuggers are simpler in some domains 🙃 

https://warpcast.com/anurajenp/0xe7b65cd5

Take it easy, and if it's easy, take it twice

Hmm debugger helped me when I was investigating the data that get passed to a function as argument I'm one version of the library the data gets type casted to a type the function expects automatically in another it does not. 

Apart from this scenario I almost always use logs