Agenda Timer
Keep meeting agenda under control. Eliminate protracted meetings with better time planning and execution.
Google Sign-In
In part 2 of the tutorial I built bundles from JS files. Although that is fundamental, it is not enough to create a package for an average project. Necessary element of each bundle is an HTML file. This part of the tutorial will present you how to include HTML in the bundles.
Last year I published some statistics for dba-presents.com. Hundreds of people viewed it so there was some interest in it. It was also a chance for me to see how it looked in 2017. Both reasons convinced me to gather similar statisics for 2018. Join me in taking a closer look at it.
Previously I showed you what project we are going to work on. I do not want to postpone it further so this time I will build first JS bundles. I will do it almost at minimum cost. Almost means that it could be simpler but I want to make flexible so I could extend it in the next articles.
Until a web application is at the development stage, you may ignore bundling modules. But when it goes to production, you start considering minification and reducing a number of requests for static resources to the server. Webpack is currently one of the most popular solutions for that.
Do not declare variables in JavaScript with var. Use let or const instead. A natural question is what is the difference? All of this can be explained with a few examples.
Do your colleagues make fun of you that you do not know Scrum? Show them they are wrong.
This scenario happens to almost every team at some point in time. A user story is estimated to a relatively small value e.g. 1 Story Point. It is added to the Sprint Backlog during Spring Planning. When a developer starts working on it, it becomes obvious that the user story is bigger than 1 SP. Should the estimate be updated?
How about documentation in Agile? Thirty fifth question is about Agile Manifesto and documentation.
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.
