Smriti Tuteja

Author
Smriti Tuteja

Blogs
Smriti began their journey in software development but found their voice in storytelling. Now, Smriti simplifies complex tech concepts through engaging narratives that resonate with both engineers and hiring managers.
author’s Articles

Insights & Stories by Smriti Tuteja

Explore Smriti Tuteja’s blogs for thoughtful breakdowns of tech hiring, development culture, and the softer skills that build stronger engineering teams.
Clear all
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Filter
Filter

Tips to perform well at hackathons

Hackathons have long been much talked about events, they have been established as superior tests of wit. With over 100s of participants, amazing prizes up for grabs and soaring competition, the hackathon is a great ground for ideas and innovation. Hackathons are usually accompanied with lots of excitement and stress levels are high too, owing to strict timeframes, lots of competition and performance pressure.

As developers, we all think that we have all the skills required for being great developers and we have portrayed them at several occasions but why is it not us on the winners list of the hackathon.

Here are some ways that can assure good performance at your next hackathon.

  1. Avoid unrealistic goals: A hackathon is time bound, expecting to build a functional product with too many features will be too much and excessive stress will hinder performance. A minimum viable product that works well without glitches may work well to secure a winning position at the hackathon.
  2. Select your team intelligently: Even a great idea cannot be executed well in a limited timeframe if teamwork is not in place. The selection of a team should be based on some basic criteria that aid the success of a team:
    • Teammates must be equally passionate about coding and the prospect of victory in the hackathon.
    • The selection must encompass expertise in different areas. Try to get people with different skills, both tech and non-tech.
    • All members must be tolerant towards pressure. Morale loss under strict deadlines is a deterrent to performance.
    • The vision of each member of the team towards the result must be congruent.
  3. Take inspiration from others in the community: A thorough insight into the tactics that other hackers employed at previous hackathons can be advantageous. Their experiences, successes and failures will help in coming up with a good plan of action.
  4. Use source control tool: Just imagine, you are into a long process of building your product, hours later you spot a malfunction and you don’t know where you made a mistake. There definitely isn’t enough time to go through piles of code to spot the error. Hence, it’s wise to use a source control system like git that can help in keeping track of each change and identify the change that caused the error.
  5. Use existing libraries and frameworks: Don’t reinvent the wheel. Don’t spend too much time in writing code for functionalities that can be implemented using open source libraries and frameworks. Just focus on implementing the core idea you are working on.
  6. Use quick deployment solutions: The core idea of a hackathon is to build a working prototype of your idea. Don’t spend too much time in hosting the app. Figure out how you can quickly deploy applications on cloud hosting solutions like AWS, Microsoft Azure or Google Cloud. You can also use PaaS solutions like Heroku, Openshift or IBM Bluemix for deployment and hosting. Using an easy deployment solution will help the team to concentrate on coding, building, deployment and testing.
  7. Presentation is crucial: It is wise to spare some time to prepare for the presentation because everything that you have done in the hackathon depends on how correctly you can demonstrate your hack. Make sure that you cover all aspects of the hack including important points like - problem being solved by the hack, scope that the current hack covers, why it is different from existing solutions and work that can be done in future.
  8. App should be interactive: During the presentation, an interactive app is more likely to catch the attention of judges and create an impression than a rather dull app. It should hence be kept in mind that there should be a scope for user interaction.
  9. Socialize and network: Hackathons are not just about competition but also about networking, meeting interesting people and making some friends. Make sure competition does not come in the way of having fun. Winning is not the only thing that you can take away at a hackathon, you might even find your love.

You are sure to rock your next hackathon if you follow these steps. There is no rocket science in a hackathon, after all we demonstrate our coding skills each day, it is all about planning and executing effectively.

Stay tuned to know how you can conduct a successful hackathon.

Round up of ACM ICPC Practice Contest

There isn’t much time left for the regional level of ACM ICPC coding contest. It is the most prestigious contest globally, and considering the exposure and charisma that it holds, as one nears the timelines, stress levels increase and one tends to doubt their preparation.

We at HackerEarth, understand this and conduct a 5-hour practice contest as a build up to the ACM ICPC.

The contest was styled similar to the ACM ICPC contests, wherein 5 hours were provided to solve 11 programming problems. The problem set, as described by the team involved in preparing, testing, fixing, and conducting the contest - was relatively easy for expert programmers, and we could feel the wave of submissions coming as soon as the contest became live. In the first hour itself, 8 out of 11 problems were solved by a lot of teams. The three remaining problems according to the team were difficult, especially Legendary Graph - and they were right! Only two teams could manage to crack that problem in the duration of 5 hours.

Though, the problem set ended up having one issue - which was the 10th problem.

So, before the prizes are distributed and sent, we need to clear the confusion regarding the final standings of the contest.

Game of sweets! (the 10th problem) did not have a clear problem statement, which resulted in a lot of teams interpreting the question differently than they should have — and ended up submitting a lot of apparently wrong solutions — some of which were correct according to the alternate interpretation of the problem statement. So, to sort that out, we decided to manually evaluate the submissions for the top people in the rank list — by checking if their solution passed either of the two interpretations of the given problem and then update the rank list for the top 3 people and the top 3 Indian teams.



The contest received participation from about 25 countries across the globe. A total of 1384 teams participated. Some of the best international programmers like anta, Lewin, Errichto, Xellos, Natsugiri, waterfalls also participated.

The top 3 teams were Anta, bloody_unko, and Lewin - where Anta and Lewin participated individually, and not in a team! They would be awarded vouchers worth $100, $80 and $50 respectively. The top 5 Indian teams were Faceless Men, DaFruitsSalad, Rex_Regum, Heuristics, Mobius_Treap. The top 3 Indian teams in this contest, who also qualify for ACM ICPC Regional will have their ACM ICPC travel expenses reimbursed.

The practice contest has been successful in equipping the participants with the format of the regional level of ACM ICPC contest. It has also succeeded in bringing to light several competent programmers on the global level. The zeal that this contest received globally, encourages us to come up with other similar contests in the future.

PS. You can find the editorials for all the problems in the contest here.

Hacker: The misunderstood innovator

Hacker! What is the first thing that comes to mind when we hear this word? Security systems penetrated, important information stolen or some other type of cyber crime. However, let’s pause for a moment and think, what comes to our mind when we read “10 life hacks you must know” or “5 relationship hacks”; doesn’t this refer to things that would make our lives or relationships easier. So, a hack is a useful innovation that uses a different approach to chores to achieve ease and efficiency.

To brand security breaking as hacking is unjust because if one goes by the history of the word hacking, it traces back to the early 70s. Even the origins suggest that hacking is all about wit, it makes life easier, and it is pure innovation. Yes, there are people who have used this wit and innovation to achieve unscrupulous objectives but those people can be correctly termed as crackers and not hackers.

The word hacker has long been misused and portrayed with a negative aura. It has gone ahead in demeaning all those creative souls who have hacked to glory and given amazing innovation to the world. We are a large community of coding enthusiasts, we are hackers. Thus, we have taken up this initiative to separate the word “hacker” from the infamy attached, we want to help ourselves and our co-hackers achieve the deserved identity. We aren’t alone; many people in the media are also talking about it.

It is time that the term “ethical hacking” loses meaning because hacking is always ethical and unethical hacking is better referred to as cracking.

Going ahead with our objective to make the difference between hacking and cracking conspicuous, we are filing a petition to take this cause to as many people as possible. The petition aims at the achievement of the deserved status.

You can sign the petition at - https://www.change.org/p/hackerearth-dear-media-know-the-difference-between-a-cracker-and-a-hacker

Our initiative aims at giving everyone the creative freedom to bring out the hacker in them. There is a hacker potential in each one of us and we aim to harness it to achieve results. As hackers start coming to limelight with their work of art and results of wisdom our objective will near fulfillment.