Hackathon test debrief

[falkirks]

Well that went pretty horribly :smile:

However there is valuable information we can take from this, including:

• Make sure you environment is setup beforehand.
• Inform me if I am asking something unreasonable.
• Be on IRC as much as possible.

The current code is going to be open sourced under a repo I create, you will all have access. I am going to attempt to shift over the commit history.

Does anyone have any questions or ideas on how to make things better?

[falkirks]

Due to me shifting over the repo, please don't make any changes right now.

EDIT: The code has been shifted over.

[TuffDev]

Thank you for providing that infrastructure for future reference. Yes I agree that did not go very well, I did not contribute as much as I thought I would and I did not understand as much as I thought I would.

The environment being set up beforehand is a big one for me, I had no way to test it and had never used Composer or a web server before. MongoDB was also new to me, despite the fact that I researched it extensively, I had no working knowledge of it. So understanding and using the tools before the project would be a good thing to do later on.

Perhaps adding comments to the code will help me understand what is going on, I know it is a hassle, but it is a good practice, especially when working in groups.

[falkirks]

@TuffDev the placeholder project that was ready a few days before had all the same dependencies. So if you had that working, the full project should have worked. But, I added mongo at the last minute, however I did inform everyone about the inclusion of mongo.

As for comments, that is an awesome idea.

[TuffDev]

I did manage to get the full project working after you helped me out. Thanks.