Nostr Web Client

Well, usually it means that you don't understand the codebase. You don't know the structure and data flow. You have poor logging and "embedded" debugging code inside.

Focusing on errors themselves, stack traces and good old printf() is much better for me then getting lost in some local context bs.

The overall behavior is what I'm interested in. You need to understand the code.

Not to mention that you never find things like race conditions etc.

Debuggers always've been my last resort or learning tool.

Diacone Frost 1y ago

Using debugger == don't have a clue what's going on for me

Reply to this note

Please Login to reply.

Discussion

MichaelJ 1y ago

Sometimes you have an inherited code base and need to understand what is happening where, though. Debuggers are immensely helpful, in that case.

I see your point about logging and error messages. Well placed print statements can make all the difference.

Diacone Frost 1y ago

Yeah, sometimes you just don't know wtf is going on 😂

been there, done that

Laeserin 1y ago

Yeah, I refactored everything and it started acting weird and I had no clue what was going on. 😅 🤷‍♀️

Diacone Frost 1y ago

did it help though? I usually spend a lot of time in debugger finding out that it's just broken.

Then the printf comes in ...

Laeserin 1y ago

It did, actually, because it showed me the same result that my logging was showing me: nothing.

And run it again... nothing.

It was an infinite loop. 😅 I had a copy-paste error with a getter that called itself. Looked at it for almost an hour and couldn't see the problem, so I was like, let me ask the debugger, and then the stack blew up.

Diacone Frost 1y ago

weird that it did not overflow. some sort of magical tail recursion. php got much better then i remember ))

Diacone Frost 1y ago

ok world is back in order. php does not have tail call recursion. I can keep hating it.