top of page

Hackathon

  • Writer: tristanraj
    tristanraj
  • Nov 15, 2018
  • 2 min read

The hackathon arrived and with it came alot of conflict, lack of sleep and painful code sprints.

In hindsight we were too relaxed and did not complete enough work in time before the hackathon , during the hackathon we had lacked urgency to do work throughout, severely overestimating our abilities and underestimating the size of our features, we had prior to the hackathon looked at it far too individually, but put together our application is rather complicated. This led to loads of conflicts, lack of sleep and arguements. I would elaborate further but there is nothing much further to it rather than lots of misunderstanding and tension, perhaps working with friends gave us the idea that the way we are as friends is the way we work. Which is what we midunderstood. Everybody has a different way of working and understanding things when working. If we had understood that we could have sat down and discussed and get to know one anothers styles when working.


Overall the hackathon taught me a valuable lesson when it comes to development in that we should always evaluate our features and such with proper thought behind it and also think of it as a whole. One should never underestimate the features of an application.

What else it taught me is to be more understanding and work well with others during application development as well.


During the hackathon on top of working on the prototype, I had to work on the pitch, personally I was petrified, although I knew that it was essentially another presentation, I could feel the pressure of my groupmates and I's grades on my shoulder. Additionally we had been told that we would go to SAP and present our prototypes to them. I helped work on the slides with Janine and gave her the content that we would be presenting, and with her and Gi Keis help I did the pitch and they gave me feedback.


One of the reasons I was afraid nearing to the demo was that our demo wasnt well done, it was mostly hard-coded and we didnt have enough completed. This was mostly due to our lack of urgency I would say, of which I am guilty of.


Recent Posts

See All
Demo day and P2 Completion

From the span of the three says prior to p2 demo day and the demo day itself I had been sick as my colon was swollen and had caused me...

 
 
 
Pre demo day development

So as it was my task to do the nearby clinic option, I decided to start by attempting to get Google Maps API to work and show the Google...

 
 
 
Post-hackathon discussions

During our discussions we decided that to learn from our mistakes we would reduce the amount of features and fully focus on three main...

 
 
 

Comments


bottom of page