I cannot emphasize enough the importance of correct data entry.
I was having a problem with connecting to a web API service with
an ESP32 processor.
It didn't make sense as the very same code worked fine with a UNO WiFi.
The code in each appeared to be identical when placed side by side. Huh?
On closer examination my eyes caught the slight difference on
the DOT com entry of the server name definition under my constants.h file.
"api.pushingbox,com" is not "api.pushingbox.com".
My geriatric eyes almost did not catch it at first.
Compilers cannot catch all our human screwups unfortunately.
Oldest computer acronym: GIGO -- Garbage In, Garbage Out!
Years ago, when my eyes were better but printing was worse, I spent 3 weeks hunting for a : that was typed as a ;
Also had a recurring problem with big cust that was traced to a 0 typed as an O in the customers specification memo. I had cleverly copy/pasted their memo to insure no transcription error could occur. Took MONTHS to find and nearly cost us a multimillion $$$ contract. Good thing it was the CLIENTS fault!
Yepper. Revealed who was at fault on conf. call after being raked over coals for error. Cust got real quiet when I quipped "Oh we got that fixed." and mentioned typo in THEIR original memo (which EVERYONE on the call had a copy of).
When I worked as a designer and contractor, I'd often just sell the design work and the customer would choose whatever cheap-@ss contractor that they wanted, and occasionally we got contracted to build the projects for a couple different engineering firms.
One of the latter was an historical remodel for a state supreme court justice. The architect, her first project, talked down to me, a mere contractor on a regular basis.
On one particular conference call I mentioned that we needed to work a header into a particular inner wall and create a bearing path with a beefer LPI joist under the floor in parallel, so as to distribute the load to the foundation walls without adding poles and new footings in the center of the basement. The client was on this call. The architect got very snippy with me about her degree and the fact that everything had been accounted for.
Turns out that she had never studied pre-civil war home design, wherein the central bearing was split between two walls. She went on to fire me in the middle of the call. Being fired, I disconnected from the call.
About 15 minutes later, the client called me directly and asked me to hire another firm to verify my findings. I did and I was right. So, they hired me back, out of the architect's contract, and I received the architect's 30% admin fee on top of the original contracted price. Also got a big stream of lawyers calling for design work after that.
