TJ is Blogging!

This is a continuation of my previous post on how to win a hackathon - 1 . There, I have discussed some important things to do if you want to win a hackathon. If you didn't read it, please go ahead and have a look ^^. 4. Know your judges 👨‍⚖️ Most of the hackathons, they will publish what are the judging criteria and what the expectation of the app you are building. One of the most common criteria would be the relevance to the theme. It would be of course has to be considered during finalizing the idea. We have discussed this part in our previous post. However, it would be great if you know the panel of judges who are going to review your app submissions. This is a very important perspective of the project that you are going to work on during the hackathon. If you know who the judges are before you start building your app. Then you have to think of the psychological perspective of the judging panel. Judges from non-technical fields Let's say the judging panel includ...

Previously I've posted about what is a hackathon and  why you should go to hackathons . This post is about some points that you should concern if you really want to win a hackathon. I'm going to write this as a series of posts because I might need to describe some details for each area you have to concern. So, let this be the first post of the series. There can be two types of wins. 1. Unexpected wins I'm not ashamed to say most of the wins I've had from hackathons are unexpected. Yet they are the best! because you never expect to win at all. You go to a hackathon without planning (sometimes without even knowing much about it) and you find random people as a group, develop something spontaneous. Somehow it turns out to be a great idea and a great hackathon project. And you get really awesome gifts too. 2. Well planned wins This is like training for an examination. You have to do your homework. You have to learn about the event, technology, have several conce...

This post is for young developers, students or anybody who is interested in Hackathons. If you don't know what a hackathon is, it is a competition for programmers. Something like a programming marathon. Why there is a "hack" instead of programmingthon or something? Well, this is my personal opinion, in hackathons, they don't expect you to hack like illegally. The idea is to do something fast and not the way someone normally do. Normally for hackathons, you get around 24 to 48 hours to build something (maybe weeks depending on the event). In order to build something that fast, you gotta use some tricks, or tweak a little than what people normally do. What do I know about hackathons to write about them? Well, I don't like to brag about myself but yeah I've participated into number of local and international hackathons and won few prizes as well. So I would know a thing or two about them :) As a developer I love hackathons for many reasons. 1. Food! ...