Issues

[eliasmalik]

You created only two issues (#3 and #4) for the whole project, neither of which have any description.

From looking at the issues, I have no idea what work was meant to be done against them.

I know it seems like an unnecessary burden to have to create issues for work when you're all sitting with each other, but it's really important to get into the habit of breaking down tasks into smaller chunks. This will help you with your planning in future, when you will have to estimate how long you will take to do something.

If your tasks are really big, it is much harder to estimate them, and your estimates will be wrong more often, because you've not thought about the task beforehand.

For example "database" (issue #4): what is included in this task? how long will it take? what could go wrong? I cannot tell.

If instead you had a number of tasks like:

• Create DB schema
• Setup DB build and connection scripts
• Create and test DB query functions for reading posts
• Create and test DB query functions for updating posts
• ...etc.

Then it's much easier to estimate each task, and easier to see what work needs to be done for each task, which reduces the amount of discussion you need to have in your team.