Founder @QVista.io. I build no-code automation tools that help teams streamline work. I share insights on automation, SaaS development, and solving workflow challenges.
Interesting questions! Playing around with let and const reminded me how important clear structure and encapsulation are — something we focused on while building QVista to make workflow automation visual, organized, and easy to manage.
The use of const, let and var in the post is the common agreement in the community.
I think the biggest pain point is the use of const. While it is a constant for primitives like strings and floats, when you are using it on arrays of objects it is not that much of a constant.
For me working with objects or arrays I use let when the variable should not be exposed. Otherwise I use var.
The reason block scopes are safer from overwriting has to do with the fact that javascript has no namespacing build in. The emulation of namespaces is nesting variables in objects.
Thanks David! You've identified the issue that trips people up—const protects the binding, not the contents. Your point about arrays and objects is perfect. The namespacing insight about block scope is excellent too—that's the real nice thing with let and const. Cheers buddy! ❤
Self-taught student and professional in fullstack web development, currently working as freelancer. Have a degree in Economic Sciences by UNESP and MBA in Financial Management and Controllership.
Location
Araras, São Paulo, Brazil
Education
Self-taught in fullstack web development. Degree in Economic Sciences by UNESP and MBA in finances.
My pleasure, Laurent! I'm glad it landed clearly. This series is all about making the confusing parts of JavaScript actually make sense. More chapters coming on this, prototypes, and the event loop. Thanks for reading! ❤
We're a place where coders share, stay up-to-date and grow their careers.
Interesting questions! Playing around with let and const reminded me how important clear structure and encapsulation are — something we focused on while building QVista to make workflow automation visual, organized, and easy to manage.
The use of
const,letandvarin the post is the common agreement in the community.I think the biggest pain point is the use of
const. While it is a constant for primitives like strings and floats, when you are using it on arrays of objects it is not that much of a constant.For me working with objects or arrays I use
letwhen the variable should not be exposed. Otherwise I usevar.The reason block scopes are safer from overwriting has to do with the fact that javascript has no namespacing build in. The emulation of namespaces is nesting variables in objects.
Thanks David! You've identified the issue that trips people up—const protects the binding, not the contents. Your point about arrays and objects is perfect. The namespacing insight about block scope is excellent too—that's the real nice thing with let and const. Cheers buddy! ❤
Cool article
Thanks Chizi. Have a good one! ❤️
Thanks for this excellent breakdown!
Very well expleined! Congrats!👏👏👏
Thanks Theodora. Cheers!
Nice article! Very well explained and detailed information
Great explanation! 👏
Thank you, Rishit. Cheers! ❤
Neatly written
thanks! cheers Abhinav ❤
Thanks for this clarification!
My pleasure, Laurent! I'm glad it landed clearly. This series is all about making the confusing parts of JavaScript actually make sense. More chapters coming on this, prototypes, and the event loop. Thanks for reading! ❤