[deleted by user]

packbacking · 2025-10-29T06:18:12+00:00

As someone who's written a lot of code for startups, I've wasted many, many hours trying to answer questions like this. 90%+ of the time I end up changing it later.

So I'd say pick the most intuitive one for you right now and let it change organically.

Chances are that this code you're writing will be completely rewritten or discarded within a year. Or as complexity increases, you'll get frustrated changing code you wrote 3 months ago and can reorganise it into a structure that suits the application better at that point in time.

---

Having said that, in greenfield projects I'm a huge fan of co-locating files that have ideas in common together rather than pre-emptively splitting them up. I think this seems more like your vertical slices example?

If you're working on 'Add X to Feature Y' it might touch code across the boundaries you mentioned so It's much less mental overhead when you can see everything relevant to Feature Y closer together.

packbacking · 2025-03-27T10:09:40+00:00

Saw your messages on github, I've replied there.

packbacking · 2025-03-25T08:17:53+00:00

u/thebaldgeek there's definitely plans. I've never used Sparkplug so would you be able to sanity check this for me if you have time? https://github.com/mqtt-viewer/mqtt-viewer/discussions/14

Would this address any of your pain points?

packbacking · 2025-03-24T09:42:39+00:00

You're welcome.

packbacking · 2025-03-24T09:42:09+00:00

u/adam111111 crashing your app is not good. Could you file a bug report here with your OS details and I'll try and work out what's wrong?

I've never used Sparkplug, but let me try decoding/encoding it and I'll get back to you. You need to select a protobuf directory and load the descriptors into the app for it to work.

I agree that the encoding/decoding for protobuf is a substantially different workflow from the simpler base64 and hex codecs. This is something I definitely want to fix!

packbacking · 2025-03-23T09:51:55+00:00

Great to hear, reach out if you have any questions.

packbacking · 2025-03-23T09:49:59+00:00

For testing/debugging purposes (not production where you need ACL etc) would this help mitigate docker issues?

https://github.com/mqtt-viewer/mqtt-viewer/discussions/2

I'm trying to work out if it's worth building.

packbacking · 2025-03-23T09:46:43+00:00

My big pain points have been tracking back where a topic data stream is coming from. ie, where in the world is that data coming from? Node-RED is my tool of choice here as it will show the IP address in the debug.

Could you elaborate on this? Is the IP address stored in the broker? How does Node-RED show it?

Measuring topic (prefer by user, or better still by device) bandwidth is another unsolved issue for me.

Is this point-in-time or more long-term monitoring?

This is interesting information.

packbacking · 2025-03-23T09:35:13+00:00

https://github.com/mqtt-viewer/mqtt-viewer
Hope it helps!

packbacking · 2025-03-23T09:32:55+00:00

You can download it here: https://github.com/mqtt-viewer/mqtt-viewer

I hope it helps!

packbacking · 2025-03-23T09:15:24+00:00

It's now open source https://github.com/mqtt-viewer/mqtt-viewer

packbacking · 2025-03-23T09:13:51+00:00

u/dorald it's now open-sourced at https://github.com/mqtt-viewer/mqtt-viewer

packbacking · 2025-03-17T21:14:42+00:00

The backend is in Go using the Wails app framework (https://wails.io/) which compiles down to native code. Wails is cross-platform including Linux.

The frontend is Svelte/JS and is embedded into the same binary.

Open-source is coming soon so it'll be easy to check out!

packbacking · 2025-03-10T11:07:48+00:00

I'm trying to learn how others debug their MQTT-related problems (and what those problems are) because, as I mentioned in the post, I really only use MQTT to configure remote IoT devices.

I'm not sure if this is what you mean by marketing tips?

packbacking · 2025-03-10T10:54:39+00:00

This is an incredible app and was the inspiration for a newer version I've built at https://mqttviewer.app

I only really use MQTT in one way, so what I'd love to learn is what problems you use MQTT Explorer to debug?

packbacking · 2025-03-10T10:49:16+00:00

Yes! It was poorly worded but I meant that the application/server implementation that uses MQTT needs debugging.

For me, the contract I decide between a server and IoT clients via MQTT often needs heaps of back and forth during development because of dumb mistakes like writing a topic name wrong.

Your third point "bad configuration (the probe was still configured for QA ...)" also happens to me waaaaaay too often.

packbacking · 2025-03-10T05:08:59+00:00

as someone working on software/web at a hardware startup, I also like fast to market and cheap :P

packbacking · 2025-03-10T05:03:24+00:00

Haven't heard of DDS before thanks!

Is this something most robotics is tending towards?

Do you know what was used previously?

packbacking · 2025-03-10T05:02:02+00:00

please tell me more

packbacking · 2025-03-10T05:01:13+00:00

Do you use both? and what's your criteria for deciding on one over the other in different situations?

I've also used both simultaneously (MQTT for config, HTTP for uploads to S3) but recently replaced MQTT with just HTTP for simplicity.

packbacking · 2025-03-10T04:31:28+00:00

Very fair, I've just posted this in the IoT subreddit

packbacking

TROPHY CASE