शैडोइंग अभ्यास: 25 crazy software bugs explained - वीडियो के साथ अंग्रेजी बोलना सीखें

It's not a bug, it's a feature.

Programmers often use that excuse to justify their garbage code, and sometimes it actually works.

Like in the original Sid Meier's Civilization game, Gandhi's aggression level was set to an unsigned integer of 1, making him a super chill pacifist.

But when another civ adopts diplomacy, it reduces aggression by 2.

1-2 equals 255, or an unsigned integer underflow, which maxed out Gandhi's aggression and turned him into a diabolical thermonuclear enthusiast.

Civ players love this bug so much that it became a feature.

That's the urban legend anyway, but it's all fun and games until people start losing money and getting blown up in real life.

Real men test in production, and in today's video, we're going to take this carbon fiber submarine

and travel down the software bug iceberg to look at 25 examples of bad code that changed the world.

Where the deeper we go, the more severe the consequences.

If you survive until the end, you'll understand why to do fix it later might be the last line of code you ever write.

Our journey begins in the year 2008, a time when people still use devices like iPods to listen to music.

Microsoft had its own crappy knockoff called Zune.

The device worked great until December 31st, New Year's Eve, when every Zune around the world froze and became a very stylish brick.

The screen displayed a loading bar and would get stuck at 100% and then just stay there.

It could only be fixed manually by removing the battery.

This happened because it wasn't programmed to account for the extra day in a leap year.

When reaching the 366th day of a leap year, the software attempted to reset, but a logic error in handling the day count meant the device could not exit the loop, causing it to freeze permanently.

This code could be easily fixed by simply breaking out of the loop when the number of days reached 367.

But not all bugs are that easy to fix, like the infamous Pentium FDIV bug of 94.

Occasionally, when a program did floating point division on a Pentium chip, it would return an incorrect value.

It only happened in about 1 in 9 billion division operations, but was discovered by a professor at Lynchburg College while doing computational number theory.

Originally, he thought it was his own bug, but after extensive testing, he reported it to Intel.

Intel tried to downplay it, but then IBM suspended Intel chips in their PCs, and it turned into a massive PR nightmare.

The core issue is related to the SRT division algorithm, which is a way to speed up division by using lookup tables to estimate the next digit of a quotient.

The lookup table contains 1066 entries, but the problem in this bug is that 5 entries were missing,

causing certain combinations of numbers to return incorrect results at the hardware level.

That's pretty bad, but this next bug was found inside an Apple.

In 2019, you could use your iPhone to start a FaceTime call with someone, then while the call is ringing, swipe up to add another person making it a group call, add your own phone number as an additional person,

then FaceTime would glitch out and think the group call was active.

And now you can eavesdrop on the audio from the original recipient's phone.

And then if the person pressed the power button to dismiss the call, it would activate their camera.

What's even crazier is that this bug was discovered by a 14-year-old

while trying to set up a group chat for playing Fortnite.

Then he tells his mom, and his mom tries to report it to Apple.

Apple thinks its code is perfect and just ignores him, but then, about a week later, the bug starts to go viral on social media, and everybody's doing it on live streams.

At this point, Apple disables Group FaceTime entirely, and released a patch about a week later.

They did make things right with the 14-year-old, though, and awarded him a bug bounty and some education funding, but the root of the problem appears to be the fact

that they weren't checking the state of the call before activating the audio stream.

Normally, software bugs cause people to lose money, but sometimes, the opposite is true, like the 2024 Chase ATM glitch.

Most banking systems run on proprietary code that was written 50 years ago using ancient languages like COBOL.

Usually, when you deposit a check, it needs a few days to clear before you can withdraw those funds from an ATM.

But at JPMorgan Chase, some sort of glitch prevented this safeguard, and tons of viral videos hit TikTok of people withdrawing tens of thousands of dollars that they never had,

by simply depositing a fake check and withdrawing money right away.

I'm no fan of the banking system, but unfortunately, this also constitutes check fraud.

A few days later, these people had bank accounts deep in the red

and are now being sued by the bank and may face criminal charges.

That brings us to the end of tier one, and things are going to get a lot crazier from here.

But if you like crazy programming stories, a website you'll want to check out is daily.dev, the sponsor of today's video.

If you're learning to code or learning a new language or framework, it's the one place you can curate all the latest news, tutorials, videos, and content filtered by the topics you're interested in.

When you join a squad, it'll create a personalized news feed on that topic, but more importantly, connect you to a community of like-minded developers where we can all suffer together.

And these aren't bots, but real people of all skill levels who can help you build your network in the tech industry.

And did I mention, it's all entirely free, so check it out with my invite link at daily.dev slash fireship.

But now, it's time to dive below the surface into tier two starting with the AT&T long-distance crash of 1990.

Cell phones were hardly a thing back then, and if you wanted to communicate with someone outside of your village, you would have to pay for a long-distance network.

After a software update, a single faulty line of code caused a network switch to crash and automatically reboot.

One failed switch is no big deal, but when it would reboot, it would cause neighboring switches to fail as well, resulting in a cascade of failures that took out the entire network.

The bug was a C program that included a break statement within an if clause within a switch clause.

When a second message was received while the switch was still processing the first, the program dropped out of the if clause prematurely and overwrote crucial data, causing the switch to reset.

And this created a domino effect that blocked 50 million calls around the world.

A dropped call is annoying, but the last place you want to bug is in an aircraft, especially when it's in the oxygen system of an F-35 fighter jet.

In 2012, pilots were experiencing hypoxia-like symptoms during flights, like dizziness, disorientation, and overconfidence just like a drunk driver.

These jets have a complex oxygen generation system called OBOGS.

Usually it worked fine, but the underlying software wasn't robust enough to account for real-time variables like rapid altitude changes or variations in pilot breathing patterns.

When it comes to data, the old saying goes, garbage in, garbage out.

And when that data controls how much oxygen you get while flying a $100 million lethal weapon, you better be damn sure you test your code for all possible variables.

In this case, the code is top secret, but it's probably C++, and luckily nobody got blown up and it was later fixed with a software update.

Speaking of airplanes though, back in 2008, the 4.3 billion pound Heathrow Terminal 5 opened,

and it only took a few days for a software bug to result in over 500 cancel flights and 42,000 lost bags.

The new terminal had a complex automated baggage handling system with 30 miles of conveyor belts

and RFIDs and barcodes to manage up to 12,000 bags per hour.

When they pushed a prod, several different software systems failed to communicate.

Employees couldn't log in, RFID tracking systems couldn't track bags, among many other issues.

And this led to an entire breakdown of the system, costing 16 million pounds to fix, which is a prime example of when testing and production goes wrong.

But well-tested code breaks too.

In 1982, the Vancouver Stock Exchange began to slowly decrease in value due to a rounding error.

The error was so minor though, that nobody even noticed.

The value of the total index started at 1,000, but then over the course of two years dropped to 520, until one day somebody was like, what the hell is going on here?

It was a software bug, but had the index increased in value, it would have been a feature.

What happened was the software was truncating each stock price change to two decimal places instead of rounding.

One stock in an index of thousands only has a minor impact, but over time, it creates a cumulative rounding error.

And in this case, they had to completely recalculate the value of the index from scratch.

And that brings us to November 1988, when Robert Morris accidentally created the Morris Worm on this here floppy disk.

Morris was not an evil hacker, but a graduate student at Cornell, who released a self-replicating computer program designed to gauge the size of the internet, which was tiny back then,

but it rapidly spread across Unix-based systems, and crashed thousands of computers in the process by overwhelming their resources.

It took out 6,000 computers, which at that time was around 10% of the total internet.

The worm itself exploited weaknesses in things like the SendMail protocol and a buffer overflow vulnerability in the Finger program, which provided information about users on the network.

The program would then execute code remotely on these machines and send itself to other machines on the network.

His plan almost worked, but there was a bug in his code that would reinfect the same computer over and over again.

Eventually, it took out MIT, UC Berkeley, and NASA, and resulted in Morris getting the first felony conviction under the Computer Fraud and Abuse Act.

But now it's time to dive deeper into Tier 3, where things actually start to blow up, like NASA's Mars Climate Orbiter in 1999,

which torched $125 million in taxpayer money when it burned up entering the atmosphere of Mars.

And that happened because one software team used imperial units, pound force, while the other team used metric units, newton seconds.

And that's kind of a big issue when it comes to space travel, especially when just a few years ago, in 1996, bad software caused the Ariane 5 rocket to explode.

Exactly 37 seconds after liftoff, a software bug in the inertial reference system led to a critical data conversion error,

where a 64-bit floating point number was incorrectly converted to a 16-bit integer.

This made the rocket think it was 90 degrees off course, and when it went to correct at high velocity, it went boom.

Luckily, there was nobody on board, but in 2010, the Toyota Prius put a bunch of people in danger due to a bug in its anti-lock braking system,

which would cause momentary delays in braking under certain conditions, like on icy roads or potholes.

100

There's something wrong with the brakes.

101

The computer created a 0.4 second delay, switching from regenerative braking to friction braking, and this resulted in a recall of 400,000 vehicles,

102

which was a beautiful thing because it meant there weren't as many Prius drivers driving slow in the fast lane.

103

That was a big mistake made by low-level systems engineers, but front-end developers screwed things up too, like the 2020 Citibank bad UI disaster.

104

Citibank was intending to make an interest payment of $8 million, however, due to a poorly designed UI, they accidentally transferred the full loan amount of approximately $900 million.

105

The software had a confusing three-screen process for payments, and the interface made it appear as though checking certain boxes would ensure only interest was paid, but in reality, it did the opposite.

106

Now, after Citibank accidentally paid back this money, they asked the lenders if they could have it back, and they were like, nah, bro.

107

So Citibank took them to court, but the court ruled in favor of the lenders

108

and let them keep the $900 million that Citibank accidentally transferred due to the bad UI.

109

That's pretty bad, but this tier wouldn't be complete if we didn't talk about the Y2K bug.

110

In the early days of programming, no one thought the world would still be around by the year 2000, so they typically used only two digits to represent years.

111

As the year 2000 approached, people realized this and began to panic that computers would interpret 00 as the year 1900 instead of 2000.

112

What's funny about Y2K is that this issue never caused any widespread disasters, but the media hysteria around it led to billions of dollars being spent in preparation for the end of the world.

113

But now it's time to ratchet up the pressure in tier 4, which includes critical bugs that caused widespread damage around the world.

114

Like the Knight Capital Money Burn speedrun, this company used algorithms to perform trades in the stock market.

115

However, the developers accidentally used a variable name linked to an outdated testing algorithm called PowerPeg, which had been inactive since 2003.

116

This algorithm was designed to manipulate virtual markets by buying high and selling low.

117

Now, if you don't know much about investing, usually you want to buy low and then sell high.

118

That's not financial advice though.

119

When they pushed a prod, the algorithm went haywire and started flooding the New York Stock Exchange with incorrect trades.

120

4 million trades in just 45 minutes to be exact.

121

Knight Capital lost $440 million in a single day and wiped out 75% of investors' equity.

122

But a far scarier bug is Heartbleed of 2014, which was a vulnerability in OpenSSL, a library that's supposed to make internet communication secure,

123

which was caused by a simple coding oversight, a missing bounds check in the implementation of the Transport Layer Security, or TSL heartbeat extension.

124

Normally, when a client sends a heartbeat request, it includes a payload and expects the server to reply with the same payload.

125

However, due to improper input validation, an attacker could send a malicious heartbeat request that appeared legitimate, and this allowed attackers to repeatedly request memory contents from the server,

126

potentially gaining access to highly confidential data without any way to be detected.

127

And that's unimaginably bad because two-thirds of the internet servers were vulnerable.

128

Now, we already talked about Toyota's braking problem, but they also implemented an acceleration problem, where your car would magically speed up uncontrollably and try to kill you.

129

It led to 6,200 complaints, 52 injuries, and 89 deaths.

130

This one could have gone in Tier 5, but it was a multitude of issues that caused the problem, not just the software.

131

But the investigation revealed that a software bug in the electronic throttle control system was partly to blame.

132

Apparently, the code had terrible error handling logic and lack redundancy, and the code was structured in a way to allow multiple failure points, which could cascade through the entire system.

133

And that's not good when that software is in control of your throttle.

134

Toyota had to recall 9 million vehicles and pay $1.2 billion in fines and settlements.

135

In the previous tier, Y2K was a bit disappointing, but just a few months ago, CrowdStrike gave us the Y2K we deserved.

136

As a cybersecurity company, they convinced companies to install this thing called the Falcon Sensor, which has kernel-level access to all their employees' machines.

137

Everything was going great until one day, somebody pushed a bad configuration file called Channel File 291 to production.

138

This resulted in millions of Windows machines entering the blue screen of death.

139

Hospitals shut down, flights were canceled, and people nearly starved to death after the Arby's drive-thru went down.

140

It was bad, but not as bad as the Northeastern blackout, which occurred on August 14, 2003, when nearly 50 million people in the United States and Canada lost power.

141

First Energy Corporation had a monitoring system for the power grid, but its error handling code wasn't so good.

142

If multiple alarms were generated in a short period of time, the entire system would enter an unrecoverable state without notifying the operators, and this meant that no new alarms would be shown,

143

and no existing ones be cleared, which meant that it looked like everything was normal to the operators, but in reality, half the damn country didn't have power.

144

Luckily, nobody died, but now our submarine is making a weird cracking noise as we get down to the bottom tier.

145

In 1994, a military helicopter of the Royal Air Force took off in Scotland in foggy conditions.

146

The aircraft has an automatic throttle control that takes inputs from sensors placed around the aircraft.

147

But in these challenging conditions, the system became overloaded and didn't know what to do.

148

When things started getting weird, the pilots tried to regain manual control, but eventually lost total control, and 25 people died in the process.

149

The investigation found that the throttle control software was not adequately tested under these conditions.

150

But perhaps the most famous deadly software bug is the Therac-25 radiation machine.

151

This was a device used to treat cancer patients by providing a therapeutic dose of radiation.

152

Unfortunately, it was yet another device with inadequate air handling, and when it encountered a race condition, it wouldn't just break, but it would deliver the patient with a lethal dose of radiation.

153

And at least three patients died after receiving radiation doses 100 times higher than intended.

154

In addition to the race condition bug, the device also removed mechanical interlocks that provide a physical safeguard from things like this happening, and instead chose to rely entirely on software.

155

And that was a fatal mistake.

156

But usually when software kills people, it has to do with the military-industrial complex.

157

In 1991, the United States was fighting the Gulf War in Iraq, and Saddam launched a Scud missile that should have been easily intercepted by the Patriot missile system.

158

Unfortunately, there was a bug in the system's clock and timing calculations.

159

It had a 24-bit timer that tracked time in tenths of seconds, but after it was in operation for over 100 hours without a reset,

160

the timer overflowed, causing it to report incorrect information about incoming threats, and that incoming Scud missile killed 28 American soldiers.

161

For that issue, you can blame a back-end developer, but the 1988 Aegis Combat System disaster was caused by a front-end developer.

162

One day, it accidentally shot down a civilian plane from Iran with 290 souls on board.

163

The investigation revealed

164

that a lack of user-friendly information on the system's display was one of the key reasons

165

that they misidentified the friendly plane as a threat.

166

There was a timing lag that read to misleading altitude data, which ultimately led to a tragic mistake.

167

One of the biggest military contractors, though, is Boeing, and they make many of the jets we fly on, like the 737 MAX.

168

Thanks to programmers, these modern jets practically fly themselves, but maybe that's not a good thing.

169

These planes were updated with a thing called the Maneuvering Characteristics Augmentation System, or MCAS, which would automatically push the nose down to prevent a stall.

170

There were two angle-of-attack sensors hooked up to the system, but it would initiate the nose-down sequence if only one of them provided weird data.

171

But that was a major oversight in the programming, because if one of the sensors provided faulty data, it would start pushing the nose down.

172

And that's exactly what happened on two tragic flights, Lion Air Flight 610 in 2018 and Ethiopian Airlines Flight 302 in 2019,

173

where 346 passengers and crew lost their lives.

174

Boeing's reputation was permanently bricked after all 737 MAX planes were grounded, and the fix was to simply make sure that both sensors were providing consistent data before pushing the nose down.

175

This final tier was tragic, but on the bright side, good code has saved a lot more lives than the lives lost by bad code.

176

Writing entirely bug-free code is difficult, but remember, there are two ways to write error-free programs.

177

Only the third one works.

178

Thanks for watching, and I will see you in the next one.

📺 उसी चैनल से

✨ अनुशंसित वीडियो

39 वाक्य

Intel chips can’t possibly be this bad… 100% crash rate?

Business EnglishUniversity StudentsWorking Adults

629 वाक्य

Last Cheater Standing Wins $10,000!

Business EnglishUniversity StudentsWorking Adults

190 वाक्य

MySQL took 21 years to fix this bug

Business EnglishUniversity StudentsWorking Adults

364 वाक्य

World's Deadliest Computer Virus: WannaCry

Business EnglishUniversity StudentsWorking Adults

187 वाक्य

The Most Expensive MISTAKES Ever

Business EnglishUniversity StudentsWorking Adults

77 वाक्य

The Hidden War Against Steam

Business EnglishUniversity StudentsWorking Adults

252 वाक्य

Memory is crazy expensive so I made my own…

Business EnglishUniversity StudentsWorking Adults

131 वाक्य

macOS 27 Released! What's New?

Business EnglishUniversity StudentsWorking Adults

17 वाक्य

What is Software Testing & Why Testing is Important?

Business EnglishUniversity StudentsWorking Adults

211 वाक्य

USB4 is a Glorious Mess

Business EnglishUniversity StudentsWorking Adults

105 वाक्य

Gilfoyle Hacks Jian Yang's Smart Fridge 🤓 Silicon Valley

Business EnglishDaily ConversationUniversity Students

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो में शैडोइंग के लिए 178 वाक्य और 3454 शब्द हैं। बोला गया हिस्सा 16:49 लंबा है। वक्ता तेज़ बोलता है, लगभग 205 शब्द प्रति मिनट, इसलिए जुड़ी हुई और कमज़ोर ध्वनियाँ ज़्यादा मिलेंगी। केवल 77% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं, इसलिए शब्दावली कठिन है।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 कम प्रचलित शब्द, उच्चारण और अर्थ के साथ:

developer /dɪˈvɛləpɚ/ (संज्ञा) — विकासक. A person or entity engaged in the creation or improvement of certain classes of products.
algorithm /ˈælɡəɹɪðm̩/ (संज्ञा) — अल्गोरिद्म. A collection of ordered steps that solve a mathematical problem. A precise step-by-step plan for a computational procedure that possibly begins with an input…
incorrect /ˌɪn.kəˈɹɛkt/ (विशेषण) — त्रुटिपूर्ण. Not correct; erroneous or wrong.
jet /ˈd͡ʒɛt/ (संज्ञा) — प्रवाह. A collimated stream, spurt or flow of liquid or gas from a pressurized container, an engine, etc.
oxygen /ˈɑksɪd͡ʒən/ (संज्ञा) — जारक, ऑक्सीजन. The chemical element (symbol O) with an atomic number of 8 and relative atomic mass of 15.9994. It is a colorless and odorless gas. Sometimes called elemental…
garbage /ˈɡɑɹ.bɪd͡ʒ/ (संज्ञा) — कचरा, कूड़ा. Food waste material of any kind.
missile /ˈmɪs.aɪl/ (संज्ञा) — प्रक्षेपास्त्र. Any object used as a weapon by being thrown or fired through the air, such as stone, arrow or bullet.
tragic /ˈtɹæd͡ʒɪk/ (विशेषण) — त्रासदिक, वियोगांत. Causing great sadness or suffering.
heartbeat /ˈhɑɹtˌbit/ (संज्ञा) — धड़कन. One pulsation of the heart; especially an irregular one, hence the emotion which causes it.
topic /ˈtɑpɪk/ (संज्ञा) — प्रसंग, विषय. A subject; a theme; a category or general area of interest.
server /ˈsɝvɚ/ (संज्ञा) — सर्वर. A program that provides services to other programs or devices, either in the same computer or over a computer network.
disaster /dɪˈzɑːs.təː/ (संज्ञा) — आपदा, तबाही. An unexpected natural or man-made catastrophe of substantial extent causing significant physical damage or destruction, loss of life or sometimes permanent…
fraud /ˈfɹɔːd/ (संज्ञा) — धोखा, छल. The crime of stealing or otherwise illegally obtaining money by use of deception tactics.
operator /ˈɑpəˌɹeɪtɚ/ (संज्ञा) — संचालक. A person or organisation that operates a device, system, service, etc.
rocket /ˈɹɑk.ɪt/ (संज्ञा) — राकेट, प्रक्षेपास्त्र. A cylindrical projectile that can be fired to a great height through combustion, (specifically) a type of firework of this form, typically exploding with light…

वीडियो में आने वाली फ़्रेज़ल वर्ब

look at (क्रिया) — हेरना. To observe or watch.

ध्यान देने योग्य उच्चारण

वक्ता 21 बार संक्षिप्त रूपों का प्रयोग करता है, जैसे didn't, wasn't, couldn't। इन्हें वैसे ही छोटा बोलें जैसा आप सुनते हैं।

“th” की ध्वनियाँ: algorithm /ˈælɡəɹɪðm̩/, lethal /ˈliː.θəl/, breathe /bɹiːð/
“sh” और “zh” की ध्वनियाँ: radiation /ˌɹeɪ.diˈeɪ.ʃən/, aggression /əˈɡɹɛʃən/, reputation /ˌɹɛpjʊˈteɪʃən/, extension /ɪkˈstɛnʃən/, occasionally /əˈkeɪʒənəli/
लंबे शब्द — बलाघात सही रखें: accidentally /ˌæk.sɪˈdɛnt(ə)li/, developer /dɪˈvɛləpɚ/, radiation /ˌɹeɪ.diˈeɪ.ʃən/, operator /ˈɑpəˌɹeɪtɚ/, communicate /kəˈmjuːnɪkeɪt/

इस वीडियो से अभ्यास कैसे करें

पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
0.75× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर developer, algorithm, incorrect जैसे शब्दों पर ध्यान दें।

इस वीडियो का व्याकरण

वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:

संरचना	वीडियो में
शर्त वाले वाक्य if + उपवाक्य, will/would + क्रिया — शर्त और उसका नतीजा	If you survive until the end, you'll understand
Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है	was set · be fixed · wasn't programmed
Relative clauses who / which + उपवाक्य — व्यक्ति या वस्तु के बारे में अतिरिक्त जानकारी	algorithm, which is · fix, which is · internet, which was

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: 25 crazy software bugs explained - वीडियो के साथ अंग्रेजी बोलना सीखें

10 very promising Open Source Projects you haven’t heard of

7 Programming myths that waste your time

DHH has gone completely off the rails...

DNS Explained in 100 Seconds

Anthropic begged the world to stop AI… then shipped this

One man just liberated Fable... and now it’s illegal

7 Things No Programmer Ever Wants to Hear

80% of programmers are NOT happy… why?

The most interesting hack in history just got weirder...

Raspberry Pi Explained in 100 Seconds

Did Google just kickstart the intelligence explosion?

Tragic mistake... Anthropic leaks Claude’s source code

100+ Docker Concepts you Need to Know

When open-sourcing your code goes wrong...

Docker in 100 Seconds

The mystery is solved... and the answer is 40x cheaper than Claude

An ex-OpenAI researcher just deleted language from the LLM...

Git Explained in 100 Seconds

There's a new Linux distro in town for developers...

The "vibe coding" mind virus explained…

Intel chips can’t possibly be this bad… 100% crash rate?

Last Cheater Standing Wins $10,000!

MySQL took 21 years to fix this bug

World's Deadliest Computer Virus: WannaCry

The Most Expensive MISTAKES Ever

The Hidden War Against Steam

Memory is crazy expensive so I made my own…

macOS 27 Released! What's New?

What is Software Testing & Why Testing is Important?

USB4 is a Glorious Mess

Gilfoyle Hacks Jian Yang's Smart Fridge 🤓 Silicon Valley

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो की मुख्य शब्दावली

वीडियो में आने वाली फ़्रेज़ल वर्ब

ध्यान देने योग्य उच्चारण

इस वीडियो से अभ्यास कैसे करें

इस वीडियो का व्याकरण

शैडोइंग तकनीक क्या है?