‘I Do Declare’

Share This Post

We have been discussing data types over the past few postings. We have covered them from a very introductory, high level. I will have other posts where I will delve deeper, but today, I want to talk about how to declare a data type.

Now, before I dive in, I want you to understand something. I have been using JavaScript in my examples. I love JS. I use it a ton and I think it is an essential language that every developer should learn. With that being said, it is not a perfect language (which one is?). I have mentioned this before, but JavaScript is loosely typed. What that means is that when you create a variable, you do not have to state what data type it will contain. That is not true for strictly typed languages, such as C#, Java, etc. In those languages, you have to declare the data type.

So in JavaScript, you can create a variable along with changing data types as follow…

[code lang=”js”]
// Declare variable
var myVar;
// Instantiate variable with numeric data
myVar = 10;
// Change data value and therefore the type
myVar = "This is a string";

So, as you can see, data type conversion is loose in JS. In other languages, you have to use the ‘new’ keyword to create a variable. In JS, this is only true of an Array, and even that has exceptions. You can use the new keyword in JS, but in some code quality tools (JSHint, etc.) this will throw an error. There is some scuttlebut about making the next version of JS strictly typed, but who knows when that will be done.

[code lang=”js”]
// Create a data type array
var myVar = new Array();

Here is a C# example…

[code lang=”js”]
// An example of an integer
public int myNumber;
// An example of a string
public string myString;

Happy Coding!

More To Explore


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.


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

Need help?

Let's have a chat...


Jump Back In!

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


Begin Your Learning Journey Today!

Come back inside to continue your learning journey.