How about documentation in Agile? Thirty fifth question is about Agile Manifesto and documentation.
How to fail Liquibase changeset when prerequisites are missing
Index creation should not start when there is not enough disk space. An old table should not be dropped until it is completely empty. A database upgrade may happen only if a DBA has changed a default value of some setting. Many database upgrades have some prerequisites. If they are not met, the whole change should not even start. You may write a checklist during development and follow it on the upgrade but there is a better way - preconditions in Liquibase.
Full-stack dev quiz question #34
Spring libraries are back at dba-presents.com. Thirty fourth question is about Spring Retry.
npm ERR! code ERR_STREAM_WRITE_AFTER_END
Today I have encountered a problem with NPM. When I tried to install a new package, it returned me npm ERR! code ERR_STREAM_WRITE_AFTER_END. I would like to share the details and the solution for those of you who will see the same error.
Environments in Liquibase changesets
Usually, database changes go through a pipeline of environments. For example, they are developed at developers' laptops, checked into a repository, deployed to the development environment, pushed to the test environment and finally propagated to the production. Ideally, the changes should be applied to all these environments in the same way but in real life there are some exceptions.
Full-stack dev quiz question #33
Have you used CHECKSUM function in SQL Server? Thirty third question verifies this knowledge.
Repeating actions with Spring Retry
Some operations in software systems are not reliable. Database operations may deadlock, sending an email may fail, a network request may not reach the destination etc. There is a chance that another attempt of the same action will succeed. It is recommended to wrap such operations with a retrying mechanism. Spring Retry is a library that makes it easy.
Six sins of forming Scrum Teams
A Scrum Team is not just a set of random people that work in the same company. It is a specific group that meets a bunch of conditions. Rules and guidelines of Scrum Teams creation are well described by Scrum methodology. I have talked to different people about it over the years and I noticed that there is a set of common misunderstandings regarding Scrum Teams. If you look around, you may notice some of them.
Working software over comprehensive documentation
Does the title sound familiar? This is the second point listed in Agile Manifesto. Do you remember about it everyday at work? Do you really understand what it means and why it is so important? I am sure some of us do not because I have met two such persons in the last couple of weeks :)