Latest / Martin Animations / The IT guy told me I was using the software wrong. Wait until he finds out I coded it

Transcript

The IT guy told me I was using the software wrong. Wait until he finds out I coded it · Martin Animations

0:00
Speaker 1: The IT guy told me I was using the software wrong.
0:02
Speaker 1: Wait until he finds out I coded it. He leaned
0:05
Speaker 1: over my shoulder so close I could smell his energy
0:07
Speaker 1: drink breath, and said I was doing everything wrong. His
0:10
Speaker 1: name was Derek Hoffman, and he had this condescending way
0:13
Speaker 1: of clicking his tongue whenever he saw my screen. That's
0:15
Speaker 1: not how you use the interface at all. Did you
0:17
Speaker 1: even read the manual? He reached past me to grab
0:20
Speaker 1: my mouse without asking, his hand actually shoving mine aside
0:23
Speaker 1: as he took control. I pulled my hand back and
0:25
Speaker 1: watched him navigate through the software I'd spent three years
0:27
Speaker 1: building from scratch. The software that had been acquired by
0:30
Speaker 1: Nexus Tech for $ 87 million six months ago. The software
0:34
Speaker 1: where every single line of code came from my brain,
0:36
Speaker 1: my late nights, my failed relationships because I chose debugging
0:39
Speaker 1: over dinner dates. But Derek didn't know that. Nobody at
0:42
Speaker 1: this company knew that the new junior developer they'd hired
0:45
Speaker 1: was actually David Kaplan, though I went by my middle
0:48
Speaker 1: name here, just Kai. The acquisition contract had a non-compete
0:51
Speaker 1: clause that kept me out of the industry for a year,
0:54
Speaker 1: but it said nothing about getting a regular job at
0:55
Speaker 1: the company that bought my creation. So here I was,
0:58
Speaker 1: sitting in a gray cubicle, watching Derek explain my own
1:01
Speaker 1: software to me, like I was a child who'd never
1:03
Speaker 1: seen a computer before. Derek's fingers flew across my keyboard,
1:06
Speaker 1: typing commands that were technically correct, but inefficient as hell. See,
1:10
Speaker 1: you're trying to access the backend through the main dashboard,
1:13
Speaker 1: but that's not what it's designed for. The architecture doesn't
1:16
Speaker 1: support that kind of query. He was so confident, so
1:19
Speaker 1: absolutely certain that I was the idiot in this scenario.
1:22
Speaker 1: What he didn't know was that I'd specifically designed the
1:24
Speaker 1: architecture to support exactly that kind of query. because I'd
1:27
Speaker 1: anticipated users would need that flexibility. The main dashboard access
1:31
Speaker 1: was actually the fastest route to the backend, but Derek
1:33
Speaker 1: had apparently never read the actual documentation, just the simplified
1:37
Speaker 1: user guide that the marketing team had written. I bit
1:39
Speaker 1: my tongue and nodded along while he continued his lecture,
1:42
Speaker 1: explaining how real developers approached these problems. The urge to
1:46
Speaker 1: correct him was physical, like an itch I couldn't scratch,
1:49
Speaker 1: but I'd learned over the past two months that staying
1:51
Speaker 1: quiet revealed far more than speaking up ever could. Derek
1:53
Speaker 1: had been the senior IT administrator at Nexus for five years,
1:57
Speaker 1: and according to office gossip, he'd positioned himself as the
2:00
Speaker 1: resident expert on my software the moment the acquisition went through.
2:03
Speaker 1: He'd apparently spent one weekend reading through some of the
2:05
Speaker 1: public documentation and decided that made him qualified to train
2:09
Speaker 1: everyone else. My team lead, Patricia Lim, walked by and
2:12
Speaker 1: paused at my cubicle. Derek, are you helping Kai with
2:15
Speaker 1: the integration issues? She had this hopeful tone, like maybe
2:18
Speaker 1: Derek's involvement would actually solve something instead of making it worse.
2:21
Speaker 1: Derek straightened up, puffing his chest out slightly. Yeah, I'm
2:25
Speaker 1: showing him the proper way to navigate the system. Lot
2:27
Speaker 1: of people make these same mistakes when they're new to
2:29
Speaker 1: enterprise software. He said, enterprise software, like he was saying,
2:33
Speaker 1: rocket science, with this weight that suggested mere mortals couldn't
2:36
Speaker 1: possibly understand. Patricia nodded and moved on, and I caught
2:39
Speaker 1: her shooting me a look that suggested she'd been on
2:41
Speaker 1: the receiving end of Derek's expertise before. After she left,
2:45
Speaker 1: Derek continued his tutorial, now pulling up his own screen
2:48
Speaker 1: to show me examples. See, I've actually been working on
2:50
Speaker 1: optimizing the core functions. The original developer clearly didn't understand scalability.
2:55
Speaker 1: He pulled up a code file, and I felt my
2:57
Speaker 1: eye twitch. Those were my functions. The ones I'd spent
2:59
Speaker 1: six months optimizing, the ones that had been specifically praised
3:03
Speaker 1: in the tech press for their elegant scalability solutions. Derek
3:06
Speaker 1: had added about 200 lines of completely unnecessary code that
3:09
Speaker 1: actually slowed everything down by creating redundant processes. I couldn't
3:13
Speaker 1: help myself. What does this section do? I pointed at
3:16
Speaker 1: his additions, keeping my voice curious and innocent. Derek launched
3:19
Speaker 1: into an explanation that was technically gibberish, throwing around terms
3:23
Speaker 1: that sounded impressive but meant nothing in this context.
3:25
Speaker 2: He was like a.
3:26
Speaker 1: Student who'd memorized big words without understanding what they meant,
3:29
Speaker 1: stringing them together in ways that sounded plausible to non-programmers,
3:33
Speaker 1: but made no actual sense. So you're basically creating a
3:36
Speaker 1: buffer cache for the redundant overflow? I asked, using terms
3:39
Speaker 1: that also meant nothing but sounded equally impressive. Derek nodded enthusiastically.
3:44
Speaker 2: Exactly.
3:45
Speaker 1: I'm glad someone here is actually trying to learn instead
3:47
Speaker 1: of just clicking around randomly. He saved his changes and
3:50
Speaker 1: closed the file, completely missing how his optimization and had
3:53
Speaker 1: just introduced three separate memory leaks that would crash the
3:56
Speaker 1: system under any significant load. I made a mental note
3:58
Speaker 1: to document this. The legal team had advised me to
4:01
Speaker 1: keep detailed records of everything happening with my software at Nexus,
4:04
Speaker 1: though they'd been vague about why. Something about potential future
4:07
Speaker 1: litigation and breach of contract claims. But they'd told me
4:10
Speaker 1: to just observe and document for now. That afternoon, I
4:13
Speaker 1: sat in the break room eating lunch while Derek held
4:15
Speaker 1: court with some of the other IT staff. The problem
4:18
Speaker 1: with the original coder, he was saying, loud enough for
4:20
Speaker 1: half the room to hear, is that they clearly prioritized
4:23
Speaker 1: flashy features over solid architecture. I've been having to basically
4:26
Speaker 1: rebuild the foundation while keeping everything running. The other IT
4:29
Speaker 1: guys nodded along, and I recognized the dynamic immediately. Derek
4:33
Speaker 1: was the alpha of this particular pack, and agreeing with
4:35
Speaker 1: him was easier than challenging him. One of the younger guys,
4:38
Speaker 1: Nathan Patel, looked uncertain. But didn't the software win some
4:41
Speaker 1: awards for its architecture? I read that it revolutionized backend
4:44
Speaker 1: processing or something. Derek waved this away dismissively. Marketing hype.
4:48
Speaker 1: Awards don't mean the code is actually good. just that
4:51
Speaker 1: the company had a good PR team. I've seen the
4:53
Speaker 1: actual code, and trust me, it's amateur hour. Lot of
4:56
Speaker 1: shortcuts and band-aid solutions. Whoever wrote this probably learned to code.
4:59
Speaker 2: From YouTube tutorials.
5:01
Speaker 1: The room laughed, and I took another bite of my sandwich,
5:04
Speaker 1: chewing slowly while watching Derek bask in the attention. He
5:07
Speaker 1: had no idea that the amateur he was mocking had
5:09
Speaker 1: a PhD in computer science from MIT and had been
5:12
Speaker 1: coding since he was 12. The problem started appearing three
5:15
Speaker 1: days later. The system began experiencing intermittent crashes, always during
5:19
Speaker 1: peak usage hours. Users were getting logged out randomly, data
5:23
Speaker 1: queries were timing out, and the customer support team was
5:25
Speaker 1: drowning in complaints. I watched from my cubicle as Derek
5:28
Speaker 1: rushed around trying to diagnose the issue, his confidence from
5:31
Speaker 1: earlier in the week, notably absent. Patricia called an emergency meeting,
5:35
Speaker 1: and everyone from IT crowded into the conference room. Derek
5:38
Speaker 1: pulled up his diagnostic reports on the projector, walking everyone
5:40
Speaker 1: through his analysis. It's clearly a problem with the original
5:43
Speaker 1: code architecture. The system can't handle our user load. We're
5:47
Speaker 1: going to need to bring in an external consultant to
5:48
Speaker 1: do a complete overhaul. He clicked through slides showing error
5:51
Speaker 1: logs and crash reports, and I could see exactly what
5:54
Speaker 1: was wrong. Every single error traced back to the optimizations
5:57
Speaker 1: Derek had implemented. His redundant processes were eating up memory
6:00
Speaker 1: until the system choked, and his buffer cache was creating
6:03
Speaker 1: data conflicts that corrupted active sessions. But he'd designed his
6:06
Speaker 1: diagnostic report to make it look like fundamental flaws in
6:09
Speaker 1: the base code, carefully omitting any mention of his recent changes.
6:12
Speaker 1: Patricia looked stressed, rubbing her temples. An overhaul could take
6:15
Speaker 1: months and cost millions. Is there any short-term solution? Derek
6:18
Speaker 1: shook his head gravely. Not without risking data integrity. The
6:22
Speaker 1: best we can do is roll back to the pre-acquisition version,
6:25
Speaker 1: but then we lose all the features we've been building on.
6:27
Speaker 1: This was fascinating to watch, like seeing a train wreck
6:30
Speaker 1: in slow motion. Derek had created the problem, couldn't see
6:33
Speaker 1: that he'd created the problem, and was now proposing solutions
6:36
Speaker 1: that would make the problem worse. I raised my hand slightly,
6:39
Speaker 1: and Patricia nodded at me.
6:40
Speaker 2: I might have an idea.
6:42
Speaker 1: Every head in the room turned toward me, and I
6:44
Speaker 1: could see Derek's expression shift from stressed to annoyed. The
6:47
Speaker 1: error logs show memory overflow starting around Thursday at 3pm.
6:50
Speaker 1: What changes were implemented around that time? It was a
6:52
Speaker 1: simple question, but I already knew the answer. Derek's face
6:55
Speaker 1: colored slightly. I implemented some performance enhancements, but those were
6:59
Speaker 1: thoroughly tested. I nodded slowly, pulling out my laptop. Would
7:03
Speaker 1: you mind if I looked at the change logs? Just
7:05
Speaker 1: to rule out any conflicts with the base code. Derek
7:07
Speaker 1: looked like he wanted to refuse, but with Patricia watching,
7:10
Speaker 1: he couldn't without looking defensive. Fine, but you're not going
7:13
Speaker 1: to find anything. Those enhancements are industry standard practices. I
7:17
Speaker 1: pulled up the repository and started walking through Derek's changes
7:20
Speaker 1: line by line. Within five minutes, I'd identified four critical
7:23
Speaker 1: errors that any decent code review should have caught. Within
7:26
Speaker 1: ten minutes, I'd mapped out exactly how those errors cascaded
7:29
Speaker 1: into the crashes everyone was experiencing. I explained it as
7:32
Speaker 1: simply as I could, using terms that non-programmers could follow,
7:35
Speaker 1: showing how Derek's buffer cache was actually creating duplicate data
7:39
Speaker 1: entries that conflicted with the original processing queue. Patricia leaned forward,
7:43
Speaker 1: suddenly very focused. Can you fix it?
7:45
Speaker 2: I nodded.
7:46
Speaker 1: I can write a patch in about two hours, roll
7:48
Speaker 1: back Derek's changes, implement a proper caching system that doesn't
7:51
Speaker 1: conflict with the existing architecture, and add some error handling
7:54
Speaker 1: to prevent this from happening again. The room was quiet,
7:57
Speaker 1: and Derek's face had gone from annoyed to pale. He
7:59
Speaker 1: tried to salvage the situation. That's a pretty bold claim
8:02
Speaker 1: from someone who's been here two months. No offense, Kai,
8:04
Speaker 1: but this system is complex.
8:06
Speaker 2: I met his eyes.
8:07
Speaker 1: The system is actually pretty elegant once you understand the
8:09
Speaker 1: underlying logic. The original developer built in a lot of flexibility,
8:13
Speaker 1: but you have to work with the architecture.
8:14
Speaker 2: Not against it.
8:15
Speaker 1: I turned back to Patricia. I can have it done
8:17
Speaker 1: by end of day if you want. Patricia made a decision.
8:20
Speaker 2: Do it.
8:21
Speaker 1: Derek, work with Kai on this. I want both of
8:23
Speaker 1: you checking each other's code before anything goes live. Derek
8:26
Speaker 1: looked like he'd been asked to eat glass, but he nodded.
8:29
Speaker 1: Back at my cubicle, Derek pulled up a chair and
8:31
Speaker 1: watched my screen as I started coding. I didn't need
8:33
Speaker 1: two hours. I needed about forty minutes. But I'd learned
8:36
Speaker 1: that underestimating time made people trust you more than overestimating.
8:40
Speaker 2: I wrote the patch.
8:41
Speaker 1: Fixing Derek's mistakes while making it look like I was
8:43
Speaker 1: just adapting his approach. I added comments explaining what each
8:46
Speaker 1: section did, writing them at a level that Derek could understand,
8:49
Speaker 1: but that would also make it obvious to any actual
8:51
Speaker 1: programmer that I knew exactly what I was doing. Derek
8:54
Speaker 1: watched in silence, and I could feel his confusion growing.
8:57
Speaker 1: Every few minutes he'd ask a question, and I'd answer
8:59
Speaker 1: it simply, watching him realize that I understood the system
9:02
Speaker 1: better than he did. The patch worked perfectly. I deployed
9:05
Speaker 1: it at 4.30pm, and within minutes, the error rates dropped
9:08
Speaker 1: to zero. System performance actually improved beyond baseline, because I'd
9:12
Speaker 1: taken the opportunity to optimize a few other bottlenecks I'd noticed.
9:15
Speaker 1: Patricia stopped by my cubicle at FiveWare with a smile.
9:18
Speaker 1: I don't know where you learn to code like that,
9:20
Speaker 1: but nice work, Kai. Derek had already left for the
9:22
Speaker 1: day without saying anything. That night, I got a message
9:25
Speaker 1: from my lawyer, Gregory Whitfield. The subject line just said,
9:28
Speaker 1: Interesting Development, and the body contained a link to an
9:30
Speaker 1: internal Nexus memo. Apparently, Derek had been sending emails to
9:34
Speaker 1: upper management claiming credit for major improvements to his software.
9:38
Speaker 1: specifically mentioning features and optimizations that I had built into
9:41
Speaker 1: the original code years ago. The memo was Derek's pitch
9:44
Speaker 1: for a promotion to chief technology officer, based entirely on
9:47
Speaker 1: his supposed expertise with the system. Gregory's message continued, this
9:51
Speaker 1: could be useful for the secondary claim. He's essentially committing
9:54
Speaker 1: fraud by claiming credit for your work. Document everything. I
9:57
Speaker 1: sat back in my chair, looking at my apartment that
10:00
Speaker 1: was significantly smaller than the house I'd been able to
10:02
Speaker 1: afford before selling my company. The acquisition had made me
10:05
Speaker 1: wealthy on paper, but the non-compete clause meant I couldn't
10:08
Speaker 1: work on anything similar, couldn't start a new company, couldn't
10:10
Speaker 1: even consult in my own field. Taking this junior developer
10:13
Speaker 1: job had been partly about staying sane, having something to
10:16
Speaker 1: do with my days, but also about seeing what Nexus
10:18
Speaker 1: was actually doing with my creation. The next morning, I
10:21
Speaker 1: arrived to find Derek already at my cubicle looking uncomfortable.
10:24
Speaker 1: We need to talk about yesterday. He shifted his weight
10:27
Speaker 1: from foot to foot. I think maybe we got off
10:29
Speaker 1: on the wrong foot. You clearly know your stuff. This
10:31
Speaker 1: was as close to an apology as Derek was capable of,
10:34
Speaker 1: and I could see the calculation behind it. He'd realized
10:36
Speaker 1: I was a threat to his self-proclaimed expertise. I nodded,
10:39
Speaker 1: keeping my expression neutral. I'm just trying to help the
10:42
Speaker 1: team succeed. Derek relaxed slightly.
10:44
Speaker 2: Right, exactly.
10:45
Speaker 1: So, I was thinking- Maybe you could help me with
10:47
Speaker 1: some of the more technical documentation. You seem to have
10:50
Speaker 1: a good grasp of the underlying architecture.
10:52
Speaker 2: Translation.
10:53
Speaker 1: He wanted me to do his work for him while
10:54
Speaker 1: he continued to take credit. I agreed, because watching Derek
10:58
Speaker 1: operate was providing invaluable documentation for whatever legal strategy Gregory
11:01
Speaker 1: was building. Over the next two weeks, Derek sent me
11:04
Speaker 1: increasingly complex problems, things he should have been able to
11:07
Speaker 1: solve himself if he actually understood the system. I solved
11:10
Speaker 1: each one, always explaining my solutions in ways that made
11:13
Speaker 1: it clear I understood not just the fix, but the
11:16
Speaker 1: fundamental design philosophy behind the code. Other people started noticing. Nathan,
11:20
Speaker 1: the younger IT guy, started coming to me with questions
11:23
Speaker 1: instead of Derek. Patricia assigned me to more critical projects.
11:26
Speaker 1: The customer support team started specifically requesting my help when
11:29
Speaker 1: issues came up. Derek's response was to double down on
11:32
Speaker 1: his expertise claims. He started a blog about optimizing legacy code,
11:36
Speaker 1: writing posts that were thinly veiled criticisms of my original architecture.
11:40
Speaker 1: He spoke at a local tech meetup about rescuing failed
11:43
Speaker 1: software projects. using examples that were clearly based on his
11:46
Speaker 1: work with my system. Each blog post, each presentation, each
11:49
Speaker 1: claim was screenshot and documented. Gregory sent me a message.
11:53
Speaker 1: He's building our case for us.
11:54
Speaker 2: Keep going.
11:55
Speaker 1: But the situation at work was getting tense. Derek had
11:58
Speaker 1: started making comments about my attitude problem and how I
12:01
Speaker 1: didn't respect the chain of command. He complained to Patricia
12:03
Speaker 1: that I was undermining his authority by going around him
12:06
Speaker 1: to solve problems. Patricia called me into her office on
12:08
Speaker 1: a Friday afternoon.
12:09
Speaker 2: She looked tired.
12:10
Speaker 1: Kai, you're doing great work. But Derek says you're not
12:13
Speaker 1: following proper protocols. He's your senior, and he needs to
12:16
Speaker 1: be kept in the loop on all technical decisions. I
12:18
Speaker 1: chose my words carefully. I'm happy to follow protocols. Can
12:22
Speaker 1: you clarify what those are? Derek hasn't really outlined a
12:24
Speaker 1: clear process for escalation or approval. Patricia hesitated. Just keep
12:29
Speaker 1: him informed, okay? Derek's been here a long time and
12:31
Speaker 1: he knows the company culture. That weekend, I did something
12:34
Speaker 1: I'd been avoiding. I actually read through the acquisition contract
12:37
Speaker 1: in detail, all 237 pages. Most of it was standard
12:41
Speaker 1: legal language. but buried in section 12, subsection 4, I
12:45
Speaker 1: found something interesting. Nexus had the right to hire me
12:47
Speaker 1: as a consultant during the non-compete period to address technical
12:50
Speaker 1: issues with the software, and they had to pay my
12:52
Speaker 1: original consulting rate, which was $ 500 per hour. I'd never
12:56
Speaker 1: thought about it because I hadn't planned to work here,
12:58
Speaker 1: but now that I was already on staff as a
13:00
Speaker 1: regular employee making $ 75, 000 a year, the implications were fascinating.
13:04
Speaker 1: On Monday, I scheduled a meeting with Patricia and HR.
13:08
Speaker 1: I need to clarify my employment status. I pulled out
13:10
Speaker 1: the relevant contract section. According to the acquisition agreement, if
13:13
Speaker 1: I work on the core software in any capacity, it
13:15
Speaker 1: needs to be under my consulting contract, not as a
13:18
Speaker 1: regular employee. The HR director, Linda Vasquez, read the section
13:21
Speaker 1: three times, her expression growing more concerned with each reading.
13:25
Speaker 1: She excused herself to call legal. Thirty minutes later, I
13:27
Speaker 1: was sitting in a conference room with Patricia, Linda, the
13:30
Speaker 1: company's general counsel, and the CFO. The general counsel, Michael Brennan,
13:34
Speaker 1: had the contract spread out in front of him. How
13:36
Speaker 1: long have you been working on the core software? I
13:39
Speaker 1: pulled out my documentation. Since my second day. Derek has
13:42
Speaker 1: been assigning me to fix critical issues with the system.
13:44
Speaker 1: I have logs of every project, every fix, every consultation.
13:48
Speaker 1: I slid the folder across the table. That's approximately 320
13:51
Speaker 1: hours of work over two months. Michael did the math
13:54
Speaker 1: in his head, and I watched his face go pale.
13:56
Speaker 1: 320 hours at $ 500 per hour was $ 160, 000, plus the $ 12, 500
14:02
Speaker 1: I'd already been paid in salary. The CFO, James Thornton,
14:05
Speaker 1: was already typing on his calculator. This can't be right.
14:08
Speaker 1: Why didn't Derek flag this? Patricia looked confused. Derek said
14:11
Speaker 1: Kai was just a junior developer. He's been assigning him
14:14
Speaker 1: to software maintenance. Michael flipped through my documentation.
14:17
Speaker 2: This isn't maintenance. This is core architectural work. System optimization.
14:21
Speaker 2: Emergency crisis management. This is exactly what the consulting clause covers.
14:25
Speaker 2: He looked at me.
14:26
Speaker 1: Why didn't you say something sooner? I met his gaze calmly.
14:29
Speaker 1: I assumed HR had processed my employment correctly. I only
14:32
Speaker 1: reviewed the acquisition contract this weekend when I was trying
14:34
Speaker 1: to understand the proper reporting protocols Derek mentioned. The meeting
14:38
Speaker 1: ended with promises to sort this out. and requests that
14:40
Speaker 1: I not discuss this with anyone while they investigated. That afternoon,
14:44
Speaker 1: Derek stopped by my cubicle looking smug. Heard you had
14:47
Speaker 1: a meeting with the executives. Hope you didn't try to
14:49
Speaker 1: cause trouble. Companies don't like employees who rock the boat.
14:52
Speaker 1: I smiled politely. Just clarifying some paperwork issues. Nothing major.
14:56
Speaker 1: But it was major. And over the next week, I
14:59
Speaker 1: watched the fallout spread through the company like a virus.
15:02
Speaker 1: HR launched an audit of all the work I'd been doing.
15:04
Speaker 1: They discovered that Derek had been systematically assigning me to
15:07
Speaker 1: high-level projects, while documenting them as routine junior developer tasks.
15:11
Speaker 1: Every fix I'd implemented, every system improvement, every crisis I'd
15:15
Speaker 1: resolved was work that should have been billed under my
15:17
Speaker 1: consulting contract. The financial implications were bad enough, but then
15:21
Speaker 1: they found Derek's blog and his speaking engagements. The legal
15:24
Speaker 1: team was very interested in his public claims of rescuing
15:26
Speaker 1: and rebuilding software that he neither created nor apparently understood.
15:30
Speaker 1: Michael called me back in on Thursday. We need to
15:32
Speaker 1: discuss a settlement. He looked like he hadn't slept well.
15:35
Speaker 1: Your consulting contract entitles you to payment for all substantive
15:38
Speaker 1: work on the core software. Our audit shows approximately 600
15:42
Speaker 1: hours of qualifying work. 600 hours at $ 500 per hour
15:45
Speaker 1: was $ 300, 000. James the CFO was in the meeting again,
15:49
Speaker 1: looking like he was in pain. We'd like to negotiate
15:52
Speaker 1: a flat fee rather than hourly billing, and we need
15:54
Speaker 1: to discuss your ongoing role at the company. I waited,
15:57
Speaker 1: letting them make the first offer. Michael continued. We'll pay
16:00
Speaker 1: you $ 250, 000 for all work completed to date. plus retain
16:03
Speaker 1: you as a consultant going forward at your contract rate
16:05
Speaker 1: for any future core software work. You'd move out of
16:08
Speaker 1: Derek's department entirely and report directly to Patricia.
16:11
Speaker 2: It was a good offer, but I wasn't done.
16:13
Speaker 1: I want Derek removed from any supervisory role over the
16:15
Speaker 1: core software. His modifications have introduced critical vulnerabilities, and his
16:19
Speaker 1: lack of understanding poses a security risk.
16:22
Speaker 2: I pulled out another folder.
16:23
Speaker 1: These are the six instances where his changes directly caused
16:26
Speaker 1: system failures. These are the optimization claims he's made publicly
16:29
Speaker 1: that are factually incorrect. and these are the emails where
16:32
Speaker 1: he claimed credit for features that were built into the
16:34
Speaker 1: original architecture. Michael and James exchanged glances. Michael spoke carefully.
16:39
Speaker 1: What exactly are you proposing? I laid it out simply.
16:41
Speaker 1: Derek moves to a different department with no access to
16:44
Speaker 1: my software. I get full architectural authority as primary consultant.
16:47
Speaker 1: Any public communications about the software's development go through me
16:51
Speaker 1: for technical accuracy. The settlement was finalized three weeks later.
16:55
Speaker 1: I got my $ 250, 000 in back pay, a consulting contract
16:58
Speaker 1: that kicked in whenever I touched the core software, and
17:01
Speaker 1: a clause that gave me veto power over any public
17:03
Speaker 1: statements about the technical aspects of the system. Derek was
17:06
Speaker 1: reassigned to managing the company's internal IT infrastructure, away from
17:10
Speaker 1: anything touching my code. He cleaned out his desk on
17:12
Speaker 1: a Friday afternoon while I was in a meeting, leaving
17:14
Speaker 1: without saying goodbye to anyone. Patricia told me later that
17:17
Speaker 1: he'd been furious, claiming I'd sabotaged him, but the documentation
17:21
Speaker 1: of his errors and false claims made any formal complaint impossible.
17:24
Speaker 1: The blog came down within days, and his speaking engagement
17:27
Speaker 1: at the upcoming tech conference was quietly cancelled. Nathan took
17:30
Speaker 1: over as the primary IT liaison for my software, and
17:33
Speaker 1: the difference was immediate. He actually read documentation, asked intelligent questions,
17:37
Speaker 1: and didn't try to fix things that weren't broken. But
17:40
Speaker 1: the real satisfaction came three months later when I got
17:42
Speaker 1: a call from Derek's new employer, a startup called VectorSync,
17:45
Speaker 1: that wanted to license some technology. They'd called me because
17:48
Speaker 1: my name was on the patents. We hired Derek Hoffman
17:51
Speaker 1: as our CTO based on his expertise with your software,
17:54
Speaker 1: the startup's CEO, Amanda Foster, said. He's been advising us
17:57
Speaker 1: on building a competing system and we wanted to make
17:59
Speaker 1: sure we weren't infringing on any of your IP. I
18:02
Speaker 1: asked a few careful questions and learned that Derek had
18:05
Speaker 1: grossly misrepresented his role in my software's development, claiming he'd
18:08
Speaker 1: been the lead architect who'd saved the project. The startup
18:11
Speaker 1: had offered him a significant equity stake based on these claims.
18:14
Speaker 1: I sent Amanda a detailed timeline of Derek's actual role,
18:17
Speaker 1: along with documentation of his technical errors and the settlement
18:20
Speaker 1: agreement that specifically outlined what work he'd actually done versus
18:23
Speaker 1: what he'd claimed credit for. Amanda called back two days later.
18:27
Speaker 1: We're terminating Derek's employment. Thank you for being honest with us.
18:30
Speaker 1: I never found out exactly what happened after that, but
18:32
Speaker 1: Derek's LinkedIn profile went quiet, and the few mutual connections
18:35
Speaker 1: we had mentioned he'd left the tech industry entirely. Maybe
18:38
Speaker 1: he found somewhere else to be a big fish in
18:40
Speaker 1: a small pond, somewhere his technical limitations wouldn't be exposed
18:44
Speaker 1: so dramatically. Or maybe he finally learned that claiming expertise
18:47
Speaker 1: you don't have only works until you meet someone who
18:49
Speaker 1: actually knows what they're talking about. The experience changed how
18:52
Speaker 1: I thought about my work and my role in the
18:54
Speaker 1: tech industry. I started consulting for other companies who'd acquired
18:57
Speaker 1: software from small developers, helping them understand what they'd actually
19:00
Speaker 1: bought and how to work with it properly. I wrote
19:03
Speaker 1: articles about the importance of understanding your own systems rather
19:06
Speaker 1: than relying on self-proclaimed experts. I spoke at conferences about
19:09
Speaker 1: the gap between real technical knowledge and performance of technical
19:12
Speaker 1: knowledge and how companies could protect themselves from the derricks
19:15
Speaker 1: of the world. Patricia eventually offered me a permanent position
19:19
Speaker 1: as chief technology architect, but I declined. The consulting arrangement
19:22
Speaker 1: gave me freedom and flexibility that a staff role never could. Plus,
19:26
Speaker 1: the non-compete clause had expired, and I was starting to
19:29
Speaker 1: think about my next project. But I kept the Nexus contract,
19:32
Speaker 1: coming in a few days a month to maintain the
19:33
Speaker 1: software and train new developers. On one of those days,
19:36
Speaker 1: I was working in my old cubicle, when a new
19:38
Speaker 1: junior developer stopped by. Excuse me, I'm having trouble with
19:41
Speaker 1: the backend interface. The IT team said I should ask you.
19:44
Speaker 1: I looked at her screen and smiled. What specific issue
19:47
Speaker 1: are you having? She pointed at her code. I'm trying
19:49
Speaker 1: to access the database directly, but the documentation says I
19:52
Speaker 1: should go through the main dashboard. That seems inefficient. I
19:55
Speaker 1: pulled up a chair. Actually, the main dashboard route is faster.
19:58
Speaker 1: Let me show you why the architecture was designed that way.
20:01
Speaker 1: As I walked her through the logic, explaining the reasoning
20:03
Speaker 1: behind design decisions that most people took for granted, I
20:06
Speaker 1: realized this was exactly why I'd taken that junior developer
20:09
Speaker 1: job in the first place. Not for the money or
20:11
Speaker 1: the satisfaction of proving Derek wrong, though both were nice,
20:15
Speaker 1: but because I needed to understand how people actually used
20:17
Speaker 1: my creation, how they thought about it, where they struggled,
20:20
Speaker 1: where the documentation failed them. Derek had been so focused
20:23
Speaker 1: on being the expert that he'd never actually learned to
20:26
Speaker 1: use the tools at his disposal. He'd built his entire
20:29
Speaker 1: persona around knowing more than everyone else, and when confronted
20:32
Speaker 1: with actual expertise, he'd had nothing to fall back on.
20:35
Speaker 1: I spent an hour with the new developer, answering questions
20:37
Speaker 1: and explaining concepts, and she left with a genuine understanding
20:40
Speaker 1: of the system, rather than just a rote solution to
20:42
Speaker 1: her immediate problem. That, more than anything else, felt like winning.
20:46
Speaker 1: Not the settlement money, not Derek's humiliation, but the ability
20:49
Speaker 1: to help someone learn something real. Later that evening, I
20:52
Speaker 1: got an email from Gregory with a subject line that
20:54
Speaker 1: just said, FYI. The body contained a link to a
20:57
Speaker 1: lawsuit filing. Derek was suing Nexus for wrongful termination, claiming
21:01
Speaker 1: he'd been scapegoated for problems with the software. and that
21:04
Speaker 1: his reassignment was retaliation for whistleblowing about technical issues. I
21:08
Speaker 1: called Gregory immediately. Is this going to be a problem?
21:11
Speaker 2: He laughed. For him? Yes. For you?
21:14
Speaker 1: No. We have documentation of every false claim, every technical error,
21:18
Speaker 1: every piece of credit he tried to steal. If this
21:20
Speaker 1: goes to trial, it'll destroy whatever's left of his professional reputation.
21:24
Speaker 1: The suit was quietly dismissed six months later, after Derek
21:27
Speaker 1: apparently saw the evidence Nexus was prepared to present. But
21:30
Speaker 1: the experience left me thinking about how many other Dereks
21:32
Speaker 1: were out there. confidently explaining things they didn't understand, building
21:35
Speaker 1: careers on claimed expertise they didn't possess, and how many
21:38
Speaker 1: people suffered under that false authority. I started a blog
21:41
Speaker 1: of my own, anonymously at first, writing about technical myths,
21:45
Speaker 1: common misconceptions, and how to spot the difference between real
21:48
Speaker 1: knowledge and performed knowledge. It gained a following in the
21:51
Speaker 1: tech community, people sharing stories of their own encounters with
21:54
Speaker 1: false experts and the damage they'd caused. One reader reached
21:57
Speaker 1: out with a story about an IT manager who'd convinced
21:59
Speaker 1: his company to do a complete system overhaul that wasn't needed,
22:02
Speaker 1: costing millions and months of productivity, all because he needed
22:05
Speaker 1: to justify his position. Another wrote about a CTO who
22:08
Speaker 1: blocked every improvement suggestion because he couldn't understand the proposals
22:11
Speaker 1: and felt threatened by developers who knew more than him.
22:14
Speaker 1: The stories piled up, a catalog of technical incompetence masquerading
22:17
Speaker 1: as expertise, and I realized Derek wasn't an anomaly. He
22:20
Speaker 1: was a symptom of a larger problem in tech culture
22:22
Speaker 1: where confidence was valued over competence, where the ability to
22:25
Speaker 1: sound smart mattered more than actually being smart, and where
22:28
Speaker 1: questioning the supposed experts was seen as insubordination. rather than
22:32
Speaker 1: due diligence. I started doing workshops about technical leadership, how
22:36
Speaker 1: to evaluate claimed expertise, how to create environments where knowledge
22:39
Speaker 1: could flow freely without being bottlenecked by fragile egos. Companies
22:43
Speaker 1: brought me in to audit their technical teams and identify
22:45
Speaker 1: where communication was breaking down. More often than not, I'd
22:49
Speaker 1: find a Derek somewhere in the chain, someone who'd positioned
22:51
Speaker 1: themselves as indispensable by making systems seem more complicated than
22:54
Speaker 1: they were. Three years after that first day when Derek
22:57
Speaker 1: grabbed my mouse and told me I was doing everything wrong,
23:00
Speaker 1: I sat in a keynote speaker chair at a major
23:01
Speaker 1: tech conference. The moderator asked me about the experience that
23:04
Speaker 1: had launched my consulting career, and I told a version
23:07
Speaker 1: of the story, names changed, details obscured, but the core
23:11
Speaker 1: truth intact. I learned that sometimes the best way to
23:13
Speaker 1: understand a system is to watch how people misunderstand it,
23:16
Speaker 1: I said. And I learned that real expertise isn't about
23:19
Speaker 1: knowing everything. It's about knowing what you don't know and
23:22
Speaker 1: being willing to learn from anyone, regardless of their job
23:24
Speaker 1: title or time at the company. The audience laughed when
23:27
Speaker 1: I described Derek's face. realizing I'd fixed in two hours
23:30
Speaker 1: what he'd claimed would take months. They nodded knowingly when
23:32
Speaker 1: I talked about the patterns of false expertise I'd identified.
23:35
Speaker 1: And afterward, dozens of people came up to share their
23:38
Speaker 1: own Derek stories. Their own experiences of being underestimated, of
23:42
Speaker 1: watching incompetent people fail upward while actual experts were ignored.
23:46
Speaker 1: That conference talk led to more speaking engagements, more consulting contracts,
23:50
Speaker 1: more opportunities to help companies identify and fix the Derek
23:53
Speaker 1: problem in their organizations. But the most satisfying moment came
23:56
Speaker 1: four years after the settlement, when I got an email
23:58
Speaker 1: from Nathan, the young IT guy who'd taken over when
24:00
Speaker 1: Derek left. Hey Kai, wanted to let you know I
24:03
Speaker 1: just got promoted to senior developer. I've been using the
24:05
Speaker 1: principles you taught me about really understanding systems before trying
24:08
Speaker 1: to modify them, and it's completely changed how I approach problems.
24:11
Speaker 1: Thank you for taking the time to actually teach, instead
24:14
Speaker 1: of just showing off. You saved my career before I
24:16
Speaker 1: even realized it needed saving. That message meant more than
24:19
Speaker 1: any settlement check or successful lawsuit. Derek had treated people's
24:22
Speaker 1: ignorance as a resource to exploit for his own advancement.
24:25
Speaker 1: I tried to treat it as a gap to fill.
24:27
Speaker 1: a chance to help someone understand something real. And in
24:29
Speaker 1: the end, that difference in approach made all the difference.
24:32
Speaker 1: Derek was somewhere out of tech, his reputation destroyed by
24:35
Speaker 1: his own false claims. I was building a career helping
24:38
Speaker 1: companies avoid hiring their own Dereks, teaching real experts how
24:41
Speaker 1: to share knowledge effectively, and creating systems where competence mattered
24:44
Speaker 1: more than confidence. The software I'd built was still running,
24:47
Speaker 1: better than ever, maintained by people who actually understood it,
24:50
Speaker 1: rather than people who just claimed to. Sometimes I still
24:53
Speaker 1: think about that first day, Derek's hand grabbing my mouse.
24:56
Speaker 2: His absolute certainty that he knew better.
24:58
Speaker 1: I think about how close I came to just correcting
25:01
Speaker 1: him immediately, pulling rank, announcing who I really was, but
25:04
Speaker 1: staying quiet, watching, learning, documenting, that had taught me things
25:08
Speaker 1: that immediate confrontation never could have. I learned how people
25:11
Speaker 1: like Derek operated, the specific techniques they used to maintain
25:14
Speaker 1: false expertise, the warning signs that someone's confidence exceeded their competence.
25:19
Speaker 1: And I learned that sometimes the best revenge isn't dramatic
25:21
Speaker 1: confrontation or public humiliation. Sometimes it's just quietly being excellent
25:26
Speaker 1: at what you do until the truth becomes impossible to ignore,
25:29
Speaker 1: until the false expert's house of cards collapses under the
25:31
Speaker 1: weight of their own claims. Derek had told me I
25:34
Speaker 1: was using the software wrong. He'd been so sure, so confident,
25:37
Speaker 1: so completely wrong. And in his wrongness, in his arrogant
25:41
Speaker 1: insistence that he knew better, he'd given me everything I
25:43
Speaker 1: needed to not just prove him wrong but to build
25:45
Speaker 1: something better from the wreckage of his ego. That's the
25:48
Speaker 1: thing about false expertise. It's sustainable only in the absence
25:51
Speaker 1: of real knowledge. The moment someone who actually knows what
25:54
Speaker 1: they're talking about shows up, the whole performance falls apart.
25:57
Speaker 1: If you're still here, you're a true fan. Show some
25:59
Speaker 1: support with a like and subscribe to catch the next one.