Does anyone know the story of the dev who was playing a game, encountered a bug and submitted feedback? The company ignored him, but they were hiring so he applied. He was hired, spent his time there fixing the bug that he had originally submitted, then as soon as it was implemented he quit. What a chad.
Common story, very funny though. I’m actually working at a SaaS vendor I used to use, and their search was unusable. I finally got to fix it and am very happy about it
Not always, it really depends on what the person who did the board layout or wrote the firmware thought. When I do a board/firmware I label it from the devices perspective, so the TX is where the bits I’m transmitting will be coming out of, RX is where I’m expecting your bits to be sent to. Others label it from the perspective of the device connecting to it. So TX is where you connect the line your sending bits from. To me that’s wierd because, to others it’s what they expect. There is no standard and the result is you end up hooking it to an oscilloscope and see which line bits are being sent from. Then you use the scope to figure out all the settings. If they don’t transmit in power up then… Frustration ensures
I have given up on Logic when dealing with clients… Trying to figure out what they actually mean is never what they actually mean.
It seriously blows my mind that some of these people are like CEO status of huge companies. How they even function in every day society and remember to breath is beyond me.
programmerhumor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.