Are you new to JavaScript? Have you ever wondered what the difference is between var, const, and let?
Understanding the scope, hoisting, and reassignment of variables in JavaScript is crucial for developing robust and maintainable code.
In brief, variables declared with var are function-scoped and are hoisted to the top of their containing function or global scope. Reassignment is possible within their scope.
var a=4
Variables declared with let are block-scoped and are hoisted to the top of their containing block.
Attempting to access a let variable before its declaration will result in a Reference Error. Reassignment is possible within their block scope.
let b=5
Variables declared with const are also block-scoped, but they must be assigned a value when declared, and they cannot be reassigned to a different value after their initial assignment. However, the value itself can be mutable if it's an object or an array.
const flag=true
In modern JavaScript, it's recommended to use const by default and only use let when you need to reassign the variable. Avoid using var unless you have a specific reason to use it, as it has some quirks and can lead to unexpected behavior due to its function-scoped nature and hoisting.
Remember, using the right variable declaration is essential for writing maintainable and bug-free code.
”Quality is not an act, it is a habit” — Aristotle
Imagine a world where software works flawlessly, where products and services meet your expectations and give you a satisfying experience. This is the world we can create with Software testing.
Every IT community requires testers because there would be no one dedicated to identifying issues within the software of a computer, machine, program, or other devices that could cause it to malfunction. However, Quality Assurance is more than just testing; it is also the process of incorporating quality into software development.
Traditionally, Tester’s Day has been observed every year on September 9. On September 9, 1945 when the scientists who were testing the computer Mark II Aiken Relay Calculator, they found a real small moth between the contacts of the electro-mechanical relay and one of them pronounced the word ‘bug’.
The scientists had to make a report on the work done where the term ‘debugging’ appeared for the first time. Now debugging is the process of finding and eliminating bugs which lead to incorrect performance of the system and failures. At that time, the tests were focused on the hardware because it was not as developed as today and its reliability was essential for the proper functioning of the software.
”Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it” — Brian W. Kernighan
The term debugging was associated with the application of a patch for a particular bug as a phase within the stage of software development, and that is why the tests that were performed were only of a corrective nature by taking certain measures in order to make the program work and it was in 1949 when Alan Turing wrote his first article about carrying out checks on a program and then in 1950, in the article “Turing Test”, he explains the situation of how a software must adapt to the requirements of a project and the behavior of a machine or a reference system must be indistinguishable.
However, according to the Yale Book of Quotations, the American inventor Thomas Alva Edison used the term ‘bug’ in a letter to Theodore Puskas in 1878 to describe a flaw in a system.
According to other sources the term bug was commonly used to describe faults in the system during Edison’s time and according to some reports this wasn’t even the first ever computer bug — “It was reported as the first bug in jest, as it was an insect. The term bug had been used as a label for problems in computers and other electrical systems for a long time before this. Grace Hopper did not find the bug. Bill Burke found the bug. Grace Hopper was the team lead and often told the story of its discovery.”
Though people have different assumptions or thoughts for this day, it is important to visualize how the software testing stage has evolved and emerged from its absence to its continuous presence throughout the Software Development Life Cycle. Now we have so many roles and responsibilities within the Testing and it has evolved to a great extent and its all because of a bug found.
Every day is a Tester’s Day, however, it’s acceptable to have an exceptional day that makes testers around the globe share and team up and feel proud to be one. I’d like to congratulate all the people who test software, who strive to make the applications with great quality, passion and wish them all the best! Happy Tester’s Day to all!
World Tester’s Day is recognized on the 9th of September every year to mark the discovery of the first-ever bug in 1947 since then.
Happy Testing!!!Don’t let any bug escape your sight!
Please share this post with others to inspire them to join us in the world of testing!!!
