28East Bug Hackathon: Building Stronger, More Reliable Software

When people think of a hackathon, they often picture teams racing to build something new from scratch.

At 28East, our latest internal hackathon took a different approach. Instead of building a new app, our development team worked through a set of bugs deliberately introduced into one of our existing codebases.

The goal was simple: sharpen technical skills, share knowledge across the team, and improve how we identify and solve issues in the systems we build and maintain. 

A Practical Challenge Built around Real-World Code

The session was led by Petrus Schabort, one of our software engineers. He introduced nine bugs into a codebase the team already works with regularly: our standard feasibility tool.

These bugs were not random. They were based on issues the team has dealt with before, as well as concepts that are useful to keep top of mind when working with production code.

The developers were split into pairs, with different levels of experience. Every 15 minutes, the roles switched. One person wrote the code, while the other guided the team’s approach.

This created a focused pair-programming environment where communication mattered as much as technical ability. It also helped more experienced developers share their thinking in real time, rather than simply solving the problem themselves.

The Technology Behind the Challenge

The hackathon focused mainly on React.js and JavaScript, from foundational concepts through to more advanced problem-solving.

The team worked in 28East’s feasibility tool, which helps clients check internet connectivity at a specific address or location. This made the challenge directly relevant to the type of software our clients rely on.

Learning Through Collaboration

Because 28East has a small development team, knowledge-sharing is essential. Team members often need to understand different parts of the system and step into different roles when needed.

That was one of the key reasons behind the hackathon’s format. It made learning practical and interactive, while encouraging developers to learn from each other’s areas of expertise.

One of the standout moments was seeing experienced developers slow down to help their partners follow the logic and understand the code.

In a timed challenge, it would have been easy to rush. Instead, the team focused on sharing their learnings.

The Results

Migael and Gedeon took first place after resolving two bugs and identifying additional issues not part of the original challenge. Their attention to detail earned them extra points and highlighted the value of looking at familiar systems with fresh eyes.

Micheline and Joshua placed second. Micheline had not worked with React before, so their session involved more teaching and learning. Even with that learning curve, they still solved two bugs!

Why This Matters for Our Clients

Internal exercises like this help us build better software and stronger teams.

By revisiting existing systems, testing assumptions, and sharing knowledge across the team, we reduce the risk of critical knowledge being held by a single person. That means better continuity, stronger support, and more reliable delivery for our clients.

What’s Next for 28East

The hackathon is part of a broader focus on continuous learning at 28East.

For us, these sessions are a practical way to keep improving: as developers, as a team, and as a partner to the clients who trust us to build and support their systems.