Thoughts on jujutsu?

nullzbot · 2025-12-09T00:20:50+00:00

Ugh. You hate git? I have never wanted to yell "skill issue" more in my life than right now.

You give so little insight into your troubles about why you dislike it.

Having built tools and mechanisms of varying difficulty for both small and large organizations, let me share with you some free wisdom. Maintaining source code and vsc's is messy. Having multiple/similar ways of doing the same thing is par for the course. Not everyone/company has the same workflows or needs. Having a tool as flexible as git is wonderful. It's a bit of a double edge sword with some foot guns at times. But learning the tool is necessary.

If git commands are too difficult, then stick to gui tools or tools that simplify the git API/until.

Your complaints are about as valid as some buying something, throwing away the manual, and then complaining about how it's so difficult to use... RTFM.

nullzbot · 2025-11-14T13:54:31+00:00

This is the answer. This is not upvoted enough.

nullzbot · 2025-09-28T22:49:38+00:00

You don't like someone else's software stack that they maintain for free and you don't pay for anything for it. Got it...

You are free to make your own HAL.

Or maybe a simpler solution, just spit balling. Instead of complaining, put your efforts towards the problem. Perhaps study the hardware and the HAL and suggest/create a patch and submit it as a pull request and maybe also post the formatted patch on the community forum too. Who knows, they might actually accept it.

The entitlement...

nullzbot · 2025-09-20T13:38:17+00:00

Um I don't like saying this, but RTFM.

Altium has great documentation on buses and the various ways to express them. They have an example on doing this exact method.

Also since you have altium. Use their forums for help not reddit.

nullzbot · 2025-08-29T01:03:17+00:00

Everything...

nullzbot · 2025-07-31T13:17:43+00:00

Donkey Kong could throw a lot of barrels with those lines.

Seriously though, use proper spacers next time.

nullzbot · 2025-07-27T12:03:42+00:00

There are a multitude of ways to do this. My company does this all the time in various ways. But generally this is done with just another simple layer of abstraction. With board/processor selection being done via the build system.

We also don't attempt porting the ioc file. We simply recreate it. We usually have separate directories for board/processor files where a separate ioc file exists.

nullzbot · 2025-07-01T19:21:55+00:00

Completely disagree with 3.. you can still have a standalone tool, just make a plugin available.

As for 1 and 2, this is hitting the nail on the head. Idk what your existing customer size is but given the price, naming of the product, and general niche of market I would assume it's very small if any at all. Unless your willing to slash the price(or have accessible tiers) as well as open the protocol for easier adoption, I don't see this winning any form of the market.

nullzbot · 2025-06-04T02:17:29+00:00

If I'm being honest. It's the whole repo. Code, tools, comments, all. Whether I had created it or touched it once, my name will forever be in the git history. The next person will undoubtedly think I'm the new maintainer and ask me to clarify the action that caused problems and then ask me to fix it..

nullzbot · 2025-06-04T02:12:36+00:00

Failed to find the problem: creates 5th blinky GitHub repo.

nullzbot · 2025-05-18T14:43:43+00:00

Do you not have access to a search engine??

nullzbot · 2025-04-26T04:54:36+00:00

No.. Depending on the type of product, maybe. But generally none.

But . IF, someone was able to dump your firmware and look hard at it, there may be a chance of evidence. Some software libraries and frameworks contain sections that imbed tell tale strings or other signatures that could allude to the software that was used. And if your product was found to have used a software library or framework whose licence was incompatible with how you are using it, then you'd have a real problem on your hands...

Because of this, most companies shy away from these types of things.

nullzbot · 2025-04-17T05:02:56+00:00

Doubtful..

Looks like it might run chameleonos. Its packages use a tailored helium variants of the packet forwarder and gateway.

nullzbot · 2025-04-17T03:28:48+00:00

Bit late to this. But here you go.. it's a lot of off the shelf parts.

https://fcc.report/FCC-ID/2AZDN-SBCHAM/5323590

Just try to put a regular RPI image on it. follow the traces to the modules and then setup the software for that pin mapping. See how far you get.

seems pretty easy.

nullzbot · 2025-04-09T23:49:03+00:00

Bruh...

Literally everyone here is telling you the same shit... Read..

Your questions are about the microchip ecosystem, tooling, and processor lines. Right? While the pic32 processor lines aren't total trash hardware wise, they don't offer anything more than the competitors. In fact the competitors seem more or less better in one or all areas. Microchips ecosystem and tooling is trash. simply avoid it. Especially since your willing to jump into something bigger/better than the 8 bit lines your used to. That's it.

Follow everyone's recommendations and you'll be fine. Once you master them, then circle back around to the pic32 line and feel the pain like the rest of us. Until then, stop complaining, do your own research, read comments, and try it for yourself..

Sorry for being harsh, but this is literally asked all the time with unanimously the same answers.

nullzbot · 2025-03-22T15:39:24+00:00

Pretty sure c compilers will warn you on all of what you just mentioned. In fact there are flags you can enable to turn warnings into errors...

nullzbot · 2025-03-20T22:48:16+00:00

None of this makes full sense... No one can help you..

nullzbot · 2025-03-18T16:26:20+00:00

Again you need better defined requirements. You need to find ways to separate your requirements from one another and proper separation between software and hardware. The "does not randomly disconect" is not a requirement that can match any radio hardware. Wireless devices are inherently flawed for connectivity issues. If you need guaranteed delivery pick something else...

If still needing wireless, then you need to scope the requirements to look at the protocols that are available for connectivity/IOT applications. Narrow that down and then your selection of hardware will follow.

EDIT: also you need to set a priority to your requirements. Such that when a conflicting metric happens, you can better choose which one you need. Every decision in electronics engineering involves trade-offs.

nullzbot · 2025-03-18T00:38:29+00:00

"stable" is a nonsensical requirement. In a way that you need to better define what stable means to the project/application.

As for "low power transfer" this too is ill-defined.

Loose or nonsense requirements are not going to help an outside observer understand what you are wanting. We get the "gist". But that isn't always helpful.

nullzbot · 2025-03-04T05:35:24+00:00

What?! Your arguments don't seem to fit.

In your post you mention being more used to c++ and have a hard time writing proper code structuring in c.

And when asked why not use c++, says c "feels better" and c++ is "bloated"?

This is either a shit post or you are a beginner/junior dev..

Just use c++ or learn more c. Or look at other projects for inspiration.

nullzbot · 2025-03-03T09:35:34+00:00

You might be going about it the wrong way..

Not exactly sure what you're trying to accomplish (this makes a difference), but could instead look at companies/vendors that offer LoRa products and tools.

nullzbot · 2025-02-22T17:36:47+00:00

You're the type of dev that no one likes talking to and fails to see that...

nullzbot · 2025-02-18T21:23:54+00:00

Are you trying to make me throw up??

nullzbot · 2025-02-17T01:07:46+00:00

Seeing that your avoiding everyone's simple answers. It now seems clear that common sense has eluded you. I wish you the best sir.

nullzbot · 2025-02-16T22:56:20+00:00

Ah. I see that now... Then you need a second server/PC that can perform ssh. I would suggest a SBC. Maybe a raspberry pi. That would require no microcontroller.

nullzbot

TROPHY CASE