'Happy Path' is a Common Illusion

A mistake I see junior developers often make, focusing only on the ideal scenarios.

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:

[RobertSmith-chjj]

100% this. I recently completed a project where automated testing fooled me into thinking my code was operating correctly. I setup a simple test case and the code passed. I didn't consider more complex, real-world scenarios. Code passed the tests but produced bad data in production.

[emekatimothyiloba]

I was honestly thinking about this yesterday. Thank you

[mailmerohit]

Hey, sir please make a car video regarding, how to stop thinking/overthinking after work and let present 100% with our family.

[Sahrokh]

It's not just junior developers. Many times *we have to* deliver rushed and crappy code. We are forever time-boxed by upper people who don't know and don't care. You are literally not given the time to take into account what happens if a job queue or email don't work. It *HAS* to work and you'll never get allocated the time to implement failover. Of course, when it fails, it's *your* fault, not the fault of whom gave you half the time needed to even deliver the "happy path" code!

Now, I don't know if in the USA it's like this, but in the European countries I lived in, it is.

[iconicae]

Sometimes I am afraid of testing bad senarios because I am happy that the code did his job so this vedio is good tip for me to improve

[JouvaMoufette]

It's just as important to make sure what the code DOESN'T do as it is important to make sure what it DOES do.

[whatdahack]

Happy Path is the first, Bad Paths are the second. That is just logic. What if new users decide to register at the service?!

[iconicae]

I use error('field'){{$message}} enderror is this a good way for validation or no

[alexv]

Concentrate more on unit and integration tests then.