When multiple threads may cause a problem in a Java application? Check fifty second question of full-stack dev quiz to verify what you know about thread-safe aspect.
We usually do not think about concurrency when building simple web applications. That is a mistake. Web applications may process multiple requests at the same time, and inconsistencies coming from concurrency may suddenly cause problems. Today's question is is i++ atomic in Java?. Can we assume that one of the simplest operations is thread-safe?
When I have recently gone on vacation, I have taken a book with me. I always do that with better or worse results. This time it has been "Traction: How Any Startup Can Achieve Explosive Customer Growth" written by Gabriel Weinberg that had been recommended to me. I have read it all so I have decided to write a review.
Well done project in Angular should have a clear, well-defined structure. Do you know how to split components to modules? What are best practices? Check fifty first question of full-stack dev quiz to verify if you know how to break project down into Angular modules.
Since the second edition of Angular, you can break down the project into modules. Although the technicalities are widely known, developers are often not sure which components should go to which module and even what modules they should have.
Estimating using Story Points not always makes sense. Do you remember the key elements? Check fiftieth question of full-stack dev quiz to test what you remember from Scrum Story Points will not work for you article.
Agile methodologies are based on relative estimating. It is a fundamental element of Scrum which increases accuracy and predictability of projects cost and timeline. If you adopt Scrum, you really should estimate in Story Points. However, if you give up on some Scrum rules, Story Points will do a lot of harm. See when you should not even try using Story Points.
It is obvious that nobody has to remember all the details that are easy to find in the documentation. But on the other hand, it is good to know the basic stuff to not waste time checking it every time. Check forty ninth question of full-stack dev quiz to verify how much you remember about data modifications using Liquibase.
Database upgrades also involve data changes. One of the most popular ones are various data updates. If you have a static value known beforehand, it is simple. How about a dynamic value computed based on another column? How to tell Liquibase that col2 is not a value but a source column name?