As you are getting elements by classname chances are that what is being returned to you are not numbers, they are probably DOM nodes or even strings. To start fixing it you should first console.log(number) this number variable of yours to check what is being returned by this let number = document.getElementsByClassName("number"); line

Nice portuguese! You're welcome

I'm very glad to somehow contribute to your decision, be it heading to the development world or not! If you have any doubts, questions, want tips or anything else you can come chat with me, if you'd like to. You're welcome and have a nice and happy development learning path!

In 2010 I started a technical IT course alongside high school. In this course I studied some basic programming (with Pascal, Delphi and later with Java) and also HTML and CSS. I enjoyed it, but not that much. Then in 2013 I started a Computer Engineering course at a university and had contact with C and a lot of Java and some deeper programming, hardware and engineering stuff. I then started really enjoying it and also began to seek knowledge about the web. It was in 2016 when I really decided that I liked web development and then started studying it apart of all the university stuff. First I got in a good touch with the front-end world, then discovered how the back-end worked and also started studying some architecture related topics and nowadays I'm a full-time software engineer at a startup :)

Please check my answer above to sse my points!

Please check the answer I wrote above to see my points!

Now I have more maturity (and I have remembered this website exists) so I will give it a shot and try to start some kind of discussion here! At the company I work we are using a full serverless environment (and using the Serverless framework you linked in your response) so we do not have to worry much about infrastructure. Our team is very very concise thus all all the technology demands end up on us. Our goal by using Lambda Functions is to have less things to worry about while still dealing with low cost (the company is going to have its first client in a couple of weeks), having high availability and scaling on demand whenever needed without wories. As the development team sees the business has got a solid basis and will eventually hit a high usage. Thinking about it and knowing all the boilerplate that comes with creating complete APIs via functions we discovered that there are wrappers that make it possible to create APIs like we usually do in a docker environment, for example (using Express for Node and Gin or Echo for Go, for example). By doing it we make it very easy to migrate to a docker/kubernetes environment in the future. Another great point in doing this approach is that we stay in touch with technologies we are already used to and it is much much much easier to create APIs this way because of all the middlewares everyone needs nowadays. Lambdas were initially created to carry very tiny and concise, objective workloads, but they are capable of handling a lot more work than that. I'll also add that even AWS is thinking that way because they have developed an open-source library that makes it possible to port Golang APIs written in frameworks to a Lambda environment (https://github.com/awslabs/aws-lambda-go-api-proxy).

Thank you very much for the answer! Very helpful, will keep these things in mind. Thanks for the advices!

Physical security is one less problem, that's true! And do you think just the development team is enough to make apps secure?

Thanks for the answer! And a very nice phrase to end the lesson. Cool! Do you think things like these could be achieved only by the development team or a security team would also be needed to make sure the application is safe?