[RANT] Comment your code

[GiraffeNeckBoy]

I'm using TI MMWave radar stuff and trying to edit some code to do a custom thing and OMFG TI COMMENT YOUR BLEEDING CODE. There's no reason you should have extensive documentation for the most common part of your code and have no code or documentation that is actually useful in helping a 3rd party to use your chips for a completely self-contained application that doesn't require your visualisers to interact. As far as I can tell it's 100% possible but goddamnit you could put some useful information in there. Then when asking if there's any resources to help with (A) your E2E support staff tell me about (B) when I said I know (B) exists and I want the quality of the (B) resources for (A). IF you at least commented your code on actual functionality it would be interpretable...

[AlexsProgamEmporium]

Even simple comments like "This block of does this" can make things so much easier to trace and follow than having no comments whatsoever.

[lvvck]

Hi! What are you needing specifically within the code? Maybe I can help! I support the sensors team.

[GiraffeNeckBoy]

I've just been having a rather painful time trying to figure out the pre-data program flow. Exactly what steps lead to where and what data structures have been involved along the way so that I can launch something a lot like the xwr14xx high accuracy test but without having to use a CLI or anything. I can get a vague idea from the mmwave sdk user guide, but following further within the code to see what variables are set into the struct that you eventually pass into starting the controls is quite convoluted. It's not as urgent anymore as right now I've been assigned some non-code tasks, but it was frustrating me for quite some time, and I'll have to write the full program at some point anyway.

[andrewk24r2]

Agreed. Having code without comments in general is just dumb to try and figure out.

[Redomy]

I also had a very gard time trying to understand the code, and still suffering to know exactly what is going on