[flagged]
I stopped reading a couple paragraphs in because it felt so mechanical and AI generated. No personality to it.
Hung by a thread
11–20 of 20 posts
Re: Hung by a thread
#12[flagged]
Meh, I enjoyed reading it. I could be LLM-assisted but also I have a bunch of younger devs on my team who do actually write like this
You’re welcome to not like the article, and it can even be LLM-assisted, but that doesn’t mean it’s slop
Re: Hung by a thread
#13Oof lol. Sometimes I yearn for the Haskell or Idris style of programming where a dependency can do nothing harmful or stupid without me passing in permission. Then I think about having to pass in thread handles and file handles to logging libraries. I don't know. It would be a cool option. There is probably a hack for `tracing` that would let me manage the logging thread myself. Software is so complex these days. The…
Haskell has exceptions, so dependencies can still do plenty of harmful stuff ;)
Re: Hung by a thread
#14It's quite interesting to me the way that different "programming cultures" exist around debuggers. If you grew up doing windows C++ development, looking at things in a debugger is your first step. You only resort to printing values if you can't immediately see what happened in the debugger. A lot of other envioronment/language cultures are the opposite. Obviously both have their place, but I do feel like more people…
For embedded applications, especially robotics, it tends not to be a great default because it stops the process, which tends to be bad for realtime control loops. That said, a complete hang is the situation where I absolutely would try to get a debugger attached and get a backtrace as one of the first things to try.
Re: Hung by a thread
#15[flagged]
Meh, I enjoyed reading it. I could be LLM-assisted but also I have a bunch of younger devs on my team who do actually write like this You’re welcome to not like the article, and it can even be LLM-assisted, but that doesn’t mean it’s slop
You’re welcome to enjoy the slop, doesn’t change what it is
Re: Hung by a thread
#16[flagged]
You're absolutely right!
Re: Hung by a thread
#17It's quite interesting to me the way that different "programming cultures" exist around debuggers. If you grew up doing windows C++ development, looking at things in a debugger is your first step. You only resort to printing values if you can't immediately see what happened in the debugger. A lot of other envioronment/language cultures are the opposite. Obviously both have their place, but I do feel like more people…
I print first and get a feel for the code... Debuggers always slowed me down, and yes this was for c++
Re: Hung by a thread
#18> But I will never call into a library I don't fully understand while holding a mutex again. Fool me once.
Nice sentiment and an admirable goal. Not really actionable in practice. Even if we disregard all userspace libraries out there, fully understanding the most frequently used syscalls is a monumental task already. You have to pick your battles in terms of understanding parts of a complex system.
Re: Hung by a thread
#19[flagged]
Please don't do this here. If a post seems unfit for HN, please flag it and email us at hn@ycombinator.com so we can have a look.
Re: Hung by a thread
#20It's quite interesting to me the way that different "programming cultures" exist around debuggers. If you grew up doing windows C++ development, looking at things in a debugger is your first step. You only resort to printing values if you can't immediately see what happened in the debugger. A lot of other envioronment/language cultures are the opposite. Obviously both have their place, but I do feel like more people…
For embedded applications, especially robotics, it tends not to be a great default because it stops the process, which tends to be bad for realtime control loops. That said, a complete hang is the situation where I absolutely would try to get a debugger attached and get a backtrace as one of the first things to try.
If you’re working in robotics and don’t have fully deterministic event based replay you need to find a new middleware.