3 ms·
Just like a Java programmer to tell you to use an event bus for simple diagnostics. I’m a former one, I don’t mean no offense. I go even lower though. Just pr
by johnwheeler 5y ago
Just like a Java programmer to tell you to use an event bus for simple diagnostics. I’m a former one, I don’t mean no offense.
I go even lower though. Just
print(“XXXXXXXXXXX”)
print(“XXXXXXXXXXX”)
print(amount)
- Spivak 5y agoThat event bus exists whether you call it one or not — print is just a buffered serialized stream of events consumed by the kernel and rendered to strings.
- johnwheeler 5y ago> buffered serialized stream of events So is a sewer though, and I wouldn’t call that an event bus either.
- diogenesjunior 5y agowhen my code is not working how i expect it to, i print a ton of equal signs, then the value on a knew line, then a new row of equal signs. never used loggin before.
- jpgvm 5y agoYou my friend need to experience an interactive debugger.
- zepolen 5y agoYou my friend need to experience a production heisenbug.
- jpgvm 5y agoI think you are taking the comment rather out of context and just took the chance to be snarky. The gentleman I was replying to is clearly new to the gig and he should try out a debugger, it will change his workflow immensely and likely make him a much better developer. Yes, you still want logs (or events or traces, etc) in production to identify when edge cases or heisenbugs have occurred. A debugger doesn't replace those but it does replace 'println` style debugging when developing new code.
- zepolen 5y ago> it will change his workflow immensely and likely make him a much better developer Frankly the best developers I have met did not rely on debuggers, or logs for that matter. Using neither forces them to keep the program flow in their head and completely understand the code and system before pressing run. For debugging production systems of course logs are useful.