Stop Saying That!

Share This Post

In any programming language, there are a group of words called ‘Reserved Words’ that are set aside for specific purposes within the given language. The developer needs to keep this in mind when they are writing code. If they use one of these reserved words within their code where it is not intended to be used, their programming could yield odd results.

For example, the word ‘function’ in JavaScript is utilized to indicate a function/method is being constructed. If you use that word elsewhere, your code could break. There are also words that are not exactly on the reserved list, so to speak, but could cause issues. Let’s take another example from JS. The word location. In JavaScript, the word location is a part of the DOM (Document Object Model) and is used to either direct an end user to another page or grab the current url…

[code lang=”js”]
// This line of could would return the location of the current page.
var x = location.href;
[/code]

So if you use the word, ‘location’ in your could, you could inadvertently send the end user to a non-existent location, thus breaking your code.

Here is a link to some reserved words.

Now, beyond the use (or non-use) of reserved words is the concept of naming things intelligently. Please, for the love of all the sanity of developers everywhere, please name things that make sense. What I mean is name your pieces of code in a manner that is logical. Name variables with names that make sense. If you are getting a name from the end user, perhaps name it userName. Do not use any random or non-sensical verbiage. This practice goes hand in hand with proper comments.

Happy Coding!

Clay

More To Explore

Code

Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.

Code

The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top
small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.