Potato Couch

Been wanting to post in a long while but not finding the right time. Or the mood for a long or wordy post lol. So what's keeping me busy these days? Well, I've been watching a lot of TV series and here are my favorite TV shows.

1. Scorpion
2. How to Get Away with Murder (Season 1 has just finished, looking forward to the next season)
3. The Walking Dead

And here are other TV shows that I enjoy as well, though they're no longer ranked

• The Flash
• Sherlock Holmes (still on the second episode of Season 1 as I wrote this lol)
• Big Bang Theory
• 12 Monkeys
• Agents of SHIELD

And here are other shows I'm waiting for the next season to be shown

• The Strain
• Dracula (not sure if they're going to make another season though)

So yes, I'm really busy

THE LIFE OF A BUG

Found this article and aside from it's kinda funny, it also explains the bug well

The life of a software bug may be described as follows. A bug is born when a person makes an error in some activity that relates to software development, such as defining a requirement, designing a program, or writing code. This error gets embedded in that person's work product (requirement document, design document, or code) as a fault.

As long as this fault (also known as a bug or defect) remains in the work product, it can give rise to other bugs. For example, if a fault in a requirements document goes undetected, it is likely to lead to related bugs in the system design, program design, code, and even in the user documentation.

A bug can go undetected until a failure occurs, which is when a user or tester perceives that the system is not delivering the expected service. In the system test phase, the goal of the test engineer is to induce failures through testing and thereby uncover and document the associated bugs so they can be removed from the system. Ideally the life of a bug ends when it is uncovered in static or dynamic testing and fixed.