An irrelevant but interesting take is that this applies as an analogue to a lot of stuff in electronics related space.

• It is harder to receive data than to transmit it, because you need to do things like:
  • match your receiver's frequency with that of the transmission (which might be minutely different from the agreed upon frequency), to understand it
  • know how long the data will be, before feeding into digital variables, or you might combine multiple messages or leave out some stuff without realising
• this gets even harder when it is wireless, because now, you have noise, which is often, valid communication among other devices

Getting back to code, you now need to get in the same "wavelength" as the one who wrote the code, at the time they wrote the code.

I weirdly love reading code and figuring out what it's doing. Debugging is cathartic.

It might take a while and I might be cussing up a storm saying, wtf is this shit? Why the fuck would you do it this way? Why the fuck did you make this convoluted for no reason?

Right now it's unfucking some vibe coded bs where instead of just fixing an API to get the info we needed accurately, it's trying to infer it from other data. Like, there is a super direct and simple route, but instead there are hundreds of lines to work around hitting the wrong endpoint and getting data missing the details we need.

Plus letting the vibe add so much that is literally never used, was never needed, and on top of that returns incorrect information.