Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Welcome to Hell Developer

noahclements.com

Post reply on HN
Print view View original

1–10 of 36 posts

Re: Welcome to Hell Developer

#2

Post by Scribbd »

> As for my original sync problem? After all of that – decompiling an APK, reverse engineering a binary protocol, writing a BLE exploit script – it turned out the issue was on my phone the whole time. Not the cycling computer. The phone.

I can feel the pain.

Re: Welcome to Hell Developer

#4

Post by kjhughes »

There seems to be a debugging pattern that arises when problems are in proximity to a poorly understood, highly complex part of the system: We tend to think that's where the problem probably is. And we can lose an inordinate amount of time looking for it there. It's like an inverse streetlight effect.

I've seen coding LLMs do it too. I have a well-tested, but complex, subsystem that constantly draws their attention when something non-obvious elsewhere goes wrong.

Re: Welcome to Hell Developer

#5

Post by davidw »

That's pretty interesting; I've always wondered about the internals of those things, as I stared at mine while pedaling up some steep grade.

I'm also curious about what the electronic derailleurs and shifters run.

Re: Welcome to Hell Developer

#8

Post by procone »

I found this really hard to read due to the Claude-isms. "Classic" chicken and egg problem? 39 em-dashes, random numbered lists, etc.

If you're not going to even bother to take the time to write an article, why should I waste my time reading it?

Re: Welcome to Hell Developer

#10

Post by hmcamp »

procone wrote: post #8

I found this really hard to read due to the Claude-isms. "Classic" chicken and egg problem? 39 em-dashes, random numbered lists, etc. If you're not going to even bother to take the time to write an article, why should I waste my time reading it?

I read it and found it useful

\_(^ ^)_/

Post reply on HN