There are a lot of good answers on the internet for this question already, I have no doubt that they all provide a much more complete explanation. But sometimes a high level understanding is enough to make an decision, instead of wasting hours of research then come to the decision that it is not needed. In this article, I’ll give the shortest answer I can come up with to answer this question.
Recently, I have been helping out with designing the new competency model for the my current employer. It has been a great learning experience, and as a result I have been trying to apply some of the learning to my personal development. This blog describes how I am planning to structure my own learning in the future.
I am always trying to be polite, friendly and calm at work. It is called being professional, and it is especially important for people working in professional services. The word professional is in the name kind of gave it away, so the last thing I want is saying something I regret to a client or teammate.
Scrum development is great, it allows iterative development and much faster feedback loops. The concept is nothing new to a lot of people, and the adoption rate has been increasing. But I have yet to work in a team where I think we have achieved the maximum efficiency, in fact, most of the time we are far from it. The concept of Scrum seems easy enough, so why it is so hard to do it right?
The most difficult choice to make when creating a simple web application is not choosing the right framework or colour scheme (for any backend devs out there). Instead, the struggle comes from deciding if a backend is required or necessary. A lot of the time, it is hard to justify setting up a backend service for a simple web application. More times than not, the only thing I really need is one or two simple APIs to bounce some data around. For that, I don't really want to spin up a new EC2 instance on AWS, create a backend, setting up a database and etc.
Open Web Application Security Project (OWASP) is a non-profit organisation that was driven by a community which wishes to make the world wide web a safer place. The latest top 10 document can found here. As you can see it is created in 2013, so many of the issues would have been addressed already by new technologies. In this blog, we will be explaining the top 10 vulnerabilities and how they affect the technology today.
package.json. This file, as the name extension suggests, contains a JSON object about the project. The follow snippet shows a very simple example of what a
package.json file might contain, for more information about what each section means browsenpm will offer a much better explanation. If you have not seen a
package.json file before, it might be best if you do some quick reading before continuing reading.
Keep a clean Inbox is not an easy task for even the most organised people because there are simply too many spams. There is only so many filters you can set up before it gets really annoying and tedious. Here are just some simple, but useful ways to keep a clean Email Inbox.