572 karma · joined September 11, 2014
I'm saying put it out. Less CO2 released.
We had a modem tied to an OPXI, which required that our dial strings in Telit (remember that? I liked it better than Procomm) start with "91,", which was 9 for an outside trunk, then 1 to select a trunk, then a comma for a pause. Then the phone number of the BBS site.
The OPXI messed with the newer modem speeds. One Friday I decided that we didn't really need the OPXI if I bridged the modem with the fax line, so I did.
I didn't tell anyone. That was a mistake.
Monday morning I showed up for work and my boss (the chief engineer and president) called me into his office. Uh oh.
He said, "Did you remove the OPXI from the modem line in the lab?" "Yes." "Why?" "Because we didn't need it."
He then told me about how he came in on Saturday, finished up some PCB artwork and went to dial into the board fabricator's BBS to upload the files (long distance), and kept getting failures to connect. He tried it a bunch of times before he heard banging on the front door. He went to the front and there were multiple police officers outside. They said there were multiple 911 hangups from this location and wanted to know why. He swore that he was the only one there and there were no 911 calls. They then wanted to come in and look around the building, so he let them.
After they left, he put it all together. The dial strings were set up to dial 91,1-areacode-phonenumber which dialed 911 emergency without the OPXI in the path.
He verified that the OPXI was no longer in the loop and was ticked off. He knew immediately who did it.
He said, "Things you do to systems other people use can have unintended consequences. Please think those things completely through in the future."
Good advice, and I still hear his voice in my head today when I'm reconfiguring something.
One was a series of electronic game callers used by hunters to kill coyotes. I'm not opposed to hunting, and I realize coyotes are predators, but with the caller, the coyotes don't stand a chance.
The second was a commercial PC product that didn't end well. For me. It ended pretty well for others.
https://www.amusingplanet.com/2015/03/ancient-tsunami-warnin...
I've been coding for hire since I was 13, and I'm in my early 50's. I always loved electronics so about 20 years ago I moved into embedded. I left the rat race of the latest language / latest libraries etc. I code in straight C and maybe some assembly if the task demands it.
I feel I get better every year, and the demand and pay shows that. The only thing I've noticed is that I'm slower to anger and more willing to listen to ideas, but like you said, my BS meter is very sensitive.
About the only age-related thing I've noticed is that it takes me longer to heal when I injure something. I can't participate as easily with softball on the parking lot or even frisbee.
I'm not an expert; I truly learn something new EVERY DAY. The difference now is that I can often out-think my coworkers that are in their 20's, all from experience. About twice a year I get to work on things that have never been done before. Mostly, though, it is state machine after state machine, but to be honest, I've never found a lack of motivation with embedded.
It seems that there will always be a need for firmware down on bare metal. At least I'm banking on it, and plan to be doing this for 20 more years or so. As far as "making it big", I don't care. That was never a huge goal. I just wanted to provide for my family and retire some day.
PC app development is a different story. I was burned one too many times and cannot concentrate to write ANYTHING. Why that is (or what the difference is) I don't know.