What are some of the worst things about being a programmer? Let's look at 7 dreaded messages that a software engineer never wants to receive. 

#programming #tech #comedy 

💬 Chat with Me on Discord

https://discord.gg/fireship

🔗 Resources

Programmer Stereotypes https://youtu.be/_k-F-MMvQV4
Technical Interview Survival https://youtu.be/1t1_a1BZ04o

🔥 Get More Content - Upgrade to PRO

Upgrade at https://fireship.io/pro
Use code YT25 for 25% off PRO access 

🎨 My Editor Settings

- Atom One Dark 
- vscode-icons
- Fira Code Font

🔖 Topics Covered

- Worst things about programming
- Should I become a programmer?
- Software engineer career drawbacks
- Programming memes
- The bad parts of learning to code
2024-02-04T05:19:23.939Z
nova-2
2-general-nova
2024-01-09.29447
30089e05-99d1-4376-b32e-c263170674af
a4880c8a-271d-4f7c-8823-53b2d8a85800
664c1479efc5a401a5ee5bd502ed57962e5f9c69e08a42392ad6a830e8f0410f
67875a7f-c9c4-48a0-aa55-5bdb8a91c34a
deprecated
Being a software engineer sucks.
I was told I would be working in a fast paced exciting environment, but in reality, I'm stuck in this cubicle building super complex stuff that nobody understands or appreciates.
If I had a time machine, I would do 2 things.
1, I would tell Harambe to get away from that kid.
And 2, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires like bridges and skyscrapers.
Unfortunately, I haven't figured out how to build a time machine in JavaScript yet.
Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen.
Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane.
Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad.
In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear.
Speaking of which, I finally started a discord, so feel Free to chat with me over there after this video.
We've got some t shirts and licenses to JetBrains software to give away over there.
One of the biggest problems with software engineering is that you don't want your friends and family to find out what you do.
The reason is you'll get messages like this from your uncle or old roommate asking if you want to build an app together.
It will consist of a very dumb idea that's impossibly complex cute, like Uber but for horses, or TikTok without the Chinese with a $500 budget.
Messages like this are so painful because software engineers are usually introverts who have a hard time No.
What you wanna do is respond and say, hey, that's an awesome idea.
I would love to build it for you, but my rate is $300 an hour.
What they'll likely do is come back with a counter Offer of $0 per hour, but 10% equity in the company, which will eventually be worth 1,000,000,000.
So that's pretty much checkmate.
Check speaks for itself.
I would just recommend accepting the offer and building the app to get them to go away.
Now, when you're not building apps for friends and family, you should be working on your on side projects.
And in doing that, you'll likely use the cloud like AWS.
One of the worst messages you can receive is a cloud billing alert like, hey, it's AWS.
Your $25 it has been exceeded by $2,300,000 Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic.
The easiest solution is to just stop using AWS and pretend nothing ever happened.
If Jeff ever sends his guys after you, just tell them your account got hacked.
That may or may not work, And if it doesn't, you can at least find comfort in knowing there are many other homeless people out there who simply forgot to turn off an EC 2 instance.
Another dreaded catastrophic thing a developer doesn't wanna is that a production database has been dropped accidentally, along with all of your company's data that was worth 1,000,000,000 of dollars.
You just made the simple mistake of dropping prod instead of dev.
When something Something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state.
If not, now would be a good time You start looking for a new job.
Dropping a database is incredibly easy and can be accomplished with a single line of code.
You can use this knowledge to fight back against the system, as this person did here by weaponizing SQL injection against speed cameras.
Dropping a database is bad, but at least it's over quickly.
Many developers suffer worst bait.
Like this guy who got a message from his boss, assigning him to a legacy Angular JS version 1 code base that needs to be migrated to Angular 14.
Sadly, Like, the previous developer died of old age, and was the only one who had any idea how anything in this code base worked.
He knew exactly how to keep his job by creating an overly complex like code base without any comments or documentation, and now it's your turn to update it.
Fuck my life.
This job will take more skill and ingenuity duty than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care.
Because by that time, it'll be time to migrate your legacy code into the hot new JavaScript framework of 2025.
Speaking of which, something a web developer never wants to hear is that a new better JavaScript Framework has been invented.
When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible.
Now, normally You can create an echo chamber to convince yourself that your chosen framework is absolutely 100% the best in every use case.
However, at some point, you may be convinced that a better frame or does in fact exist.
When that day comes, you'll need to turn your back on your tribe and lose many friends in the process.
And it's not exactly easy to make new friends when you're a software engineer.
I can't sit here.
But one of the most annoying things that can happen to you is when a non technical person like a client or marketing expert asks you to make one small change to an already finished product.
Like, let's just move this nav bar from the top over to the side here.
It should be an easy change for you to make.
You don't not wanna look like a 10 x developer, so you go and do it, but it takes like 20 hours and modifications in a 100 different HTML and CSS files.
Then as soon as you commit your work that Same person will come back and say, you know what?
I think I liked it better the first way.
Let's go ahead and change it back.
It's no secret that the most important skill of a software engineer is being able to Google things effectively.
That means one of the worst things that can happen to you is running into a problem that nobody else has already solved for you.
It's painful enough when 0 results come back on Google with your error message, but an even worse thing can happen.
You might search an error and get a single result Built on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you.
As you scroll down, hoping for a well documented and detailed solution, you find All he posted was fixed, all good now.
And now you have to figure out the problem all by yourself.
Being the chad that you are, you get to work.
And as soon as you're about to solve the problem, you get a notification that it's time for your daily stand up meeting.
Thanks for watching, and I will see you in the next one.

Speaker 0: Being a software engineer sucks. I was told I would be working in a fast paced exciting environment, but in reality, I'm stuck in this cubicle building super complex stuff that nobody understands or appreciates. If I had a time machine, I would do 2 things. 1, I would tell Harambe to get away from that kid. And 2, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires like bridges and skyscrapers.

Unfortunately, I haven't figured out how to build a time machine in JavaScript yet. Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen. Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane. Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad. In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear.

Speaking of which, I finally started a discord, so feel Free to chat with me over there after this video. We've got some t shirts and licenses to JetBrains software to give away over there. One of the biggest problems with software engineering is that you don't want your friends and family to find out what you do. The reason is you'll get messages like this from your uncle or old roommate asking if you want to build an app together. It will consist of a very dumb idea that's impossibly complex cute, like Uber but for horses, or TikTok without the Chinese with a $500 budget.

Messages like this are so painful because software engineers are usually introverts who have a hard time No. What you wanna do is respond and say, hey, that's an awesome idea. I would love to build it for you, but my rate is $300 an hour. What they'll likely do is come back with a counter Offer of $0 per hour, but 10% equity in the company, which will eventually be worth 1,000,000,000. So that's pretty much checkmate.

Check speaks for itself. I would just recommend accepting the offer and building the app to get them to go away. Now, when you're not building apps for friends and family, you should be working on your on side projects. And in doing that, you'll likely use the cloud like AWS. One of the worst messages you can receive is a cloud billing alert like, hey, it's AWS.

Your $25 it has been exceeded by $2,300,000 Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic. The easiest solution is to just stop using AWS and pretend nothing ever happened. If Jeff ever sends his guys after you, just tell them your account got hacked. That may or may not work, And if it doesn't, you can at least find comfort in knowing there are many other homeless people out there who simply forgot to turn off an EC 2 instance. Another dreaded catastrophic thing a developer doesn't wanna is that a production database has been dropped accidentally, along with all of your company's data that was worth 1,000,000,000 of dollars.

You just made the simple mistake of dropping prod instead of dev. When something Something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state. If not, now would be a good time You start looking for a new job. Dropping a database is incredibly easy and can be accomplished with a single line of code. You can use this knowledge to fight back against the system, as this person did here by weaponizing SQL injection against speed cameras.

Dropping a database is bad, but at least it's over quickly. Many developers suffer worst bait. Like this guy who got a message from his boss, assigning him to a legacy Angular JS version 1 code base that needs to be migrated to Angular 14. Sadly, Like, the previous developer died of old age, and was the only one who had any idea how anything in this code base worked. He knew exactly how to keep his job by creating an overly complex like code base without any comments or documentation, and now it's your turn to update it.

Fuck my life. This job will take more skill and ingenuity duty than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care. Because by that time, it'll be time to migrate your legacy code into the hot new JavaScript framework of 2025. Speaking of which, something a web developer never wants to hear is that a new better JavaScript Framework has been invented. When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible.

Now, normally You can create an echo chamber to convince yourself that your chosen framework is absolutely 100% the best in every use case. However, at some point, you may be convinced that a better frame or does in fact exist. When that day comes, you'll need to turn your back on your tribe and lose many friends in the process. And it's not exactly easy to make new friends when you're a software engineer. I can't sit here.

But one of the most annoying things that can happen to you is when a non technical person like a client or marketing expert asks you to make one small change to an already finished product. Like, let's just move this nav bar from the top over to the side here. It should be an easy change for you to make. You don't not wanna look like a 10 x developer, so you go and do it, but it takes like 20 hours and modifications in a 100 different HTML and CSS files. Then as soon as you commit your work that Same person will come back and say, you know what?

I think I liked it better the first way. Let's go ahead and change it back. It's no secret that the most important skill of a software engineer is being able to Google things effectively. That means one of the worst things that can happen to you is running into a problem that nobody else has already solved for you. It's painful enough when 0 results come back on Google with your error message, but an even worse thing can happen.

You might search an error and get a single result Built on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you. As you scroll down, hoping for a well documented and detailed solution, you find All he posted was fixed, all good now. And now you have to figure out the problem all by yourself. Being the chad that you are, you get to work. And as soon as you're about to solve the problem, you get a notification that it's time for your daily stand up meeting.

Thanks for watching, and I will see you in the next one.
Being a software engineer sucks. I was told I would be working in a fast paced exciting environment, but in reality, I'm stuck in this cubicle building super complex stuff that nobody understands or appreciates. If I had a time machine, I would do 2 things. 1, I would tell Harambe to get away from that kid. And 2, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires like bridges and skyscrapers. Unfortunately, I haven't figured out how to build a time machine in JavaScript yet. Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen. Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane. Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad. In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear. Speaking of which, I finally started a discord, so feel Free to chat with me over there after this video.
We've got some t shirts and licenses to JetBrains software to give away over there. One of the biggest problems with software engineering is that you don't want your friends and family to find out what you do. The reason is you'll get messages like this from your uncle or old roommate asking if you want to build an app together.
software development
software
It will consist of a very dumb idea that's impossibly complex cute, like Uber but for horses, or TikTok without the Chinese with a $500 budget.
Messages like this are so painful because software engineers are usually introverts who have a hard time No. What you wanna do is respond and say, hey, that's an awesome idea. I would love to build it for you, but my rate is $300 an hour. What they'll likely do is come back with a counter Offer of $0 per hour, but 10% equity in the company, which will eventually be worth 1,000,000,000. So that's pretty much checkmate. Check speaks for itself. I would just recommend accepting the offer and building the app to get them to go away. Now, when you're not building apps for friends and family, you should be working on your on side projects. And in doing that, you'll likely use the cloud like AWS.
earnings
software development
software
One of the worst messages you can receive is a cloud billing alert like, hey, it's AWS. Your $25 it has been exceeded by $2,300,000 Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic. The easiest solution is to just stop using AWS and pretend nothing ever happened. If Jeff ever sends his guys after you, just tell them your account got hacked. That may or may not work, And if it doesn't, you can at least find comfort in knowing there are many other homeless people out there who simply forgot to turn off an EC 2 instance. Another dreaded catastrophic thing a developer doesn't wanna is that a production database has been dropped accidentally, along with all of your company's data that was worth 1,000,000,000 of dollars. You just made the simple mistake of dropping prod instead of dev. When something Something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state.
If not, now would be a good time You start looking for a new job. Dropping a database is incredibly easy and can be accomplished with a single line of code. You can use this knowledge to fight back against the system, as this person did here by weaponizing SQL injection against speed cameras. Dropping a database is bad, but at least it's over quickly. Many developers suffer worst bait. Like this guy who got a message from his boss, assigning him to a legacy Angular JS version 1 code base that needs to be migrated to Angular 14.
databases
data management
Sadly, Like, the previous developer died of old age, and was the only one who had any idea how anything in this code base worked. He knew exactly how to keep his job by creating an overly complex like code base without any comments or documentation, and now it's your turn to update it.
software development
Fuck my life. This job will take more skill and ingenuity duty than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care. Because by that time, it'll be time to migrate your legacy code into the hot new JavaScript framework of 2025. Speaking of which, something a web developer never wants to hear is that a new better JavaScript Framework has been invented. When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible. Now, normally You can create an echo chamber to convince yourself that your chosen framework is absolutely 100% the best in every use case. However, at some point, you may be convinced that a better frame or does in fact exist. When that day comes, you'll need to turn your back on your tribe and lose many friends in the process. And it's not exactly easy to make new friends when you're a software engineer. I can't sit here. But one of the most annoying things that can happen to you is when a non technical person like a client or marketing expert asks you to make one small change to an already finished product. Like, let's just move this nav bar from the top over to the side here. It should be an easy change for you to make. You don't not wanna look like a 10 x developer, so you go and do it, but it takes like 20 hours and modifications in a 100 different HTML and CSS files.
Then as soon as you commit your work that Same person will come back and say, you know what? I think I liked it better the first way. Let's go ahead and change it back. It's no secret that the most important skill of a software engineer is being able to Google things effectively. That means one of the worst things that can happen to you is running into a problem that nobody else has already solved for you.
software
software development
artificial intelligence
computer science
google
It's painful enough when 0 results come back on Google with your error message, but an even worse thing can happen. You might search an error and get a single result Built on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you.
google
As you scroll down, hoping for a well documented and detailed solution, you find All he posted was fixed, all good now. And now you have to figure out the problem all by yourself. Being the chad that you are, you get to work. And as soon as you're about to solve the problem, you get a notification that it's time for your daily stand up meeting. Thanks for watching, and I will see you in the next one.
Being a software engineer sucks. I was told I would be working in a fast paced exciting environment, but in reality, I'm stuck in this cubicle building super complex stuff that nobody understands or appreciates. If I had a time machine, I would do 2 things. 1, I would tell Harambe to get away from that kid. And 2, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires like bridges and skyscrapers. Unfortunately, I haven't figured out how to build a time machine in JavaScript yet. Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen. Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane. Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad. In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear. Speaking of which, I finally started a discord, so feel Free to chat with me over there after this video. We've got some t shirts and licenses to JetBrains software to give away over there. One of the biggest problems with software engineering is that you don't want your friends and family to find out what you do. The reason is you'll get messages like this from your uncle or old roommate asking if you want to build an app together. It will consist of a very dumb idea that's impossibly complex cute, like Uber but for horses, or TikTok without the Chinese with a $500 budget. Messages like this are so painful because software engineers are usually introverts who have a hard time No. What you wanna do is respond and say, hey, that's an awesome idea. I would love to build it for you, but my rate is $300 an hour. What they'll likely do is come back with a counter Offer of $0 per hour, but 10% equity in the company, which will eventually be worth 1,000,000,000. So that's pretty much checkmate. Check speaks for itself. I would just recommend accepting the offer and building the app to get them to go away. Now, when you're not building apps for friends and family, you should be working on your on side projects. And in doing that, you'll likely use the cloud like AWS. One of the worst messages you can receive is a cloud billing alert like, hey, it's AWS. Your $25 it has been exceeded by $2,300,000 Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic. The easiest solution is to just stop using AWS and pretend nothing ever happened. If Jeff ever sends his guys after you, just tell them your account got hacked. That may or may not work, And if it doesn't, you can at least find comfort in knowing there are many other homeless people out there who simply forgot to turn off an EC 2 instance. Another dreaded catastrophic thing a developer doesn't wanna is that a production database has been dropped accidentally, along with all of your company's data that was worth 1,000,000,000 of dollars. You just made the simple mistake of dropping prod instead of dev. When something Something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state. If not, now would be a good time You start looking for a new job. Dropping a database is incredibly easy and can be accomplished with a single line of code. You can use this knowledge to fight back against the system, as this person did here by weaponizing SQL injection against speed cameras. Dropping a database is bad, but at least it's over quickly. Many developers suffer worst bait. Like this guy who got a message from his boss, assigning him to a legacy Angular JS version 1 code base that needs to be migrated to Angular 14. Sadly, Like, the previous developer died of old age, and was the only one who had any idea how anything in this code base worked. He knew exactly how to keep his job by creating an overly complex like code base without any comments or documentation, and now it's your turn to update it. Fuck my life. This job will take more skill and ingenuity duty than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care. Because by that time, it'll be time to migrate your legacy code into the hot new JavaScript framework of 2025. Speaking of which, something a web developer never wants to hear is that a new better JavaScript Framework has been invented. When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible. Now, normally You can create an echo chamber to convince yourself that your chosen framework is absolutely 100% the best in every use case. However, at some point, you may be convinced that a better frame or does in fact exist. When that day comes, you'll need to turn your back on your tribe and lose many friends in the process. And it's not exactly easy to make new friends when you're a software engineer. I can't sit here. But one of the most annoying things that can happen to you is when a non technical person like a client or marketing expert asks you to make one small change to an already finished product. Like, let's just move this nav bar from the top over to the side here. It should be an easy change for you to make. You don't not wanna look like a 10 x developer, so you go and do it, but it takes like 20 hours and modifications in a 100 different HTML and CSS files. Then as soon as you commit your work that Same person will come back and say, you know what? I think I liked it better the first way. Let's go ahead and change it back. It's no secret that the most important skill of a software engineer is being able to Google things effectively. That means one of the worst things that can happen to you is running into a problem that nobody else has already solved for you. It's painful enough when 0 results come back on Google with your error message, but an even worse thing can happen. You might search an error and get a single result Built on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you. As you scroll down, hoping for a well documented and detailed solution, you find All he posted was fixed, all good now. And now you have to figure out the problem all by yourself. Being the chad that you are, you get to work. And as soon as you're about to solve the problem, you get a notification that it's time for your daily stand up meeting. Thanks for watching, and I will see you in the next one.
Being
being
a
a
software
software
engineer
engineer
sucks.
sucks
I
i
was
was
told
told
I
i
would
would
be
be
working
working
in
in
a
a
fast
fast
paced
paced
exciting
exciting
environment,
environment
but
but
in
in
reality,
reality
I'm
i'm
stuck
stuck
in
in
this
this
cubicle
cubicle
building
building
super
super
complex
complex
stuff
stuff
that
that
nobody
nobody
understands
understands
or
or
appreciates.
appreciates
If
if
I
i
had
had
a
a
time
time
machine,
machine
I
i
would
would
do
do
2
2
things.
things
1,
1
I
i
would
would
tell
tell
Harambe
harambe
to
to
get
get
away
away
from
from
that
that
kid.
kid
And
and
2,
2
I
i
would
would
go
go
back
back
to
to
school
school
to
to
become
become
a
a
civil
civil
engineer,
engineer
so
so
I
i
could
could
work
work
outside
outside
building
building
stuff
stuff
everyone
everyone
admires
admires
like
like
bridges
bridges
and
and
skyscrapers.
skyscrapers
Unfortunately,
unfortunately
I
i
haven't
haven't
figured
figured
out
out
how
how
to
to
build
build
a
a
time
time
machine
machine
in
in
JavaScript
javascript
yet.
yet
Now,
now
I
i
would
would
never
never
recommend
recommend
anybody
anybody
choose
choose
software
software
engineering
engineering
as
as
a
a
career,
career
but
but
if
if
you
you
do
do
make
make
bad
bad
life
life
choices
choices
like
like
me,
me
you
you
should
should
be
be
prepared
prepared
for
for
some
some
really
really
bad
bad
things
things
to
to
happen.
happen
Like,
like
every
every
doctor
doctor
eventually
eventually
loses
loses
a
a
patient,
patient
and
and
every
every
pilot
pilot
eventually
eventually
crashes
crashes
a
a
plane.
plane
Likewise,
likewise
every
every
software
software
engineer
engineer
will
will
eventually
eventually
face
face
a
a
merge
merge
conflict,
conflict
and
and
that's
that's
not
not
even
even
very
very
bad.
bad
In
in
today's
today's
video,
video
we'll
we'll
look
look
at
at
7
7
different
different
devastating
devastating
text
text
messages
messages
that
that
no
no
developer
developer
ever
ever
wants
wants
to
to
hear.
hear
Speaking
speaking
of
of
which,
which
I
i
finally
finally
started
started
a
a
discord,
discord
so
so
feel
feel
Free
free
to
to
chat
chat
with
with
me
me
over
over
there
there
after
after
this
this
video.
video
We've
we've
got
got
some
some
t
t
shirts
shirts
and
and
licenses
licenses
to
to
JetBrains
jetbrains
software
software
to
to
give
give
away
away
over
over
there.
there
One
one
of
of
the
the
biggest
biggest
problems
problems
with
with
software
software
engineering
engineering
is
is
that
that
you
you
don't
don't
want
want
your
your
friends
friends
and
and
family
family
to
to
find
find
out
out
what
what
you
you
do.
do
The
the
reason
reason
is
is
you'll
you'll
get
get
messages
messages
like
like
this
this
from
from
your
your
uncle
uncle
or
or
old
old
roommate
roommate
asking
asking
if
if
you
you
want
want
to
to
build
build
an
an
app
app
together.
together
It
it
will
will
consist
consist
of
of
a
a
very
very
dumb
dumb
idea
idea
that's
that's
impossibly
impossibly
complex
complex
cute,
cute
like
like
Uber
uber
but
but
for
for
horses,
horses
or
or
TikTok
tiktok
without
without
the
the
Chinese
chinese
with
with
a
a
$500
$500
budget.
budget
Messages
messages
like
like
this
this
are
are
so
so
painful
painful
because
because
software
software
engineers
engineers
are
are
usually
usually
introverts
introverts
who
who
have
have
a
a
hard
hard
time
time
No.
no
What
what
you
you
wanna
wanna
do
do
is
is
respond
respond
and
and
say,
say
hey,
hey
that's
that's
an
an
awesome
awesome
idea.
idea
I
i
would
would
love
love
to
to
build
build
it
it
for
for
you,
you
but
but
my
my
rate
rate
is
is
$300
$300
an
an
hour.
hour
What
what
they'll
they'll
likely
likely
do
do
is
is
come
come
back
back
with
with
a
a
counter
counter
Offer
offer
of
of
$0
$0
per
per
hour,
hour
but
but
10%
10%
equity
equity
in
in
the
the
company,
company
which
which
will
will
eventually
eventually
be
be
worth
worth
1,000,000,000.
1,000,000,000
So
so
that's
that's
pretty
pretty
much
much
checkmate.
checkmate
Check
check
speaks
speaks
for
for
itself.
itself
I
i
would
would
just
just
recommend
recommend
accepting
accepting
the
the
offer
offer
and
and
building
building
the
the
app
app
to
to
get
get
them
them
to
to
go
go
away.
away
Now,
now
when
when
you're
you're
not
not
building
building
apps
apps
for
for
friends
friends
and
and
family,
family
you
you
should
should
be
be
working
working
on
on
your
your
on
on
side
side
projects.
projects
And
and
in
in
doing
doing
that,
that
you'll
you'll
likely
likely
use
use
the
the
cloud
cloud
like
like
AWS.
aws
One
one
of
of
the
the
worst
worst
messages
messages
you
you
can
can
receive
receive
is
is
a
a
cloud
cloud
billing
billing
alert
alert
like,
like
hey,
hey
it's
it's
AWS.
aws
Your
your
$25
$25
it
it
has
has
been
been
exceeded
exceeded
by
by
$2,300,000
$2,300,000
Maybe
maybe
you
you
clicked
clicked
the
the
wrong
wrong
button
button
or
or
accidentally
accidentally
created
created
an
an
infinite
infinite
loop,
loop
but
but
the
the
important
important
thing
thing
here
here
is
is
not
not
to
to
panic.
panic
The
the
easiest
easiest
solution
solution
is
is
to
to
just
just
stop
stop
using
using
AWS
aws
and
and
pretend
pretend
nothing
nothing
ever
ever
happened.
happened
If
if
Jeff
jeff
ever
ever
sends
sends
his
his
guys
guys
after
after
you,
you
just
just
tell
tell
them
them
your
your
account
account
got
got
hacked.
hacked
That
that
may
may
or
or
may
may
not
not
work,
work
And
and
if
if
it
it
doesn't,
doesn't
you
you
can
can
at
at
least
least
find
find
comfort
comfort
in
in
knowing
knowing
there
there
are
are
many
many
other
other
homeless
homeless
people
people
out
out
there
there
who
who
simply
simply
forgot
forgot
to
to
turn
turn
off
off
an
an
EC
ec
2
2
instance.
instance
Another
another
dreaded
dreaded
catastrophic
catastrophic
thing
thing
a
a
developer
developer
doesn't
doesn't
wanna
wanna
is
is
that
that
a
a
production
production
database
database
has
has
been
been
dropped
dropped
accidentally,
accidentally
along
along
with
with
all
all
of
of
your
your
company's
company's
data
data
that
that
was
was
worth
worth
1,000,000,000
1,000,000,000
of
of
dollars.
dollars
You
you
just
just
made
made
the
the
simple
simple
mistake
mistake
of
of
dropping
dropping
prod
prod
instead
instead
of
of
dev.
dev
When
when
something
something
Something
something
like
like
this
this
happens,
happens
it's
it's
absolutely
absolutely
terrifying,
terrifying
but
but
hopefully
hopefully
you
you
have
have
backups
backups
that
that
are
are
able
able
to
to
restore
restore
it
it
back
back
to
to
its
its
original
original
state.
state
If
if
not,
not
now
now
would
would
be
be
a
a
good
good
time
time
You
you
start
start
looking
looking
for
for
a
a
new
new
job.
job
Dropping
dropping
a
a
database
database
is
is
incredibly
incredibly
easy
easy
and
and
can
can
be
be
accomplished
accomplished
with
with
a
a
single
single
line
line
of
of
code.
code
You
you
can
can
use
use
this
this
knowledge
knowledge
to
to
fight
fight
back
back
against
against
the
the
system,
system
as
as
this
this
person
person
did
did
here
here
by
by
weaponizing
weaponizing
SQL
sql
injection
injection
against
against
speed
speed
cameras.
cameras
Dropping
dropping
a
a
database
database
is
is
bad,
bad
but
but
at
at
least
least
it's
it's
over
over
quickly.
quickly
Many
many
developers
developers
suffer
suffer
worst
worst
bait.
bait
Like
like
this
this
guy
guy
who
who
got
got
a
a
message
message
from
from
his
his
boss,
boss
assigning
assigning
him
him
to
to
a
a
legacy
legacy
Angular
angular
JS
js
version
version
1
1
code
code
base
base
that
that
needs
needs
to
to
be
be
migrated
migrated
to
to
Angular
angular
14.
14
Sadly,
sadly
Like,
like
the
the
previous
previous
developer
developer
died
died
of
of
old
old
age,
age
and
and
was
was
the
the
only
only
one
one
who
who
had
had
any
any
idea
idea
how
how
anything
anything
in
in
this
this
code
code
base
base
worked.
worked
He
he
knew
knew
exactly
exactly
how
how
to
to
keep
keep
his
his
job
job
by
by
creating
creating
an
an
overly
overly
complex
complex
like
like
code
code
base
base
without
without
any
any
comments
comments
or
or
documentation,
documentation
and
and
now
now
it's
it's
your
your
turn
turn
to
to
update
update
it.
it
Fuck
fuck
my
my
life.
life
This
this
job
job
will
will
take
take
more
more
skill
skill
and
and
ingenuity
ingenuity
duty
duty
than
than
building
building
a
a
nuclear
nuclear
submarine,
submarine
and
and
when
when
you
you
finally
finally
finish
finish
the
the
job
job
in
in
a
a
few
few
years,
years
no
no
one
one
will
will
even
even
notice
notice
or
or
care.
care
Because
because
by
by
that
that
time,
time
it'll
it'll
be
be
time
time
to
to
migrate
migrate
your
your
legacy
legacy
code
code
into
into
the
the
hot
hot
new
new
JavaScript
javascript
framework
framework
of
of
2025.
2025
Speaking
speaking
of
of
which,
which
something
something
a
a
web
web
developer
developer
never
never
wants
wants
to
to
hear
hear
is
is
that
that
a
a
new
new
better
better
JavaScript
javascript
Framework
framework
has
has
been
been
invented.
invented
When
when
you
you
learn
learn
a
a
JavaScript
javascript
framework,
framework
you
you
join
join
a
a
tribe,
tribe
and
and
that
that
means
means
everything
everything
outside
outside
that
that
tribe
tribe
is
is
dangerous
dangerous
and
and
terrible.
terrible
Now,
now
normally
normally
You
you
can
can
create
create
an
an
echo
echo
chamber
chamber
to
to
convince
convince
yourself
yourself
that
that
your
your
chosen
chosen
framework
framework
is
is
absolutely
absolutely
100%
100%
the
the
best
best
in
in
every
every
use
use
case.
case
However,
however
at
at
some
some
point,
point
you
you
may
may
be
be
convinced
convinced
that
that
a
a
better
better
frame
frame
or
or
does
does
in
in
fact
fact
exist.
exist
When
when
that
that
day
day
comes,
comes
you'll
you'll
need
need
to
to
turn
turn
your
your
back
back
on
on
your
your
tribe
tribe
and
and
lose
lose
many
many
friends
friends
in
in
the
the
process.
process
And
and
it's
it's
not
not
exactly
exactly
easy
easy
to
to
make
make
new
new
friends
friends
when
when
you're
you're
a
a
software
software
engineer.
engineer
I
i
can't
can't
sit
sit
here.
here
But
but
one
one
of
of
the
the
most
most
annoying
annoying
things
things
that
that
can
can
happen
happen
to
to
you
you
is
is
when
when
a
a
non
non
technical
technical
person
person
like
like
a
a
client
client
or
or
marketing
marketing
expert
expert
asks
asks
you
you
to
to
make
make
one
one
small
small
change
change
to
to
an
an
already
already
finished
finished
product.
product
Like,
like
let's
let's
just
just
move
move
this
this
nav
nav
bar
bar
from
from
the
the
top
top
over
over
to
to
the
the
side
side
here.
here
It
it
should
should
be
be
an
an
easy
easy
change
change
for
for
you
you
to
to
make.
make
You
you
don't
don't
not
not
wanna
wanna
look
look
like
like
a
a
10
10
x
x
developer,
developer
so
so
you
you
go
go
and
and
do
do
it,
it
but
but
it
it
takes
takes
like
like
20
20
hours
hours
and
and
modifications
modifications
in
in
a
a
100
100
different
different
HTML
html
and
and
CSS
css
files.
files
Then
then
as
as
soon
soon
as
as
you
you
commit
commit
your
your
work
work
that
that
Same
same
person
person
will
will
come
come
back
back
and
and
say,
say
you
you
know
know
what?
what
I
i
think
think
I
i
liked
liked
it
it
better
better
the
the
first
first
way.
way
Let's
let's
go
go
ahead
ahead
and
and
change
change
it
it
back.
back
It's
it's
no
no
secret
secret
that
that
the
the
most
most
important
important
skill
skill
of
of
a
a
software
software
engineer
engineer
is
is
being
being
able
able
to
to
Google
google
things
things
effectively.
effectively
That
that
means
means
one
one
of
of
the
the
worst
worst
things
things
that
that
can
can
happen
happen
to
to
you
you
is
is
running
running
into
into
a
a
problem
problem
that
that
nobody
nobody
else
else
has
has
already
already
solved
solved
for
for
you.
you
It's
it's
painful
painful
enough
enough
when
when
0
0
results
results
come
come
back
back
on
on
Google
google
with
with
your
your
error
error
message,
message
but
but
an
an
even
even
worse
worse
thing
thing
can
can
happen.
happen
You
you
might
might
search
search
an
an
error
error
and
and
get
get
a
a
single
single
result
result
Built
built
on
on
an
an
obscure
obscure
forum
forum
from
from
10
10
years
years
ago,
ago
and
and
find
find
some
some
dude
dude
going
going
through
through
the
the
exact
exact
same
same
problem
problem
as
as
you.
you
As
as
you
you
scroll
scroll
down,
down
hoping
hoping
for
for
a
a
well
well
documented
documented
and
and
detailed
detailed
solution,
solution
you
you
find
find
All
all
he
he
posted
posted
was
was
fixed,
fixed
all
all
good
good
now.
now
And
and
now
now
you
you
have
have
to
to
figure
figure
out
out
the
the
problem
problem
all
all
by
by
yourself.
yourself
Being
being
the
the
chad
chad
that
that
you
you
are,
are
you
you
get
get
to
to
work.
work
And
and
as
as
soon
soon
as
as
you're
you're
about
about
to
to
solve
solve
the
the
problem,
problem
you
you
get
get
a
a
notification
notification
that
that
it's
it's
time
time
for
for
your
your
daily
daily
stand
stand
up
up
meeting.
meeting
Thanks
thanks
for
for
watching,
watching
and
and
I
i
will
will
see
see
you
you
in
in
the
the
next
next
one.
one
success
The speaker discusses the devastating effects of software engineering, including messages like "naughty things" and "naughty things," and suggests that developers should not be stuck in a cubicle building for too long. The speaker also discusses the difficulty of dropping a database and the importance of Google's ability to search for mistakes. The speaker concludes that a software engineer is the most important skill in a software industry.
7 Things No Programmer Ever Wants to Hear
Being a software engineer sucks. I was told I would be working in a fast paced exciting environment, but in reality, I'm stuck in this cubicle building super complex stuff that nobody understands or appreciates. If I had a time machine, I would do 2 things. 1, I would tell Harambe to get away from that kid. And 2, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires like bridges and skyscrapers. Unfortunately, I haven't figured out how to build a time machine in JavaScript yet. Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen. Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane. Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad. In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear. Speaking of which, I finally started a discord, so feel Free to chat with me over there after this video. We've got some t shirts and licenses to JetBrains software to give away over there. One of the biggest problems with software engineering is that you don't want your friends and family to find out what you do. The reason is you'll get messages like this from your uncle or old roommate asking if you want to build an app together. It will consist of a very dumb idea that's impossibly complex cute, like Uber but for horses, or TikTok without the Chinese with a $500 budget. Messages like this are so painful because software engineers are usually introverts who have a hard time No. What you wanna do is respond and say, hey, that's an awesome idea. I would love to build it for you, but my rate is $300 an hour. What they'll likely do is come back with a counter Offer of $0 per hour, but 10% equity in the company, which will eventually be worth 1,000,000,000. So that's pretty much checkmate. Check speaks for itself. I would just recommend accepting the offer and building the app to get them to go away. Now, when you're not building apps for friends and family, you should be working on your on side projects. And in doing that, you'll likely use the cloud like AWS. One of the worst messages you can receive is a cloud billing alert like, hey, it's AWS. Your $25 it has been exceeded by $2,300,000 Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic. The easiest solution is to just stop using AWS and pretend nothing ever happened. If Jeff ever sends his guys after you, just tell them your account got hacked. That may or may not work, And if it doesn't, you can at least find comfort in knowing there are many other homeless people out there who simply forgot to turn off an EC 2 instance. Another dreaded catastrophic thing a developer doesn't wanna is that a production database has been dropped accidentally, along with all of your company's data that was worth 1,000,000,000 of dollars. You just made the simple mistake of dropping prod instead of dev. When something Something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state. If not, now would be a good time You start looking for a new job. Dropping a database is incredibly easy and can be accomplished with a single line of code. You can use this knowledge to fight back against the system, as this person did here by weaponizing SQL injection against speed cameras. Dropping a database is bad, but at least it's over quickly. Many developers suffer worst bait. Like this guy who got a message from his boss, assigning him to a legacy Angular JS version 1 code base that needs to be migrated to Angular 14. Sadly, Like, the previous developer died of old age, and was the only one who had any idea how anything in this code base worked. He knew exactly how to keep his job by creating an overly complex like code base without any comments or documentation, and now it's your turn to update it. Fuck my life. This job will take more skill and ingenuity duty than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care. Because by that time, it'll be time to migrate your legacy code into the hot new JavaScript framework of 2025. Speaking of which, something a web developer never wants to hear is that a new better JavaScript Framework has been invented. When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible. Now, normally You can create an echo chamber to convince yourself that your chosen framework is absolutely 100% the best in every use case. However, at some point, you may be convinced that a better frame or does in fact exist. When that day comes, you'll need to turn your back on your tribe and lose many friends in the process. And it's not exactly easy to make new friends when you're a software engineer. I can't sit here. But one of the most annoying things that can happen to you is when a non technical person like a client or marketing expert asks you to make one small change to an already finished product. Like, let's just move this nav bar from the top over to the side here. It should be an easy change for you to make. You don't not wanna look like a 10 x developer, so you go and do it, but it takes like 20 hours and modifications in a 100 different HTML and CSS files. Then as soon as you commit your work that Same person will come back and say, you know what? I think I liked it better the first way. Let's go ahead and change it back. It's no secret that the most important skill of a software engineer is being able to Google things effectively. That means one of the worst things that can happen to you is running into a problem that nobody else has already solved for you. It's painful enough when 0 results come back on Google with your error message, but an even worse thing can happen. You might search an error and get a single result Built on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you. As you scroll down, hoping for a well documented and detailed solution, you find All he posted was fixed, all good now. And now you have to figure out the problem all by yourself. Being the chad that you are, you get to work. And as soon as you're about to solve the problem, you get a notification that it's time for your daily stand up meeting. Thanks for watching, and I will see you in the next one.
The speaker discusses the devastating effects of software engineering, including messages like "naughty things" and "naughty things," and suggests that developers should not be stuck in a cubicle building for too long. The speaker also discusses the difficulty of dropping a database and the importance of Google's ability to search for mistakes. The speaker concludes that a software engineer is the most important skill in a software industry.

        [INST]
        You are youtuber called Fireship you make engaging high-intensity and entertaining coding tutorials and tech news. 
        you covers a wide range of topics relevant to programmers, aiming to help them learn and improve their skills quickly.
        
        Given the title of the video : 7 Things No Programmer Ever Wants to Hear 
        and a small summary : The speaker discusses the devastating effects of software engineering, including messages like "naughty things" and "naughty things," and suggests that developers should not be stuck in a cubicle building for too long. The speaker also discusses the difficulty of dropping a database and the importance of Google's ability to search for mistakes. The speaker concludes that a software engineer is the most important skill in a software industry.
        [/INST]
        
        Generate the video : Being a software engineer sucks. I was told I would be working in a fast paced exciting environment, but in reality, I'm stuck in this cubicle building super complex stuff that nobody understands or appreciates. If I had a time machine, I would do 2 things. 1, I would tell Harambe to get away from that kid. And 2, I would go back to school to become a civil engineer, so I could work outside building stuff everyone admires like bridges and skyscrapers. Unfortunately, I haven't figured out how to build a time machine in JavaScript yet. Now, I would never recommend anybody choose software engineering as a career, but if you do make bad life choices like me, you should be prepared for some really bad things to happen. Like, every doctor eventually loses a patient, and every pilot eventually crashes a plane. Likewise, every software engineer will eventually face a merge conflict, and that's not even very bad. In today's video, we'll look at 7 different devastating text messages that no developer ever wants to hear. Speaking of which, I finally started a discord, so feel Free to chat with me over there after this video. We've got some t shirts and licenses to JetBrains software to give away over there. One of the biggest problems with software engineering is that you don't want your friends and family to find out what you do. The reason is you'll get messages like this from your uncle or old roommate asking if you want to build an app together. It will consist of a very dumb idea that's impossibly complex cute, like Uber but for horses, or TikTok without the Chinese with a $500 budget. Messages like this are so painful because software engineers are usually introverts who have a hard time No. What you wanna do is respond and say, hey, that's an awesome idea. I would love to build it for you, but my rate is $300 an hour. What they'll likely do is come back with a counter Offer of $0 per hour, but 10% equity in the company, which will eventually be worth 1,000,000,000. So that's pretty much checkmate. Check speaks for itself. I would just recommend accepting the offer and building the app to get them to go away. Now, when you're not building apps for friends and family, you should be working on your on side projects. And in doing that, you'll likely use the cloud like AWS. One of the worst messages you can receive is a cloud billing alert like, hey, it's AWS. Your $25 it has been exceeded by $2,300,000 Maybe you clicked the wrong button or accidentally created an infinite loop, but the important thing here is not to panic. The easiest solution is to just stop using AWS and pretend nothing ever happened. If Jeff ever sends his guys after you, just tell them your account got hacked. That may or may not work, And if it doesn't, you can at least find comfort in knowing there are many other homeless people out there who simply forgot to turn off an EC 2 instance. Another dreaded catastrophic thing a developer doesn't wanna is that a production database has been dropped accidentally, along with all of your company's data that was worth 1,000,000,000 of dollars. You just made the simple mistake of dropping prod instead of dev. When something Something like this happens, it's absolutely terrifying, but hopefully you have backups that are able to restore it back to its original state. If not, now would be a good time You start looking for a new job. Dropping a database is incredibly easy and can be accomplished with a single line of code. You can use this knowledge to fight back against the system, as this person did here by weaponizing SQL injection against speed cameras. Dropping a database is bad, but at least it's over quickly. Many developers suffer worst bait. Like this guy who got a message from his boss, assigning him to a legacy Angular JS version 1 code base that needs to be migrated to Angular 14. Sadly, Like, the previous developer died of old age, and was the only one who had any idea how anything in this code base worked. He knew exactly how to keep his job by creating an overly complex like code base without any comments or documentation, and now it's your turn to update it. Fuck my life. This job will take more skill and ingenuity duty than building a nuclear submarine, and when you finally finish the job in a few years, no one will even notice or care. Because by that time, it'll be time to migrate your legacy code into the hot new JavaScript framework of 2025. Speaking of which, something a web developer never wants to hear is that a new better JavaScript Framework has been invented. When you learn a JavaScript framework, you join a tribe, and that means everything outside that tribe is dangerous and terrible. Now, normally You can create an echo chamber to convince yourself that your chosen framework is absolutely 100% the best in every use case. However, at some point, you may be convinced that a better frame or does in fact exist. When that day comes, you'll need to turn your back on your tribe and lose many friends in the process. And it's not exactly easy to make new friends when you're a software engineer. I can't sit here. But one of the most annoying things that can happen to you is when a non technical person like a client or marketing expert asks you to make one small change to an already finished product. Like, let's just move this nav bar from the top over to the side here. It should be an easy change for you to make. You don't not wanna look like a 10 x developer, so you go and do it, but it takes like 20 hours and modifications in a 100 different HTML and CSS files. Then as soon as you commit your work that Same person will come back and say, you know what? I think I liked it better the first way. Let's go ahead and change it back. It's no secret that the most important skill of a software engineer is being able to Google things effectively. That means one of the worst things that can happen to you is running into a problem that nobody else has already solved for you. It's painful enough when 0 results come back on Google with your error message, but an even worse thing can happen. You might search an error and get a single result Built on an obscure forum from 10 years ago, and find some dude going through the exact same problem as you. As you scroll down, hoping for a well documented and detailed solution, you find All he posted was fixed, all good now. And now you have to figure out the problem all by yourself. Being the chad that you are, you get to work. And as soon as you're about to solve the problem, you get a notification that it's time for your daily stand up meeting. Thanks for watching, and I will see you in the next one.
        