Totally agree. Best way to come over the block is to do something completely different. Give the problem to your unconscious mind and let it do the magic. Have a long walk, run, shower, sleeping. Read a good book. Do…
I would like to propose something with a hint of Agile: 1. Make all of the work visible by writing out the major thinks to be done (Stories) 2. Split the stories to as small isolated stories as possible. 3. Find stories…
Yes agreed. Don't waste your time on that and stay away of that monster. There are far better things to learn like how to create REST APIs and using QueryDSL or JOOQ for databases.
Short answer is no. Problem with the velocity is that we developers are really poor in estimates and the velocity is rarely accurate enough. So what I would like to recommend is that you first check your definition of…
Totally agree. Best way to come over the block is to do something completely different. Give the problem to your unconscious mind and let it do the magic. Have a long walk, run, shower, sleeping. Read a good book. Do…
I would like to propose something with a hint of Agile: 1. Make all of the work visible by writing out the major thinks to be done (Stories) 2. Split the stories to as small isolated stories as possible. 3. Find stories…
Yes agreed. Don't waste your time on that and stay away of that monster. There are far better things to learn like how to create REST APIs and using QueryDSL or JOOQ for databases.
Short answer is no. Problem with the velocity is that we developers are really poor in estimates and the velocity is rarely accurate enough. So what I would like to recommend is that you first check your definition of…