<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Darren Black on Medium]]></title>
        <description><![CDATA[Stories by Darren Black on Medium]]></description>
        <link>https://medium.com/@drdaz7?source=rss-de91d8129642------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*qg5Eak-mN3xmDhp-vka46Q.jpeg</url>
            <title>Stories by Darren Black on Medium</title>
            <link>https://medium.com/@drdaz7?source=rss-de91d8129642------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:19:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drdaz7/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Apple Customer Service — Fail Different.]]></title>
            <link>https://medium.com/@drdaz7/apple-customer-service-fail-different-230b82a43dd1?source=rss-de91d8129642------2</link>
            <guid isPermaLink="false">https://medium.com/p/230b82a43dd1</guid>
            <category><![CDATA[saga]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Darren Black]]></dc:creator>
            <pubDate>Thu, 22 Aug 2019 20:58:51 GMT</pubDate>
            <atom:updated>2019-08-23T12:48:11.588Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C2N9z4Oozfj1TQYc47G7IA.jpeg" /></figure><h3><strong>Apple Customer Service</strong></h3><h4><strong>Operating at the Intersection of Greed and Incompetence</strong></h4><p><em>I’ve been a vocal Apple fan since the mid 1980’s. What follows is a lively description of the single worst experience I’ve ever had as a consumer, provided by my favourite company.</em></p><p><em>A year of Apple refusing to do the right thing, denying responsibility and prioritising greed over customer experience, for your reading pleasure.</em></p><h3><strong>My Apple History</strong></h3><p>I first encountered Apple computers living in San Diego, as a 5 year old, at a Montessori in 1984/85. I remember using the original Macintosh for the first time. I remember the 2-sectioned arrangement of the computer room I was in, the beige color of the walls, and the warm California air against my skin. I remember the thrill of having intuitive control of such a powerful thing.</p><p>It made a serious impact on young me. I knew then that technology, and particularly this company’s technology, would be really important in my life.</p><p>And so it has been. I’m a software engineer with 12 years in the pro game. I’ve worked on several mission-critical, national infrastructure-class IT systems. I run a consultancy with a speciality developing software for Apple’s ecosystem and have numerous apps in the App Store. I’ve gladly invested a lot of headspace, time and money into the Cupertino company’s work.</p><h3><strong>Time to Upgrade</strong></h3><p>In the summer of 2018, I decided to invest in a new workstation to replace my faithful iMac. It still performed wonderfully. In 6 years of use, I’d never needed support with it. I never had any trouble with it that I couldn’t deal with myself. It was the real Apple Experience™; plug it in, and it <em>works with you</em>. For years. No bullshit.</p><p>But I wanted to be mobile, and Apple’s new 2018 MacBook Pros looked pretty sweet. So I went all-in and built a dream setup. I bought a highly-specced 15 inch MacBook Pro (6-Core i7 2.6GHz, Radeon 560X, 16GB RAM, 1TB SSD) for an eye-watering £3000. I paired it with a universally lauded <a href="https://www.techradar.com/reviews/caldigit-ts3-plus-thunderbolt-3-docking-station">Thunderbolt 3 docking station</a> and a pair of the <a href="https://www.amazon.co.uk/LG-Electronics-27UD68-W-AEU-27UD68-Monitor/dp/B01AN14SEO/">best-selling 27-inch 4k screens on Amazon</a>; mounted on <a href="https://www.amazon.com/Ergotech-Freedom-Single-Aluminum-Monitor/dp/B00CEHME92">badass arms</a>. I intentionally chose some of the most popular and highly recommended hardware options to minimise the risk of trouble / incompatibility.</p><p>Having worked with dual screens before, I was really looking forward to enhanced productivity compared to my single-screen iMac setup.</p><p>And as a first for me, I bought Apple Care, (an extension to Apple’s standard after-sales support services) to make sure I got the very best experience available to me. I’d read so many good things about it.</p><p>If only I knew what lay ahead…</p><h3><strong>A Difficult Start</strong></h3><p>After assembling this developer’s paradise, I connected the laptop. Within the first half hour of use, the machine crashed hard, resetting itself. This happened frequently; 10+ times in the first evening. Screens were glitching out and turning on and off seemingly at random. The inactive machine was burning up to a worrying temperature and spinning fans, even while sleeping — it felt dangerous to leave it unattended.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F352039063%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F352039063&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F803806287_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/e96b58302f1ae438f9622039251b55ce/href">https://medium.com/media/e96b58302f1ae438f9622039251b55ce/href</a></iframe><p>Sometimes when waking from sleep, the machine would switch 1 or 2 screens on and off in a rapid loop. If the battery ran all the way down, upon charging again the machine was largely unresponsive, with screens flashing on and off, before everything froze up completely. Sometimes when asleep, the machine would start switching screens on and off at random. All of these things required me to perform a hard reset (losing any work in progress) to regain control of my computer.</p><p>And there was so much more. Even for an experienced power-nerd like me, it was hard to know where to start. New, unwanted behaviour cropped up on an almost daily basis. Suddenly, I found myself in an awful, epilepsy-inducing circus that used to be where I did my work.</p><p>There were just so many things wrong with this machine’s behaviour, and some issues were so deeply troubling in nature, that I had to contact Apple Support within the first week. I was losing work multiple times a day.</p><p>It turns out, <a href="https://support.apple.com/en-us/HT208862">Apple’s funky new T2 architecture</a> wasn’t quite ready for prime-time yet, as was widely <a href="https://www.theverge.com/circuitbreaker/2018/7/25/17614016/apple-t2-chips-bridge-os-problems-kernel-panic">reported in the tech press</a>. Apple Support confirmed there were serious software-related issues with these machines in configurations like mine (using Thunderbolt 3 peripherals), and that they were collecting data for fixes.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F352044175%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F352044175&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F803812686_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/80bbe315300cf04d1a832a418d2a65ae/href">https://medium.com/media/80bbe315300cf04d1a832a418d2a65ae/href</a></iframe><p>As the owner of a malfunctioning product, I was pretty damn upset; this was not the Apple Experience™ I had paid so much for.</p><p>As an engineer, however, I understood this situation and the need for quality information in order to fix problems. So I was motivated (by necessity) to supply data that might help Apple convert my machine from a shiny, convulsing, £3000 turd into the mighty workhorse it was supposed to be. So I spent 3–7 hours per week on the phone with Apple’s tech support, explaining what was happening, writing up descriptions and collecting video, logs and diagnostics for their engineers to work with.</p><p>At one point as I was talking with one of Apple’s supporters about the mad things my computer was doing, he confessed that they couldn’t fix the issues I was seeing, and that they <em>hoped</em> the impending release of macOS Mojave would fix it.</p><p><strong>#HopeDrivenSupport</strong></p><p>macOS Mojave was released nearly 2 months after I received the computer, and well outside the 14 day return period.</p><p>The machine was <strong>completely</strong> unusable for work before this time. And I’d spent up to 56 hours of my time helping Apple debug to this point.</p><h3><strong>macOS Mojave to the rescue?</strong></h3><p>Well, no.</p><p>Mojave certainly improved things — instead of losing my work multiple times per day, under Mojave I was losing work multiple times per week, on average.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WeYT1bwdOhg6hRbd5UB-bQ.jpeg" /><figcaption>I’m so happy I could shit.</figcaption></figure><p>This seems like a good point to mention that I’ve built computers for over 20 years (including a few Hackintoshes, before it was easy) and I had been telling Apple Support from day one that I believed their hardware was at fault.</p><p>They kept me busy wiping my hard drive, reinstalling macOS (8 times before I refused to do it anymore) and messing around with cables and configurations. I performed a bunch of complex isolation testing to rule out non-Apple components as causal. Occasionally they would allude to potential software issues that they weren’t allowed to discuss. Every time there was an update to macOS, I needed to spend significant time confirming yet again that my issues persisted with and without all the components in my setup. And when the machine inevitably failed all by itself, I needed to supply them with new logs and information.</p><p>They insisted on repeatedly ruling out literally <em>every other cause</em> than their own product, to the point of absurdity.</p><p><em>And they insisted on using my time to do it.</em></p><p>At the peak of their insanity, they asked me to wipe my machine clean, reinstall macOS and stare at it (do literally nothing else, install no software, don’t touch it), potentially for weeks, until it perhaps failed. I couldn’t do anything else, otherwise I wouldn’t know when the failure occured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7M6AYIoTERh7TyxqHoFapg.jpeg" /></figure><p>This kind of crazy bullshit doesn’t fit very well into a challenging professional workflow. Despite this computer being aimed solely at demanding professional users, it was surprisingly hard to get that point across to them.</p><p>At one point I had 5 separate support cases open against this machine simultaneously, each with a different supporter, each relating to some severe, distinct problem that cropped up. And I was only reporting the most serious problems — every issue I reported would waste more of my productive time. Every now and again Apple Support would forget about my cases; weeks would go by, so I had to chase down the supporters myself, one by one, only to find out that no progress had been made.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F352042441%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F352042441&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F803810487_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/ec7a66e6198f1aad4d37d45b2ecc0d26/href">https://medium.com/media/ec7a66e6198f1aad4d37d45b2ecc0d26/href</a></iframe><p>While performing one of Apple’s many requested clean installs on the machine, I witnessed the creepiest thing I’ve ever seen a computer do. Immediately after formatting and reinstalling macOS, on an encrypted filesystem, I found a file I’d created in the previous installation. The creation date of the file was several days before the creation date of the newly created disk it was on. Yet another heinous issue to report. Yet more extra work.</p><p>You might be wondering then, why I didn’t buy a new machine to check whether I was right about the hardware being faulty. Unfortunately, while the machine <em>usually</em> failed catastrophically multiple times per week, it could also go for weeks without failure; 3.5 weeks was the record. So it would have been impossible to show, with any confidence, that a new machine was really working before the 14 day return window had closed.</p><p>Apple Support repeatedly denied my requests to attempt a hardware swap, or ease up on their return policies. <em>Either action would have allowed us to confirm or eliminate the laptop itself as the cause of the trouble.</em></p><p>And so my work with Apple Support continued for another 4 months. That’s up to 168 hours I’d used debugging this ridiculous laptop. I could have bought several new machines with the money earned, had I been able to bill those hours to a client.</p><h3><strong>Tim Cook to the rescue?</strong></h3><p>6 months in, there was no real progress and no timeframe for any progress to occur. My patience was worn thin by Apple’s inability to fix my issues and their unwillingness to attempt to replace the defective product. My career and psyche were suffering severely from the long-term effects of a malfunctioning workstation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F352047090%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F352047090&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F803816394_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/7ce3029d08df72f28218ff0811d0d816/href">https://medium.com/media/7ce3029d08df72f28218ff0811d0d816/href</a></iframe><p>By this point I was obviously fed up, and had told Apple’s technical supporters on numerous occasions that I wanted to talk to somebody capable of dealing with angry, dissatisfied customers. This had gone way beyond being just a technical problem for me, yet they repeatedly refused to escalate my case.</p><p>It all seemed pretty hopeless, so I wrote a mail to Apple CEO Tim Cook. I explained my long history with Apple, and the unfortunate predicament I found myself in.</p><p>The next day I received a call from a representative of Apple Executive Relations. Let’s call him Roger (his name isn’t Roger). Roger apologised for the struggle so far, but assured me that I’d be working with a dedicated senior-level supporter from here on, and that he would continue to monitor the case until it concluded.</p><p>This would have been great, if only it meant that the case would then conclude with a usable solution within a reasonable timeframe. Or perhaps just that these new higher-up people would be willing to try replacing the possessed laptop.</p><p>But it didn’t mean any of that.</p><p>My new, dedicated supporter described Roger to me as the man responsible for my satisfaction with Apple as a customer. I’d describe Roger in his role with Apple as a man with the emotional response of a thick, wooden plank with severe work-induced anxiety.</p><p>I told Roger and my new supporter that I was pretty sure we were dealing with a hardware issue, and that it would make a lot of sense to swap the machine out to confirm or eliminate that possibility. As before, they brushed off this notion.</p><p>I was pretty sure by this point though, so I voiced this opinion repeatedly to Roger over the next weeks, until he informed me that <strong><em>Apple had proof in the logs I provided that these were not hardware issues, but Apple software issues.</em></strong> Admitting this seemed to cause Roger a great deal of strain — rarely have I heard somebody sound so desperate not to say something. He angrily whispered it into the phone, suggesting that he wasn’t allowed to say it. Regardless, he was adamant that Apple’s engineers could see my issues in software and would fix them in software.</p><p>Sadly, this carried on for another 4 months; I continued to supply Apple Support with video, information and diagnostics, and I continued to lose work to this seizure-ridden failure of a computer. Apple continued to release software updates that didn’t fix my problems while Roger continued to insist that my problems would be fixed in software updates, and continued to deny my requests for a hardware replacement.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F287318798%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F287318798&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F722433177_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/38eb36a5b0f6472e84084ae2c94a3b88/href">https://medium.com/media/38eb36a5b0f6472e84084ae2c94a3b88/href</a></iframe><h3><strong>The Great Back-Peddle</strong></h3><p>With the release of macOS 10.14.4, some things changed and my MacBook of Misery returned to a pattern of catastrophic failure multiple times per day. Interestingly, it became possible with this release for me to induce a catastrophic failure around 80% of the time by waking the machine from sleep.</p><p>This time around, however, I couldn’t reproduce the issue as easily without my dock attached.</p><p><em>Upon learning this, Apple Support changed their position on literally everything and told me my dock was the problem; if I didn’t use the dock, everything worked. Nothing to do with Apple software or the Mac. The problem was solved, the Mac worked as designed and their job was done. kthxbye.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsCB9NHrzlgW-RTdp3JEmg.jpeg" /><figcaption>World-class backstroke form.</figcaption></figure><p>I felt wholly unsatisfied by the experience that led me to here, and had a hard time believing Apple’s conclusion, not least because of the nervous tone in my supporter’s voice when informing me. But I had to accept it; I had no solid evidence to the contrary. Yet.</p><p>As such I wanted to talk with Roger about the time I spent helping them debug their software, and the time and work I’d lost to the hopelessly unfinished product they had sold me. Surely some courtesy was in order.</p><p>I was feeling pretty used.</p><p>This negotiation was strenuous. Roger, always plank-like in nature, was fully incapable of understanding how anything that I’d been through was a problem, or how anything could really ever be Apple’s responsibility at all. He explicitly forbade me to use the word ‘compensation’ in our discussion; it made him very upset. Only after I threatened to take legal action, and threatened to expose Apple’s extended incompetence in handling this case to the public, did he bitterly agree to refund the machine as a gesture of goodwill.</p><p><em>Roger then aggressively reminded me that the machine was absolutely not at fault, and that my dock was the issue. This refund was in no way due to faulty Apple hardware.</em></p><p>Well…</p><h3><strong>The lady doth protest too much, methinks</strong></h3><p>Motivated by all this shady behaviour, I ordered a new, premium Thunderbolt 3 dock from another manufacturer to confirm Apple’s position. By Apple’s reasoning, a new, working dock would fix all my problems. Because the laptop itself was flawless, according to Apple.</p><p>Only this new dock didn’t fix anything. The issues were exactly the same.</p><p>So I bought a <em>third</em> dock. Again, I saw the same problems.</p><p><strong><em>So the problem wasn’t my dock, contrary to Apple Support and Roger’s claims.</em></strong> I informed Roger of this intriguing development by mail. He thanked me for my continued efforts in getting to the bottom of this.</p><p>At this point there are only 2 possible outcomes remaining in this case.</p><p>The first is that Apple’s MacBook Pros don’t work with Thunderbolt 3 devices attached. This would be really unfortunate, since Thunderbolt 3 ports are literally all they have. And it seems unlikely, since if it were the case, the internet would be going mad about it; there would be a lot of people with the same problems. As crazy as it seems, this is Apple’s position at this point — that my laptop is working as designed.</p><p>The second possibility is that the laptop they sold me was defective, as I had claimed all along.</p><p>By ordering the replacement I had been requesting since the start of all this, and swapping out the laptop, I would soon be able to find out which was true.</p><p>You’ll never guess what happens next.</p><h3><strong>Finally, a replacement</strong></h3><p>I ordered an equivalent version of the recently released 2019 MacBook Pro as a replacement. Indeed, a whole yearly product cycle had passed since I’d invested in 2018’s productivity-slaying machine; a whole year without a stable platform to work on.</p><p>Happily, this new machine runs like a wonderful dream. Nothing like the last year’s recurring, snake-filled nightmares. It’s <em>the</em> best computer I’ve ever used. I’m genuinely impressed. Maybe even a little turned-on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0X1BKNmXWGabQr2XGotGHQ.jpeg" /><figcaption>Finally, a Mac that doesn’t want to kill itself.</figcaption></figure><p>This is what I expect when I buy from Apple. A machine that works <em>really</em> well.</p><p>I informed Roger by mail of my pleasure at this development. That this machine was a massive improvement. That the pervasive, random, glitchy nonsense was gone. <em>That it worked perfectly with my setup.</em> I was truly happy to <em>finally</em> have a working machine, and the knowledge that Apple, who I’ve built a significant part of my career on, could still build good tools for me to work on.</p><p>Roger responded by calling me and, in what sounded like the onset of complete psychological breakdown, instructed me <strong>very aggressively</strong> that Apple’s position was that <em>the machine was not faulty, and that I was not provided a refund because of any fault in Apple’s hardware.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7nGahega4HP3kDm6naPfRw.jpeg" /><figcaption>“It wasn’t defective! Nothing is our fault!” — Roger, Apple Executive</figcaption></figure><p>It felt pretty bad to be approached this way in the afterglow of this overwhelmingly positive development.</p><p><em>But I suppose my finally having a working computer, after dealing with a year of random, destructive misbehaviour, is only really positive if my satisfaction is actually a priority.</em></p><p><em>If you’re Roger from Apple Executive trying to save face in this train-wreck, this is all pretty grim.</em></p><p>It’s grim because Apple’s longstanding position is now provably wrong. <em>That the new laptop works flawlessly under identical conditions is conclusive proof that the old laptop was, indeed, defective.</em> My view on the case is no longer just my opinion. It’s indisputable fact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*BZtnbpPGqzqRYYD8GE0SBA.jpeg" /></figure><p>I politely informed Roger that Apple’s position was incorrect, and that their engineers would have no choice but to agree, given this new information.</p><p>Once more, in case you missed it; <strong><em>the old laptop was, all this time, defective. A hardware swap fixed everything.</em></strong></p><h3><strong>The Situation</strong></h3><p>To surmise, I now had extensive evidence of profoundly misguided and incompetent service over a very long period, directly resulting in significant loss on my part. Not only did I have the emails, videos, diagnostics and logs documenting the shambling MacBook, but I also had the smoking gun — the laptop itself. <strong><em>A machine demonstrably defective despite 11 months of Apple’s claims to the contrary.</em></strong></p><p>Legally, this is check-mate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blRUQKjsI5hz_j-PePm3hg.jpeg" /></figure><h3><strong>Disarming The Situation</strong></h3><p>I was so relieved to have a working machine, to be able to dedicate my time to my work again. It’s hard to describe in words how important it is to me as an entrepreneur and developer to be able to trust the machines I’m working on. To trust the ecosystem I’m working in. I could finally start to do that again, after almost a year unable to find that trust; that stable foundation for everything I do.</p><p>I decided, despite what had transpired, to be decent to Roger and his team; I told him I wouldn’t be pursuing the case legally and that I was willing to return the defective laptop. I honestly thought this would allow us to more easily discuss the rather ugly situation we were in. Roger had grown gradually more agitated and tiresome to deal with as Apple’s position worsened, and I wanted to ease the tension. I know I’m easier to deal with when I don’t have a gun to my head.</p><p>In retrospect, I see my error.</p><h3><strong>apple.com/decency — Page Not Found</strong></h3><p>Expecting a decent human response was a mistake.</p><p>Roger had done nothing more than refund a defective product; a bare minimum. There was nothing minimal about the scale of my pain, my effort, nor the scale of Apple’s mishandling of the case. And I’d just saved us all a lot of time, money and embarrassment by not taking this madness to court.</p><p>I felt that courtesy was still in order for all of this. So I asked Roger for exactly that.</p><p>Roger’s (and thus Apple Executive’s) position is that the refund of my faulty machine was a grand gesture of goodwill — something Apple doesn’t otherwise do — and that the case officially closed with this noble act.</p><p>With the very real threat of being successfully sued for gross negligence and damages now off the table, Apple Executive has no further comment on the case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*24fC50_SEKSE3GdqBP_-lQ.png" /></figure><p>It’s a dick move.</p><h3><strong>Quality</strong></h3><p>I’d made peace with all of this in the time since, chalked it up to learning, and wasn’t going to write this story. But I was watching some videos from Apple’s WWDC 2019 (the annual developers conference), when I came upon a rather inspired session called “The Qualities of Great Design” (<a href="https://developer.apple.com/videos/play/wwdc2018/801/">https://developer.apple.com/videos/play/wwdc2018/801/</a>). I highly recommend watching it if you create pretty much anything.</p><p>In the video was an attempt to define ‘quality’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkfGMWw51IKNl0ZQl7FumA.png" /></figure><p>The irony is overwhelming. The combined experience (product and especially service) of owning that machine failed miserably on every one of Apple’s own parameters of quality.</p><p>The standards Apple are judged by are extra high, and I think they’d have it no other way. Expectations are even higher than usual in the case of a laptop which sits alone in it’s own super-ultra-premium price class. My experience with this laptop and it’s after-sales service in no way lived up to the promise of quality Apple made when selling it to me.</p><p>It was a beautiful-looking curse, and I’m so grateful that it’s out of my life.</p><p>It was a disappointment so intense, an experience so infuriating from beginning to end, that I feel sharing this saga of failure, succinctly measured by Apple’s own criteria for quality, somehow brings poetic closure to a truly ridiculous story.</p><p>There is a woefully unfulfilled expectation of largesse here for an item of this price and a company pushing this ‘humanist’ image. Why deny me a hardware swap if not just to try and save a buck? <strong>It would have saved all of us so much time</strong>. Even if it didn’t work out, it would have appeased me, a longstanding Apple customer, developer and evangelist, and cost very little in the incredibly grand scale of Apple’s business.</p><p><em>For comparison, the manufacturers of the 3 docks described in this story were more than willing to refund / replace their products at my request. They didn’t scream bloody murder at the notion of something possibly being wrong with their gear. They understand that mistakes happen. I respect them for that. And I didn’t even have to buy a fancy service package for this ‘luxurious’ treatment.</em></p><p>Technology companies need enthusiast users and developers, like me, to improve the quality of their product through the active feedback we provide. To attract and keep enthusiasts, their customer service needs to be high quality. Or at least not be offensively poor.</p><h3>Human Values</h3><p>It’s great that Apple has applied human-first values around their business and product. Their industry-leading stance on privacy is laudable, and their environmental efforts are significant.</p><p>They can clearly do it well if they want. They didn’t do it here.</p><p>Apple Executive’s two-bit dealings, greed-driven approach to service and “nah” attitude to responsibility are really sad. Their behaviour in this case bears no mark of quality, compassion, or any of the other human-centred thinking Apple markets itself on. It devalues the brand and the product.</p><p>I pray that I never have to deal with Apple Support (or Apple Executive) again. If you ever find yourself with a sick Mac, and value your time and sanity, exhaust all other support options before dealing with these people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=230b82a43dd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>