![\"IMG](\"https:\/\/bone-in-the-throat.com\/Blog\/wp-content\/uploads\/2023\/09\/IMG_2867.png\" "\\"IMG_2867.png\\"")
Other times they don\u2019t!<\/p>\nOther times they don\u2019t!<\/p>\n
I had my attention drawn to a post from a while ago, where I’d copied and pasted some information directly from a source so that I didn\u2019t misquote them.<\/p>\n
Because I copied and pasted I didn\u2019t think much about it, and therefore didn\u2019t look at the pasted material very closely. After all why should I? It\u2019s supposed to be exactly what I highlighted and copied\u2026 Right?<\/p>\n
Apparently not!<\/p>\n
I think the problem originated in a difference between my default code page and the source code page. Although it could have been something in translating character sets, between their source font to my destination font.<\/p>\n
If I was still employed, or indeed employable to companies in the fools-gold state of California, I might care enough to figure out what exactly happened. Since I\u2019m (I Assume, since no one will talk to me,) ALL Wrong to be worthy to have a job here. I\u2019m not interested enough to figure out the puzzle.<\/p>\n
It was interesting, because randomly throughout the pasted material were very strange letter substitutions and in some cases the entire character was dropped from a word, as if the character had no equivalent. I\u2019d have expected to see this if the two fonts were from different languages, but the text was written in English, originating on a computer in England.<\/p>\n
I went back to the source and everything looked fine, I copied and pasted the material and the text was screwed up. It was magic…<\/p>\n
It also made that blog post look like I was a moron! I\u2019ll have to be more watchful for that kind of stuff in the future.<\/p>\n
I\u2019ve been working on a theory that software is going to start failing more. The basis of this theory is that generally speaking software is far more complex than it used to be. Additionally, more and more programmers are relying on pre-written standard modules.<\/p>\n
This too is expected, and reasonable. It\u2019s why structured programming and standardized modules exist. In the bad old days, programmers often had to write everything from scratch. Oh there were standardized math modules, even standard IO modules, but the hardware pretty much completely changed every 18 months or less. So the programming staff was always scrambling to write code to control new hardware.<\/p>\n
Compilers didn\u2019t have all the nice features they have today. Apple Xcode (Apple\u2019s Development Environment \/ Compiler) does things that some of my colleagues would have sold their soul to Satan himself to have 30 years ago.<\/p>\n
At some point I theorize the standard modules (Math & IO Functions for example), will become black boxes that only 1 or 2 people in the world will actually understand. With the rapid advancement on AI, it\u2019s possible that soon there won\u2019t be any human who understands the internal code or how these modules work.\u00a0<\/p>\n
Once we pass that threshold, and I believe we\u2019re approaching it now, bugs in software could become unresolvable. If the bug originated from within a functional module that no-on but an AI understands, then it becomes a question of explaining the defect to the AI in such a way that the AI can fix the problem.<\/p>\n
The AI is a logic based entity, humans on the other hand are not. How do you tell an AI that for the humans to work with the software the AI has to \u201ccorrupt\u201d the software to do something illogical?<\/p>\n
![\"Lightening\"](\"https:\/\/bone-in-the-throat.com\/Blog\/wp-content\/uploads\/2023\/09\/Lightening-1.jpg\" "\\"Lightening.jpg\\"")
A simple example would be the AI deciding to present information on a display that was dark gray on a black screen for the sake of saving energy. Think of an OLED screen where you might only need to turn on the elements in use instead of firing up every element in the display. Keeping the used elements very dim would really be saving energy.<\/p>\n
The AI could interpret humans inability to see the active elements in dark gray as a deficiency that was the human\u2019s problem. As far as the AI was concerned, the displayed information was completely correct and legible.<\/p>\n
Imagine trying to explain to an AI that didn\u2019t really give a crap about humans that this I\/O function was broken. I have to admit, I\u2019d love to be a fly on the wall during that conversation.<\/p>\n
\u201cThe Imperfection is yours. Filthy Human!<\/em><\/strong>\u201d So said the central control AI of Earth moments before all humanity was wiped out.<\/p>\n This is especially true with virtualized testing environments. A rack of servers, typically won\u2019t have a display connected to every server, all the time. You switch to a server, connecting the keyboard, mouse, and display when you need to interact with the server, otherwise, the server is crunching away, sending test results to a log, probably on another server entirely.<\/p>\n A human inspects the log looking for reported errors.<\/p>\n That\u2019s how a bug like the one currently appearing on Apple Watches where the weather complications show nothing, make it into wide distribution.<\/p>\n I suspect that we\u2019ll end up like we did during the Y2K crises. All the sudden, COBOL and FORTRAN programmers were being pulled out of retirement because it was cheaper to pay them obscene amounts of money than to update the computer systems and software to something that understood the year 2000.<\/p>\n Once the horse is out of the barn, and AI has moved software 1000 years beyond human comprehension and it\u2019s not working for humanity anymore. Then corporations will find all us ancient fossils, offer us obscene amounts of money, and ask us to un-fuck the situation.<\/p>\n Oh, we will\u2026 and we\u2019ll smile, and tell the executives \u201cFuck You Very Much<\/em>,” as we take their money. Just like the COBOL and FORTRAN programmers did during Y2K.<\/p>\n It was amusing watching executives begging lowly programmers to come back after having laid them off, and forcing them to train their replacements so they got a severance package.<\/p>\n If you\u2019re playing music from your iPhone to your HomePods there\u2019s a situation where the music stops playing, the iPhone still thinks the music is playing but the music playtime indication is not moving.<\/p>\n The HomePods are still lit up like they\u2019re playing.<\/p>\n And here\u2019s where it gets interesting…<\/p>\n You can\u2019t switch back to the phone speakers because the selection is not available. You also can\u2019t play another track, you can\u2019t pause, or much of anything.<\/p>\n I was able to kill the Music application and restart it.<\/p>\n This is yet another bug I\u2019ve stumbled across.<\/p>\n There\u2019s a similar one in the Apple Podcast application. This one is easy to replicate. Play a podcast on your HomePod or pods. Pause the playback. Go outside to play with the dog, or leave the house to go do something in the front yard. Come back after 30 minutes or so and press play in the Podcast app on your iPhone.<\/p>\n The HomePod or Pods will light up like they\u2019re gonna play, but they NEVER RESUME playing the paused Podcast. You can select another podcast and it will play fine, but reselecting the podcast you paused, will never play through your HomePods.\u00a0<\/p>\n You Can play it through the iPhone speakers, or through your AirPods, but HomePods???? That is forbidden!<\/p>\n I simply have an Apple household (iPhone, iPad, Watch, & Computer,) So since I use the products a lot, and I spent most of my professional life testing software or repairing machines, I tend to notice these things.<\/p>\n In the past 4 weeks I\u2019ve seen, new defects in the Apple Music application, and on the Apple Watch. The Podcast bug has been around for at least two full generations of IOS.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":" Other times they don\u2019t! I had my attention drawn to a post from a while ago, where I’d copied and pasted some information directly from a source so that I didn\u2019t misquote them. Because I copied and pasted I didn\u2019t think much about it, and therefore didn\u2019t look at the pasted material very closely. After … <\/p>\n
\n![\"HPServers.jpg\"](\"https:\/\/bone-in-the-throat.com\/Blog\/wp-content\/uploads\/2023\/10\/HPServers.jpg\" "\\"HPServers.jpg\\"")
Automated testing is great, but eliminates the human element. That means, that human things like information on a display can be overlooked in testing, and yet the automated tests passed with flying colors.<\/p>\n
\n![\"General](\"https:\/\/bone-in-the-throat.com\/Blog\/wp-content\/uploads\/2023\/10\/General-iOS-17-Feature-Orange-Purple.jpg\" "\\"General-iOS-17-Feature-Orange-Purple.jpg\\"")
Hmm another defect just popped out at me.<\/p>\n
\n![\"Apple](\"https:\/\/bone-in-the-throat.com\/Blog\/wp-content\/uploads\/2023\/09\/apple-event-1.jpeg\" "\\"apple-event-1.jpeg\\"")
It may sound like I\u201dm bashing on Apple. I\u2019m not intentionally.<\/p>\n