Hackathon - What I learnt in 24 hours?

Hackathon — What I learned in 24?hours?

Where can you experience all of these emotions in a 24-hour period: excitement, nervousness, eagerness, inspiration, sleepiness, enthusiasm, enlightenment, and last but not least Dance Party? To experience these, though, you must take part in a hackathon.

It was my first Hackathon in my professional career (forgot about college time ??) and really it is a great experience for me.

Special thanks to 7Span for organising this event. We had the opportunity to learn about how we can create each part of the product and how every department is required for one product.

Definition:

Kaushal Gajjar & Harsh Kansagara explained about the rules. Hemratna Bhimani announced the definition of Hackathon in just a single line that is “URL Shortner”. For a little moment, everyone was perplexed as to what it was and how it would be executed.?

Name of?Teams:

• Team-1: BugBusters (My Team ??)
• Team-2: CodElfs?
• Team-3: ZeroRisk?
• Team-4: NeodaModes?
• Team-5: UnknownSociety

First 30?Mins:

We BugBusters arranged a meeting for the first 30 mins and discussed all the features which we can implement. We have decided some features which is must be implemented. Apart from that we thought about Good to have features as well as out-of-the-box features too.

Criteria:

My Role:

In this hackathon, my role is for Flutter Application Development as well as managing the team. We two (out of 14) team member has decided to do the management of team also.

What I learned from this Hackathon:

• Instead of starting the code directly, just checkout the libraries or code availability for core functionality only.
• You don’t have to stick with any one or two criteria. Just implement less features but it should be in all require technologies like Mobile App, Web Page etc.
• Manage the team if you have experience and try to check what your team members are doing.?
• Be passionate, Have patience.
• Be a team player
• Don’t try new things if you don’t know anything about that
• Think twice before implementation,
• Try to find most accurate solution for core functionality
• Don’t be shy, you should speak. May be your point is valid at that time.
• Discipline — Very important thing

Result:

We’ve had a 24-hour hackathon, and we’re all eager to see the results.Our result was revealed on the next day.

The team BugBusters is runner-up. Absolutely the first one is ZeroRisk. We yelled when our name was called. Because it was so loud, everyone in the auditorium turned to face us. We were shocked! Finally, every single effort had paid?off!

And best wishes to everyone who participated and put forth such wonderful effort. You are top-notch.

I hope anyone who missed this hackathon would participate the next?time.

Thanks for reading. Have a great time.

Originally Posted : https://medium.com/7span/hackathon-what-i-learned-in-24-hours-8cce87d8b928