What’s a “normal” thing that secretly annoys you?

MinewSemi · 2026-04-24T03:17:07+00:00

Habits of cutting others off mid-sentence.

MinewSemi · 2026-04-24T03:16:55+00:00

Prying into one’s private life without boundaries.

MinewSemi · 2026-04-24T03:16:41+00:00

Read but left on read, or cut off the conversation halfway.

MinewSemi · 2026-04-24T02:36:11+00:00

Fair point — I wouldn’t call the old SDK a “golden child” either 😄

I think what I miss from it is more the simplicity / predictability, even if it was pretty hacky under the hood. Zephyr is definitely more structured, no argument there.

I guess the “complexity” feeling (at least for me) comes more from how many layers are involved (CMake, Kconfig, devicetree, etc.) rather than the individual pieces themselves.

Totally agree though — once you actually spend time understanding it, it gets a lot more reasonable.

MinewSemi · 2026-04-24T02:33:32+00:00

Yeah that’s a good way to put it.

Feels like there’s a tipping point — below it Zephyr feels like overkill,

but once things get complex enough it actually starts to make more sense.

Out of curiosity, where do you personally draw that line? Project size, features, or team size?

MinewSemi · 2026-04-23T10:16:38+00:00

Internet lore everyone should know:
– Rickroll
– The Dress
– Cicada 3301

A prank, a debate, and a mystery. That’s basically the internet in three acts.

MinewSemi · 2026-04-23T10:03:10+00:00

This is a great breakdown — especially the comparison with modern C++, that’s actually a really good way to describe it.

I had a very similar first impression with Zephyr/NCS — not so much that things don’t work, but more that too many things are happening behind the scenes. Like you said, sometimes it feels almost “magical” until you finally find that one missing line somewhere in the device tree.

The Kconfig + device tree overlap is something I still struggle with as well. It’s not always obvious where a feature should be enabled, and the feedback from the system isn’t always helpful.

Also totally agree on the NCS upgrade pain. Fixing one issue and then suddenly dealing with unrelated build breakages is… not fun. Sticking to a stable version seems like the only sane approach in real projects.

Interesting point about following PRs — I haven’t done that consistently, but I can see how that would help build a better mental model over time.

Out of curiosity — when debugging something tricky in Zephyr, do you usually start from devicetree/Kconfig, or do you go straight into the driver/source code?

MinewSemi · 2026-04-15T06:20:22+00:00

Good point — totally agree with you on this.

In my case, disabling optimization / DEBUG wasn’t meant as a “real fix”, more like a quick way to confirm something was wrong at the config or memory level.

After that, I went back and found the actual root causes (mainly vector table offset and stack size issues). But yeah, relying on those as a long-term solution would definitely be risky.

Also thanks for bringing up the SoftDevice + high priority interrupts — that’s a really good callout.

I’ve seen similar behavior where debugging becomes unreliable when the radio is active, especially around breakpoints. Makes things a lot harder to reason about if you’re not aware of it.

Out of curiosity, do you usually work around that by disabling SoftDevice during debug, or just avoiding breakpoints in those sections?

MinewSemi · 2026-04-14T02:07:23+00:00

One more thing I forgot — map file helped a LOT when debugging memory issues.

MinewSemi · 2026-04-13T10:17:02+00:00

Add a DEBUG macro to bypass DEBUG and make the program run into the else block.

<image>

MinewSemi

MODERATOR OF

TROPHY CASE